Summary
Description of the profile
Load any new artifact, through multiple interfaces
Provide an application developer with the ability to define application-specific attributes (for example, defined using ISO 21090 healthcare datatypes) and an information model that defines the relationships between these attributes and other attributes in the broader ecosystem.
To support the use of binary data throughout the system, the binary data must be typed and semantically annotated.
All Information models, their representation and binding to data-types and terminologies will be managed by the semantic infrastructure.
KR information models, and discrete model elements, should be available in a number of broadly used machine interpretable data formats, or serializations. The stakeholders most interested in this publishing capability were caDSR, HL7 CIC, and CDISC. In particular, CDISC wants to support the export and import of schema for tabular data. This implies the capability to perform on-demand transformations between models and formats for the representation of model elements. NB: In dicussions with CDISC users, they indicated that this export feature should enable re-use of metadata and, in some sense, federation of repositories.
NB: THIS IS NOT AN EXHAUSTIVE ENUMERATION OF EXPORT FORMATS
The KR should be able to import information models, and their model elements, from a range of formats. Users would like it to be as easy as possible to register models into the KR. Once in the KR the data elements from these models would be immediately available for use. Optionally, they may then by refined and passed through the appropriate governance process to become curated models.
NB: THIS IS NOT AN EXHAUSTIVE ENUMERATION OF IMPORT FORMATS
Images and other representations of static content
Capabilities
Requirements traceability
Requirement |
Source |
Capability |
|---|---|---|
Import local value domains into the modeling tool |
Gap Analysis::Import::022 - Import Localized Value Domains |
|
Support providing data elements in multiple formats and standards schema |
Gap Analysis::Export::052 - Multiple Formats |
|
Express ValueDomains as either XSD, RDF or OWL |
Gap Analysis::Export::076 - Value Domain Expressions |
|
Provide alternative consistent data / information model representations to best suit stakeholders' implementation needs |
Gap Analysis::Export::160 - Multiple Information Model Representations |
|
The Clinical Trials industry makes extensive use of tabular formats. They do a lot of work in Excel and in other 2-dimensional tabular formats in general (e.g., SAS, Oracle). This format is also used to analyze clinical trial data, it is generally how clinical trials capture, store, and present data. Thus the tabular formats have to be supported. However, the CDISC intent is to support other formats and perhaps move away from the tabular formats. *Source: * * 5/20/2010 Interview, David Iberson-Hurst |
Gap Analysis::CDISC::CDISC-12 - Support tabular formats and emerging formats |
|
CDISC metadata, which is the focus of CDISC standards, should be computer-tractable. This means that CDISC standards should support computer semantic interoperability (CSI) and be available through services. Per Model Driven Architecture (MDA), metadata are context-defining data about data. This includes the standard data element names, data types, and lengths are well as provenance models, models of executable business processes, data about interfaces/APIs, configuration information, data transformation rules, etc. *Source: * * 5/20/2010 Interview, David Iberson-Hurst |
Gap Analysis::CDISC::CDISC-14 - Provide CDISC metadata in machine-interpretable formats |
|
There is a need for the appropriate users to be able to review and retrieve (import) through various medium applicable data elements for file formats such as xls spreadsheets, xml, csv. text, pdf. |
Gap Analysis::HL7 CIC::CIC-5 - Provide data element definitions in multiple formats |
|
Content includes all unstructured text and other forms of content that make up a service specification. Examples include storyboards, and scope. Content is an integral part of service specification, and content is leveraged across the enterprise for documentation and communicaitons. |
Semantic Infrastructure Requirements::Artifact Management::Content |
|
This set of requirements includes providing an application developer with the ability to define application-specific attributes (for example, defined using ISO 21090 healthcare datatypes) and an information model that defines the relationships between these attributes and other attributes in the broader ecosystem. In particular, the last requirement suggests linked datasets, where application developers can connect data in disparate repositories as if the repositories are part of a larger federated data ecosystem. Additional requirements include the ability to publish and discover information models. Support is needed for forms data and common clinical document standards, such as HL7 CDA. To support the use of binary data throughout the system, the binary data must be typed and semantically annotated. All Information models, their representation and binding to data-types and terminologies will be managed by the semantic infrastructure. The ability to publish and discover information models will be supported by the semantic infrastructure, and the platform will leverage these capabilities. Link to use case satisfied from caGRID 2.0 Roadmap: The pathology, radiology and other data have various data formats which must be described, and the information model for the patient record must link between these various datatypes. The complete information model includes semantic links between datasets to build a comprehensive electronic medical record. Annotations on data are defined and included in the information model. |
Semantic Infrastructure Requirements::caGRID 2.0 Platform and Terminology Integration::Data Representation and Information Models |
dataElementDefinitionFormats, localizeValueDomains, tabularFormats, |
dataElementDefinitionFormats
Description
Provide data element definitions in multiple formats
Support providing data elements in multiple formats and standards schema.
Provide metadata in machineinterpretable formats
Provide alternative consistent data / information model representations to best suit stakeholders' implementation needs
Express ValueDomains as either XSD, RDF or OWL
Requirements addressed
- 052 - Multiple Formats
- Data Representation and Information Models
- CIC-5 - Provide data element definitions in multiple formats
- CDISC-14 - Provide CDISC metadata in machine-interpretable formats
- 160 - Multiple Information Model Representations
- 076 - Value Domain Expressions
Overview of possible operations
imageManagement
Description
Management of image and other non-text, unstructured resources
Requirements addressed
Overview of possible operations
localizeValueDomains
Description
Import local value domains into the modeling tool
Requirements addressed
Overview of possible operations
tabularFormats
Description
Support tabular formats and emerging formats.
