 |
Page History
...
Forms include CDISC Operational Data Model (ODM), HL7 Clinical Document Architecture Architecture (CDA) documents, and HL7 Version 3 RIM derived forms. This includes all aspects of the document including the style, definitions and semantics.
...
- 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 representation 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
- Provide rules and algorithms for the use of the artifacts in a particular service
...
The artifact management requirements listed above are derived from the following use cases in the previous section:
caEHRElectronic Health Records: The caEHR caBIG® Clinical Information Suite project has adopted ECCF for specifications and CDA documents for interoperability. The caEHR project 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 must support better discovery, making all the relevant information available in the right context.
...
The requirements listed above are derived from the following use cases in the previous section:
caEHRElectronic Health Records: The caEHR caBIG® Clinical Information Suite project is developing service specifications and lacks the infrastructure to govern these services. Vendors and external implementations are expected to leverage the caEHR caBIG® Clinical Information Suite service specifications and there is currently no infrastructure that allows easy discovery and consumption of this information.
...
caGRID 2.0 Platform: The caGRID 2.0 Platform provides a runtime registry for service discovery. This service registry relies on a small subset of information for discovery. The semantic infrastructure provides a mechanism to leverage rich service and artifact metadata to extend this capability.
Clinical Data Forms Data Forms Definition and Modeling
Clinical Data Forms Data Forms are the primary channel for capturing information in the healthcare and clinical domain. Forms also play a key role in information exchange and are critical to supporting interoperability in healthcare.
...
The requirements listed above are derived from the following use cases in the previous section:
- caEHRElectronic Health Records
- ONC and Other external EHR adopters
- Clinical Trails
...
To support the decision-support functions of the ECCF registry,, and and reusable rules are part of the artifacts that need to be stored in the registry and linked to specific services.Links to use cases: caEHR enterprise use cases and clinical trials use cases.
The requirements listed above are derived from the following use cases:
- Electronic Health Records
- Clinical Trials
Conformance Testing
Services specifications developed by NCI and the community have to be testable to ensure that the implementation conforms to the specification.
...
The requirements listed above are derived from the following use cases in the previous section:
CBIIT's adoption of ECCF: ECCF requires all specification developers to make conformance statements, the conformance testing framework leverages these conformance statements to generate validation tests.
...
