This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
• Enables precise communication between business users and technical experts & enterprise applications and their respective business partner systems
• Involves a layered approach for strategically managing Service Oriented Architecture artifacts and constraints while achieving semantic interoperability
• A Federated Knowledge Registry not only acts as an interface to a Repository of stored content, it formalises how information is to be registered and shared beyond a single enterprise or agency.
• Specifically, a Federated Registry & Repository capability is required when there is a need for managing and accessing metadata across physical boundaries in a secure manner. Those physical boundaries might be the result of community-of-interest, line of business, system, department, or enterprise separation.
• Irrespective of the boundary type, a Federated Registry & Repository must enable users to seamlessly access, share and perform analysis on information, including :
– Maps of information dependencies across workflow
– evidence of quality, statements of provenance and assurance– policies supporting security and privacy requirements e.g. HIPAA.
NIST HL7 e-COI Registry of DMIMs, RMIMs, HMDs, and MessageTypes
• HL7-specific classification schemes, especially the code hierarchies for the structural attributes in the RIM.
• RMIM static models from technical domains, including finance, Patient Administration, Scheduling, Laboratory Orders, Research Trials, Pharmacy, Medical Records, Common Message Types, Message Control, Master File, and Clinical Documents
• RMIM static models from the CMETs domain, each with a an association to the DMIM it is derived from (using external identifiers to the HL7 identification schemes) with external links to diagrams and descriptions, and a number of classifications by specific codes that are fixed by constraints on the RMIM.
• RMIMs leads to one or more derived HMDs and MessageTypes.• Each registered artifact has ExternalLinks to its base UML diagrams, long html
descriptions, and other visual display aids for presentation of base classes, attributes, relationships, and constraints.
• OWL-related template artifacts submitted by HL7 participants active in the Templates technical committee
• The XDS Cross Enterprise Clinical Documents Sharing profile defines the (document) Registry as an actor that maintains metadata about each registered document in a document entry & enforces policies at the time of document registration
• An XDS Document is a composition of clinical information that contains observations and services for the purpose of exchange with the following characteristics: Persistence, Stewardship, Potential for Authentication, and Wholeness (characteristics that are well defined in the HL7 CDA)
• An XDS Folder provides a collaborative mechanism for several XDS Document Sources to group XDS Documents for a variety of reasons. XDS Documents may be placed into an existing Folder at any time, as long as they relate to the same patient.
• A Document Source may only contribute documents with Document Codes and Health Facility Codes that draw from a Vocabulary Value Set that is approved by the Affinity Domain.
Ontology & other Semantic Content Considerations ….. artifacts that help agents communicate, coordinate, collaborate XML provides syntax for structured documents, but imposes no
semantic constraints on the meaning of these documents.
XML Schema is a language for restricting the structure of XML documents and also extends XML with datatypes.
RDF is a data model for resources and relations between them.
RDF Schema is a vocabulary for describing properties and classes of RDF resources, with a semantics for generalization-hierarchies of such properties and classes.
• OWL adds more vocabulary for describing properties and classes e.g. relations between classes, cardinality, equality.
• SKOS-Core is an [RDF & OWL] schema for representing controlled vocabularies and other types of Simple Knowledge Organization Systems .
COI CHI (Consolidated Health Informatics) portfolio of Clinical Vocabularies
• National Council on Prescription Drug Programs (NCDCP) standards for ordering drugs from retail pharmacies.
• The Institute of Electrical and Electronics Engineers 1073 (IEEE1073) series of standards that allow for health care providers to plug medical devices into information and computer systems
• Digital Imaging Communications in Medicine® (DICOM®) standards that enable images and associated diagnostic information to be retrieved and transferred from various manufacturers' devices
• Laboratory Logical Observation Identifier name Codes® (LOINC®) to standardize the electronic exchange of clinical laboratory results.
• Template & Archetype Choice Points significantly aids to comprehensibility, alignment, while promoting tracing and accountability when : – archetype is a computable expression of a domain level (clinical)
concept in the form of structured constraint statements, based on some reference model (RMIM)
– archetypes are aligned with Affinity Domain concepts
– archetypes all have the same formalism i.e. may be part of a COP ontology but belong to only one or other ontological level
– template is used to narrow the choices of archetypes for local or specific purposes (DMIM).
– archetype defines constraints on reference model instances which express valid structure (i.e. composition, cardinality).
– archetype defines constraints on instances of a reference model which express valid types and values.
• e-Health service information can be managed by two different e-Health service entities using different message structures.
• ARTEMIS project providing a standard way of accessing the data by registering & storing – ontologies based on existing healthcare standards,
– the semantic mapping between these ontologies,
– invoke each others web services by semantic mediation.
• Discovery of Services stored in a Registry need semantic service registry query mechanisms that leverage previous research linking OWL to the Registry Information Model