 |
Page History
...
Technical Description: all data elements and referenced concepts in the metadata repository are indexed and easily accessible by type-ahead and other integrated tooling solutions. The model browser is a convenient interface for exploring the metadata in a UML or data element centric way. Furthermore, the repository supports the import and export of modeling standards, such as XMI, which facilitates direct reuse.
Managing semantic relationships in order to link and share data
- ICR IRWG Requirements
In many cases, different systems call the same data element by different names even though they are semantically equivalent in a given context. For example, a hospital system may have a Patient Last Name and a clinical trials system may have a Subject Surname. Both of these data elements share a semantic equivalence, but it may be very difficult to combine them automatically. The metadata registry should provide a way to describe semantic relationships such as this in order to enable the linking and sharing of data.
Supporting interoperability standards (e.g. Healthcare Datatypes)
Domain Descriptions: a metadata specialist has been tasked with cross-linking the hospital system and the clinical systems in her organization. Fortunately, both systems have been modeled with well defined metadata, which has been registered in a metadata repository. Unfortunately, the information models used by the systems are not harmonized, so data cannot easily be integrated. Therefore, the metadata specialist defines semantic relationships between the elements that she knows are related, though they do not share the exact same common data elements. For example, she semantically links Patient Last Name in the hospital system to Subject Surname in the clinical system. Once all of the appropriate relationships are made, clinicians are able to navigate between the system seamlessly. Furthermore, the antiquated data warehouse where all of this information is painstakingly transformed and poorly linked can be retired, and quality of care queries can now be carried out using semantic relationships.
Technical Description: semantic relationship and rules between data elements can be formed, stored, and shared in the metadata repository. Furthermore, these relationships can be reasoned on using a inference engines and query systems.
Cross Reference:
- ICR IRWG Requirements Mapping/transformation support for ISO21090 data types
- https://wiki.nci.nih.gov/x/2gpyAQOARyAQ
- https://wiki.nci.nih.gov/x/IQhyAQqxJyAQ
https://wiki.nci.nih.gov/x/qxJyAQSupporting interoperability standards (e.g. Healthcare Datatypes)
Domain Description: Leveraging interoperability standards, such as standard data formats and datatypes are critical to data exchange within and across enterprises. For example, ISO 21090, otherwise known as HL7 Healthcare Datatypes, provide a basic representation of common chunks of data exchanged in the healthcare community, such as Address, Document, and Coded List. The metadata repository should be flexible enough to encode a variety of standards while restrictive enough to provide a common foundation for data exchange. Furthermore, it is critical that organizations and individuals be able to restrict, or localize, these standards for custom use.
2nd paragraph: describe the fact that the KR can accommodate any UML-based model (including ISO 21090)
Capturing data in a standard way using data element reuse
A metadata specialist has been tasked to expose some clinical research data in a standards-based approach. She sits down to her modeling tool, and, as a first step, imports the healthcare data types from the caBIG metadata repository. She begins replacing what were complex sets of classes and attributes in her existing model with these standard datatypes. The resulting system is not only simplified, but is also interoperable by virtue of using ISO 21090.
Technical Description: the metadata repository allows for the representation of any standard as long as it can be encoded in UML. ISO 21090 is such as standard, and can easily be exported into XMI and imported into a modeling tool. In UML, these classes can be represented as complex types and applied to attributes rather than associations.
Cross Reference:
- Mapping/transformation support for ISO21090 data types ICR IRWG Requirements
- CDEs from Man. curation, UML models and CRFs
Capturing data in a standard way using data element reuse
Is this one redundant with "Creation of metadata and management of information models through modeling and web tools" and "Finding touch points with other systems when building a population science application"?
Description: Core to interoperability is capturing data in a standard way using the same or similar data elements. Data elements Core to interoperability is capturing data in a standard way using the same or similar data elements. Data elements individually can be reused, for example allowing for patient data to be joined across systems using the Patient Medical Record Number. Forms Forms in their entirety can be reused, such as eligibility forms for multi-site clinical trials. Data Data formats for encoding biomedical data can be shared, such as MAGE-ML for gene expression data. This allows for data to be captured in a standard way, shared across platforms and systems, for users to search based on the data that is encoded using type-ahead Google-like functionality, and for users to build new systems based on the standards that are already in use.for gene expression data. This allows for data to be captured in a standard way, shared across platforms and systems, for users to search based on the data that is encoded using type-ahead Google-like functionality, and for users to build new systems based on the standards that are already in use.
Cross Reference:
- ICR IRWG Requirements
- CDEs from Man. curation, UML models and CRFs
Finding touch points with other systems when building a population science application
...
Technical Description: each information model has well defined metadata available in distributed metadata repositories. The nature of the metadata is such that simple queries can determine overlapping data elements. This can be visualized side-by-side in a tabular format, or graphically in a UML class model. The metadata repository can output data using UML standards, such as XMI, which can easily be aggregated and imported into a modeling tool.
Support data transformations in order to allow different flow cytrometry tools to work together
Domain Description:
Technical Description:
Even semantically harmonized tooling may utilize data of different formats. For example, in flow cytrometry alone, there are a large number of standards for encoding data, such as MIFlowCyt, ACS, NetCDF, Gating-ML, FuGEFlow, and OBI. When exchanging data between these systems, it is important to be able to describe the relationships between the standards, data elements, and value sets. The structure of the data, the naming of the data elements, and the actual values used to encode the same data may need to be transformed in order to interoperate on the data. On one hand, relationships between the standards can be manually described, and on the other hand, computable metadata enables automated transformation.
...
