Bind Models Functional Profile
Bind models to data types and value sets.
Data Type, terminology, vocabulary models.
Provide terminology and value set binding.
Develop usage scenarios and context for the information.
This Functional Profile includes, but is not limited to, the following capability elaborations:
Derived From Requirements
- Gap Analysis::Service::064 - Terminology Service Metadata Metadata about terminology services should include; descriptions of the algorithms/methods using controlled vocabularies, keyword assignments to inputs and outputs, description of domains/subdomains service serves for using controlled vocabularies
- Gap Analysis::Transform::093 - HL7 Complex Data Types Support complex data types as required by the HL7 V3 standard. Due to the large installed base of HL7 V2 compliant products support datatypes defined in the V2 specification.
- Gap Analysis::BRIDG::BRIDG-2 - Handle ISO-11179 specification handling of early binding of attribute context The ISO-11179 metadata specification specifies that a concept definition should be applied to each data element concept that is rigorous, noncircular, and granular enough to separate the definition of the concept in question from a closely related concept. When the concept definition that is applied to a data element concept is so specific that it attempts to disambiguate not just related concepts, but different uses of the same concept, it creates a situation of early binding of the concept definition that prevents its reuse in a broader manner. In the case of a domain analysis model that is meant to be abstract, this early binding prevents the reuse of domain analysis attributes across a broad range of use cases and leads to segregation of an individual concept into multiple sub concepts usable only in extremely narrow use cases, outside the scope of a domain analysis model representation.
- Semantic Infrastructure Requirements::caGRID 2.0 Platform and Terminology Integration::Data Semantics In a diverse information environment, semantics must be used to clearly indicate the meaning of data. This requirement is expected to be addressed by the Semantic Infrastructure, although there will be a touchpoint between the caGrid 2.0 and the Semantic Infrastructure to annotate data with semantics. Integration with the Semantic Infrastructure will enable reasoning, semantic query, data mediation (for example, ad hoc data transformation) and other powerful capabilities. Data semantics are captured in the Semantic Infrastructure and the platform will leverage the Semantic Infrastructure interfaces for reasoning and analysis. Link to use case satisfied from caGRID 2.0 Roadmap: The oncologist accesses the TCGA database to search for de-identified glioblastoma tumor data that is similar to the patient data exported from the hospital medical record. During this search, the semantics of the data fields are leveraged to indicate matches between TCGA data fields and the hospital medical record data fields.
- Semantic Infrastructure Requirements::Conformance Testing::Search and Access Conformance Statements Conformance testing leverages the artifact and service metadata to validate that an implementation adequately addresses the requirements stated in the service specification. An example of service requirement is the ability to specify a response time in the specification (design time) and validate that this response time is valid for an implementation of the service. Aadditional test points include but are not limited to binding to specific terminologies and domain models.
- Semantic Infrastructure Requirements::Artifact Management::Static Models Static models include a variety of models with different representations.
terminologyModel
Terminology Model maintenance
dataTypesModel
Data types Model maintenance
Support complex data types as required by the HL7 V3 standard. Due to the large installed base of HL7 V2 compliant products support datatypes defined in the V2 specification.
