Publish and Discover Information Models Functional Profile
The ability to publish and discover information models will be supported by the semantic infrastructure, and the platform will leverage these capabilities.
This Functional Profile includes, but is not limited to, the following capability elaborations:
Derived From Requirements
- Gap Analysis::Manage::006 - Sandboxed Data Elements and Concepts Allow model owners to create sandboxed data elements and concepts as necessary to use in their models
- Gap Analysis::Import::040 - Load Models Directly to KR Provide mechanism for users to load their model directly into the KR – instead of the curators and model owners doing the data load
- Gap Analysis::Import::050 - Bulk,batch load Provide the capability to bulk/batch load new content from a variety of sources for later curation.
- Gap Analysis::Import::098.3 - Line of Business Artifacts Provide an easy way to create data elements from line of business artifacts such as a spreadsheet or database description
- Semantic Infrastructure Requirements::Artifact Management::Artifact Lifecycle Management Artifact lifecycle management and metadata requirements include the ability to: * Manage lifecycle, governance and versioning of the models, content and forms * Establish relationships and dependencies between models, content and forms * Determine provenance, jurisdiction, authority and intellectual property * Create represention and views of the information, realized through the appropriate transforms * Provide access control and other security constraints * Create annotations for better discovery and searching of artifacts * Develop usage scenarios and context for the information * Provide terminology and value set binding The artifacts are bound to the services via the service metadata. The service metadata combined with the artifacts and supporting metadata provide a comprehensive service specification. The artifact management requirements listed above are derived from the following use cases: * caEHR: The caEHR project has adopted ECCF for specifications and CDA documents for interoperability. The caEHR project requirements include the need for an infrastructure for managing all the artifacts generated during specification process, including HL7 models and documents. The caEHR project also intends to publish these artifacts for the community and vendors. The infrastructure needs to support better discovery, making all the relevant information available in the right context. * ONC and other external EHR adopters: ONC has adopted CCD and CCR for meaningful use. All national EHR implementations are expected to support forms and the semantics of these forms play a critical role in interoperability. The semantic infrastructure must provide a mechanism to create, store and manage these forms. * Clinical Trials: Clinical trials use forms to capture clinical information, and the semantics captured by these forms are critical for interoperability and reporting. The semantic infrastructure must provide a mechanism to manage the lifecycle of these forms.
- Gap Analysis::HL7 CIC::CIC-1 - Store clinical data elements in a publicly available repository CIC wants to be able to register and maintain the clinical data elements in a publicly available repository,
- Semantic Infrastructure Requirements::caGRID 2.0 Platform and Terminology Integration::Data Representation and Information Models 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.
lineOfBusinessArtifacts
Provide an easy way to create data elements from line of business artifacts such as a spreadsheet or database description
batchLoadCurationArtifacts
Provide the capability to bulk/batch load new content from a variety of sources for later curation.
localizeDataElements
Allow model owners to create sandboxed data elements and concepts as necessary to use in their models
Provide mechanism for users to load their model directly into the KR – instead of the curators and model owners doing the data load
clinicalDataElements
Store clinical data elements in a publicly available repository.
