 |
Page History
...
| Children Display |
|---|
| Page info | ||||
|---|---|---|---|---|
|
...
Summary
Description of the profile
Create, destroy, edit, and maintain models.
...
Vocabulary models.
XML Schemas.
This Functional Profile includes, but is not limited to, the following capability elaborations:
- cdiscModel
- hl7CdaModel
- hl7Model
- saifModel
- metaModel
- orchestrationModel
- unstructuredDocument
- umlModel
- vocabularyModel
- schemaModel
Derived From Requirements
- 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.
- Semantic Infrastructure Requirements::Artifact Management::Behavioral Models Behavioral dynamic models capture the behavior of services. Behavior of services provides an unambiguous definition of the service constraints, capabilities, dependencies and interactions. The metadata and grammar required to realize service behavior is called behavioral semantics. Behavioral semantics provide a mechanism for better service discovery and enforcing the constraints at design and runtime.
- 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.
- Gap Analysis::caEHR::caEHR 2 - CDA,CCD Document Handling caEHR performs many of the behavior functions via the creation and parsing of clinical documents in the HL7 CDA format. While other methods exist, the KR system should provide the ability to represent the content structure of standard documents in such a way as to assist in the generation and understanding of these documents. CDA documents have sections that are composed of defined clinical statements. These sections and statements are derived from HL7 definitions. The definition of a document should be made available via the KR system. This includes constraints on certain elements for a given section. For example, if a section contains the set of declared allergies for a patient, then the KR system should identify the component elements, and the constrained value sets for representing allergies. The CDA document also has the ability to express information using negation indicators. As in, a patient does not have a specific symptom. The KM system should allow for the definition of alternate representations of such elements so as to allow for consistent understanding and transformations of such elements. That would be one requirement, but probably the function of the CTS2 service. The negationInd attribute is just another attribute in a V3 class and requires no special handling from the metadata repository.
- Gap Analysis::CDISC::CDISC-13 - Provide the ability to retrieve CDISC Standards in a machine interpretable format CDISC has to deliver its standards and the MDR approved content to the authorized CDISC member. Currently a major format for clinical trial data delivery is PDF. The PDF publication format is gradually expected to fade. A CDISC Knowledge Repository should support Files and Services to distribute information. In particular, the existing CDISC standards should be aligned with each other; this includes CDASH, SDTM, BRIDG, and Controlled Terminology. The knowledge repository should make it easy to consume this metadata information and provide detailed explanations to the membership in real-time. This is a major issue because shifting to the use of CDISC standards or using updated CDISC standards can turn the world of a clinical research project upside down. CDISC needs to be able to explain and justify the changes the use of CDISC standards would mandate (e.g., switch from PDF to CDASH). The CDISC meta-model explicitly calls for the storage of SDTM, CDASH, and ADaM and that these standards should be derivable from an underlying BRIDG-based meta-model. The KR should be able to export all or subsets of its content in a machine-readable format (e.g., XML, ASCII). Source * CDISC SHARE Meta Data Model, V 0.1 May 7, 2010 CDISC Share Pilot Report and CDISC Requirements Package 1 - NCI Semantic Infrastructure, 5/28/2010, Section 2.2 * 5/20/2010 Interview, David Iberson-Hurst in response to a David Hau question.
- Gap Analysis::CDISC::CDISC-7 - Support the meta-model being developed by CDISC SHARE CDISC is developing a meta-model for CDISC Share. These meta-model requirements should be supported in the NCI Knowledge Repository. This meta-model shall support ISO 11179, which provides the foundation for data elements and concepts. ISO 21090 data types are the foundation for repository data types. As noted in CDISC-8 BRIDG concepts are also a foundation for the repository objects. This repository should include object names, attributes. The attributes include variable definitions, code lists, data types (e.g., ISO 21090), object variable groupings, observation classes, observation class attributes, observation class rules, special purpose classes, domain level attributes, domain level rules, domain level examples, object level rules, relationships among objects, object level examples, define file rules, and define file examples. The relationships between each object should be fully specified. This also includes the requirement that every object (e.g., class, attribute, association, concept, term) in the repository must have a definition. The meta-model defines the structures and rules used to define CDISC standards. It outlines how clinical research and treatment firms, health agencies and regulators should gather, retain, and disseminate health domain specific knowledge. The repository also provides content governance support mechanisms. Sources * CDISC SHARE Meta-Model Paper; CDISC Share Pilot Report and CDISC Requirements Package 1 - NCI Semantic Infrastructure, 5/28/2010, Section 2.1; Section 2.6 * CDISC Team 2 Meetiing 5/27/2010 , David Iberson-Hurst
- Gap Analysis::CDISC::CDISC-8 - Support the BRIDG (Biomedical Research Integrated Domain Group) Domain Analysis Model (DAM) The BRIDG DAM is designed to integrate clinical research trial and clinical care domains so that research results can inform healthcare more quickly and so that healthcare outcomes can be used in designing clinical trial protocols. The goal is to enable information system interoperability to improve both medical research and related areas of healthcare. BRIDG already incorporates a number of CDISC standards (e.g., STDM) and is working to harmonize other CDISC standards. *Source: * * CDISC SHARE: A Briefing on CDISC Share, Oct 6, 2009 E. Helton, R Kush, F Newby, M Haber, & D Iberson-Hurst; * CDISC SHARE: Pathway into the Future for Standards Development and Delivery, April 10, 2010, Brow W. Kisler, CDISC Senior Director
- Gap Analysis::HL7 CIC::CIC-11 - Support reuse of existing vocabularies to build new vocabularies There is a need to support a feature, like a shopping cart in caDSR, to allow for building of streams (data collection of screens) from existing vocabularies – consider looking at using caDSR Forms to do this
- Gap Analysis::HL7 CIC::CIC-9 - Provide a common interface for different clinical specialties There is a need to permit the user to enter data from their perspective, but have the entered data converted into a standard and consistent metadata format.
- Semantic Infrastructure Requirements::Artifact Management::Content 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::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.
- 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.
- Gap Analysis::EVS::EVS-2 - Implement HL7 formal naming conventions KR needs to implement metadata object names that bind to HL7 version 3 artifacts according to the HL7 formal naming conventions
- 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.
- Semantic Infrastructure Requirements::Conformance Testing::Test for Conformance Conformance testing allows both CBIIT and other HL7 SAIF adopters to validate specifications.
.
An artifact is a managed resource within the Semantic Infrastructure.
An artifact is associated with the following capabilities:
- descriptions to enable the artifact to be visible, where the description includes a unique identifier for the artifact and a sufficient, and preferably a machine processible, representation of the meaning of terms used to describe the artifact, its functions, and its effects;
- one or more discovery mechanisms that enable searching for artifacts that best meet the search criteria specified by the service participant; where the discovery mechanism will have access to the individual artifact descriptions, possibly through some repository mechanism;
- accessible storage of artifacts and artifact descriptions, so service participants can access, examine, and use the artifacts as defined.
Artifact descriptions change over time and their contents will reflect changing needs and context.
Architectural implications of change on the Semantic Infrastructure are reflected in the following capabilities:
- mechanisms to support the storage, referencing, and access to normative definitions of one or more versioning schemes that may be applied to identify different aggregations of descriptive information, where the different schemes may be versions of a versioning scheme itself;
- configuration management mechanisms to capture the contents of the each aggregation and apply a unique identifier in a manner consistent with an identified versioning scheme;
- one or more mechanisms to support the storage, referencing, and access to conversion relationships between versioning schemes, and the mechanisms to carry out such conversions.
Artifact Descriptions make use of defined semantics, where the semantics may be used for categorization or providing other property and value information for description classes.
Architectural implications of semantics on the Semantic Infrastructure are reflected in the following capabilities:
- semantic models that provide normative descriptions of the utilized terms, where the models may range from a simple dictionary of terms to an ontology showing complex relationships and capable of supporting enhanced reasoning. This is a refinement of the Artifact metadata capability.
- mechanisms to support the storage, referencing, and access to these semantic models. This is a refinement of the Artifact store capability.
- configuration management mechanisms to capture the normative description of each semantic model and to apply a unique identifier in a manner consistent with an identified versioning scheme. This is a refinement of the Change configurationManagement capability.
- one or more mechanisms to support the storage, referencing, and access to conversion relationships between semantic models, and the mechanisms to carry out such conversions.
Capabilities
- cdiscModel
- configurationManagement
- discovery
- hl7CdaModel
- hl7Model
- identity
- metadata
- metaModel
- orchestrationModel
- provenance
- saifModel
- schemaModel
- semanticConversion
- store
- transition
- umlModel
- unstructuredDocument
- versioning
- vocabularyModel
Requirements traceability
Requirement | Source | Capability | ||||||
|---|---|---|---|---|---|---|---|---|
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. | Semantic Infrastructure Requirements::Artifact Management::
| |||||||
Behavioral dynamic models capture the behavior of services. Behavior of services provides an unambiguous definition of the service constraints, capabilities, dependencies and interactions. The metadata and grammar required to realize service behavior is called behavioral semantics. Behavioral semantics provide a mechanism for better service discovery and enforcing the constraints at design and runtime. | Semantic Infrastructure Requirements::Artifact Management::
| |||||||
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. | Gap Analysis::BRIDG::
| |||||||
caEHR performs many of the behavior functions via the creation and parsing of clinical documents in the HL7 CDA format. While other methods exist, the KR system should provide the ability to represent the content structure of standard documents in such a way as to assist in the generation and understanding of these documents. CDA documents have sections that are composed of defined clinical statements. These sections and statements are derived from HL7 definitions. The definition of a document should be made available via the KR system. This includes constraints on certain elements for a given section. For example, if a section contains the set of declared allergies for a patient, then the KR system should identify the component elements, and the constrained value sets for representing allergies. The CDA document also has the ability to express information using negation indicators. As in, a patient does not have a specific symptom. The KM system should allow for the definition of alternate representations of such elements so as to allow for consistent understanding and transformations of such elements. That would be one requirement, but probably the function of the CTS2 service. The negationInd attribute is just another attribute in a V3 class and requires no special handling from the metadata repository. | Gap Analysis::caEHR::
| |||||||
CDISC has to deliver its standards and the MDR approved content to the authorized CDISC member. Currently a major format for clinical trial data delivery is PDF. The PDF publication format is gradually expected to fade. A CDISC Knowledge Repository should support Files and Services to distribute information. In particular, the existing CDISC standards should be aligned with each other; this includes CDASH, SDTM, BRIDG, and Controlled Terminology. The knowledge repository should make it easy to consume this metadata information and provide detailed explanations to the membership in real-time. This is a major issue because shifting to the use of CDISC standards or using updated CDISC standards can turn the world of a clinical research project upside down. CDISC needs to be able to explain and justify the changes the use of CDISC standards would mandate (e.g., switch from PDF to CDASH). The CDISC meta-model explicitly calls for the storage of SDTM, CDASH, and ADaM and that these standards should be derivable from an underlying BRIDG-based meta-model. The KR should be able to export all or subsets of its content in a machine-readable format (e.g., XML, ASCII). Source * CDISC SHARE Meta Data Model, V 0.1 May 7, 2010 CDISC Share Pilot Report and CDISC Requirements Package 1 - NCI Semantic Infrastructure, 5/28/2010, Section 2.2 * 5/20/2010 Interview, David Iberson-Hurst in response to a David Hau question. | Gap Analysis::CDISC::
| |||||||
CDISC is developing a meta-model for CDISC Share. These meta-model requirements should be supported in the NCI Knowledge Repository. This meta-model shall support ISO 11179, which provides the foundation for data elements and concepts. ISO 21090 data types are the foundation for repository data types. As noted in CDISC-8 BRIDG concepts are also a foundation for the repository objects. This repository should include object names, attributes. The attributes include variable definitions, code lists, data types (e.g., ISO 21090), object variable groupings, observation classes, observation class attributes, observation class rules, special purpose classes, domain level attributes, domain level rules, domain level examples, object level rules, relationships among objects, object level examples, define file rules, and define file examples. The relationships between each object should be fully specified. This also includes the requirement that every object (e.g., class, attribute, association, concept, term) in the repository must have a definition. The meta-model defines the structures and rules used to define CDISC standards. It outlines how clinical research and treatment firms, health agencies and regulators should gather, retain, and disseminate health domain specific knowledge. The repository also provides content governance support mechanisms. Sources * CDISC SHARE Meta-Model Paper; CDISC Share Pilot Report and CDISC Requirements Package 1 - NCI Semantic Infrastructure, 5/28/2010, Section 2.1; Section 2.6 * CDISC Team 2 Meetiing 5/27/2010 , David Iberson-Hurst | Gap Analysis::CDISC::
| |||||||
The BRIDG DAM is designed to integrate clinical research trial and clinical care domains so that research results can inform healthcare more quickly and so that healthcare outcomes can be used in designing clinical trial protocols. The goal is to enable information system interoperability to improve both medical research and related areas of healthcare. BRIDG already incorporates a number of CDISC standards (e.g., STDM) and is working to harmonize other CDISC standards. *Source: * * CDISC SHARE: A Briefing on CDISC Share, Oct 6, 2009 E. Helton, R Kush, F Newby, M Haber, & D Iberson-Hurst; * CDISC SHARE: Pathway into the Future for Standards Development and Delivery, April 10, 2010, Brow W. Kisler, CDISC Senior Director | Gap Analysis::CDISC::
| |||||||
There is a need to support a feature, like a shopping cart in caDSR, to allow for building of streams (data collection of screens) from existing vocabularies – consider looking at using caDSR Forms to do this | Gap Analysis::HL7 CIC::
| |||||||
There is a need to permit the user to enter data from their perspective, but have the entered data converted into a standard and consistent metadata format. | Gap Analysis::HL7 CIC::
|
...
|
...
|
...
|
...
|
...
HL7 CDA Model management, including create, destroy, edit.
caEHR performs many of the behavior functions via the creation and parsing of clinical documents in the HL7 CDA format. While other methods exist, the KR system should provide the ability to represent the content structure of standard documents in such a way as to assist in the generation and understanding of these documents.
CDA documents have sections that are composed of defined clinical statements. These sections and statements are derived from HL7 definitions. The definition of a document should be made available via the KR system. This includes constraints on certain elements for a given section. For example, if a section contains the set of declared allergies for a patient, then the KR system should identify the component elements, and the constrained value sets for representing allergies.
The CDA document also has the ability to express information using negation indicators. As in, a patient does not have a specific symptom. The KM system should allow for the definition of alternate representations of such elements so as to allow for consistent understanding and transformations of such elements.
That would be one requirement, but probably the function of the CTS2 service. The negationInd attribute is just another attribute in a V3 class and requires no special handling from the metadata repository.
There is a need to permit the user to enter data from their perspective, but have the entered data converted into a standard and consistent metadata format.
|
...
CDISC Model API
...
| ||||||||
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::
| |||||||
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:: |
|
...
|
...
|
...
|
...
|
...
|
...
HL7 Model maintenance
KR needs to implement metadata object names that bind to HL7 version 3 artifacts according to the HL7 formal naming conventions
...
| ||||||||
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::caGRID 2.0 Platform and Terminology Integration::
| |||||||
KR needs to implement metadata object names that bind to HL7 version 3 artifacts according to the HL7 formal naming conventions | Gap Analysis::EVS::
| |||||||
| Semantic Profile::OASIS SOA::
| discovery from inherited abstract profile Artifact, identity from inherited abstract profile Artifact, metadata from inherited abstract profile Artifact, store from inherited abstract profile Artifact, | ||||||
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::Conformance Testing::
| |||||||
| Semantic Profile::OASIS SOA::
| versioning from inherited abstract profile Change, configurationManagement from inherited abstract profile Change, transition from inherited abstract profile Change, discovery from inherited abstract profile Artifact, identity from inherited abstract profile Artifact, metadata from inherited abstract profile Artifact, store from inherited abstract profile Artifact, semanticConversion from inherited abstract profile Semantic Model, | ||||||
Static models include a variety of models with different representations. | Semantic Infrastructure Requirements::Artifact Management::
| vocabularyModel, hl7Model, metaModel, umlModel, schemaModel, | ||||||
Conformance testing allows both CBIIT and other HL7 SAIF adopters to validate specifications. | Semantic Infrastructure Requirements::Conformance Testing::
|
| Anchor | ||||
|---|---|---|---|---|
|
Description
CDISC Model API
Requirements addressed
- CDISC-13 - Provide the ability to retrieve CDISC Standards in a machine interpretable format
- CDISC-7 - Support the meta-model being developed by CDISC SHARE
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Mechanisms to support the storage, referencing, and access to normative definitions of one or more versioning schemes that may be applied to identify different aggregations of descriptive information, where the different schemes may be versions of a versioning scheme itself.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
One or more discovery mechanisms that enable searching for artifacts that best meet the search criteria specified by the service participant; where the discovery mechanism will have access to the individual artifact descriptions, possibly through some repository mechanism.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
HL7 CDA Model management, including create, destroy, edit.
caEHR performs many of the behavior functions via the creation and parsing of clinical documents in the HL7 CDA format. While other methods exist, the KR system should provide the ability to represent the content structure of standard documents in such a way as to assist in the generation and understanding of these documents.
CDA documents have sections that are composed of defined clinical statements. These sections and statements are derived from HL7 definitions. The definition of a document should be made available via the KR system. This includes constraints on certain elements for a given section. For example, if a section contains the set of declared allergies for a patient, then the KR system should identify the component elements, and the constrained value sets for representing allergies.
The CDA document also has the ability to express information using negation indicators. As in, a patient does not have a specific symptom. The KM system should allow for the definition of alternate representations of such elements so as to allow for consistent understanding and transformations of such elements.
That would be one requirement, but probably the function of the CTS2 service. The negationInd attribute is just another attribute in a V3 class and requires no special handling from the metadata repository.
There is a need to permit the user to enter data from their perspective, but have the entered data converted into a standard and consistent metadata format.
Requirements addressed
- CIC-9 - Provide a common interface for different clinical specialties
- caEHR 2 - CDA,CCD Document Handling
- Data Representation and Information Models
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
HL7 Model maintenance
KR needs to implement metadata object names that bind to HL7 version 3 artifacts according to the HL7 formal naming conventions
Requirements addressed
- Data Semantics
- EVS-2 - Implement HL7 formal naming conventions
- Search and Access Conformance Statements
- Static Models
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Descriptions which include a unique identifier for the artifact.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
A representation of the meaning of terms used to describe the artifact, its functions, and its effects.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Meta Model maintenance
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Orchestration Model maintenance
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
While the Resource identity provides the means to know which subject and subject description are being considered, Provenance as related to the Description class provides information that reflects on the quality or usability of the subject. Provenance specifically identifies the entity (human, defined role, organization, ...) that assumes responsibility for the resource being described and tracks historic information that establishes a context for understanding what the resource provides and how it has changed over time. Responsibilities may be directly assumed by the Stakeholder who owns a Resource or the Owner may designate Responsible Parties for the various aspects of maintaining the resource and provisioning it for use by others. There may be more than one entity identified under Responsible Parties; for example, one entity may be responsible for code maintenance while another is responsible for provisioning of the executable code. The historical aspects may also have multiple entries, such as when and how data was collected and when and how it was subsequently processed, and as with other elements of description, may provide links to other assets maintained by the Resource owner.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
SAIF Model maintenance
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Schema Model maintenance
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
One or more mechanisms to support the storage, referencing, and access to conversion relationships between semantic models, and the mechanisms to carry out such conversions.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Accessible storage of artifacts and artifact descriptions, so service participants can access, examine, and use the artifacts as defined.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
One or more mechanisms to support the storage, referencing, and access to conversion relationships between versioning schemes, and the mechanisms to carry out such conversions.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
UML Model maintenance
The BRIDG DAM is designed to integrate clinical research trial and clinical care domains so that research results can inform healthcare more quickly and so that healthcare outcomes can be used in designing clinical trial protocols. The goal is to enable information system interoperability to improve both medical research and related areas of healthcare. BRIDG already incorporates a number of CDISC standards (e.g., STDM) and is working to harmonize other CDISC standards.
Requirements addressed
- Static Models
- CDISC-8 - Support the BRIDG (Biomedical Research Integrated Domain Group) Domain Analysis Model (DAM)
Overview of possible operations
...
SAIF Model maintenance
...
Meta Model maintenance
...
| Anchor | ||||
|---|---|---|---|---|
|
Description
Service specification content, primarily unstructured text
Requirements addressed
Overview of possible operations
| Anchor | ||
|---|---|---|
|
...
|
...
|
...
|
...
|
...
|
...
|
Description
Configuration management mechanisms to capture the contents of the each aggregation and apply a unique identifier in a manner consistent with an identified versioning scheme.
Requirements addressed
Overview of possible operations
...
UML Model maintenance
...
| Anchor | ||||
|---|---|---|---|---|
|
Vocabulary Model maintenance
...
|
Description
Vocabulary Model maintenance
Support reuse of existing vocabularies to build new vocabularies.
Requirements addressed
- BRIDG-2 - Handle ISO-11179 specification handling of early binding of attribute context
- Data Semantics
- Search and Access Conformance Statements
- Static Models
- Artifact Lifecycle Management
- CIC-11 - Support reuse of existing vocabularies to build new vocabularies
...
Overview of possible operations
...
| Scrollbar |
|---|
