Skip to end of metadata
Go to start of metadata

Information Moving

This information will be moving to version 4.0 of the OpenHIE Architecture Specification


 IHE Data Exchange Standards Overview  

The following are the IHE profiles that OpenHIE is working toward demonstrating or has demonstrated as supported in reference implementations.  However, the OpenHIE architecture is not limited to supporting these profiles.  For documentation on IHE conformance testing for the profiles supported, see the OpenHIE IHE Conformance Statements.  For more information about the OpenHIE workflows that utilize these standards and profiles, see the OpenHIE Workflow Collection Maturity documentation which describes the OpenHIE workflow collections.  

ADXThe Aggregate Data Exchange (ADX) Profile enables interoperable public health reporting of aggregate health data. ADX will typically be used to represent routinely reported aggregate data such as the numerators and denominators which can be used in the construction of public health indicators.
ADX-HIVThe ADX (Aggregate Data Exchange) profile affords data exchange partners a way to define a Data Structure Definition and the associated normative schema of the data message for a particular indicator report. To foster further adoption, the Aggregate Data Exchange-HIV (ADX-HIV) profile leverages the ADX profile version 2.1, which is currently published for trial implementation, to develop a content specification specifically for HIV.
APSThe APS document is a medical summary and inherits all header constraints from Medical Summaries.
ATNAThe Audit Trail and Node Authentication (ATNA) Integration Profile establishes security measures which, together with the Security Policy and Procedures, provide patient information confidentiality, data integrity and user accountability
CSDThe Care Services Discovery (CSD) Profile supports queries across related directories containing data about: organizations, facilities, services and providers. Queries against an optional “FreeBusy” service are also supported; this FreeBusy information would support the development of a list of schedulable time slots for providers or services at specific facilities.
CTConsistent Time (CT) enables system clocks and time stamps of computers in a network to be synchronized (median error less than 1 second).
mACMMobile Alert Communication Management Sending one-way alerts to health workers and health system beneficiaries (clients).
mADXEmerging FHIR standard for Aggregate Data Exchange.
mCSDMobile Care Services Discovery Profile supports queries across related directories containing data about: organizations, facilities, services and providers. Based on HL7 FHIR.
MHDMobile Access to Health Documents profile defines a simple HTTP interface to an XDS like environment. The MHD profile is intended for any system that prefers the simplified HTTP RESTful technology rather than the more robust technology used in XDS. It defines transactions to a) submit a set of documents and metadata from the mobile device to a document receiver, b) find the document submission set metadata based on query parameters; c) find document entries containing metadata based on query parameters, and d) retrieve a copy of a specific document.
PDQThe Patient Demographics Query (PDQ) Integration Profile lets applications query a central patient information server and retrieve a patient’s demographic information.
PDQmThe Patient Demographics Query for Mobile (PDQm) Profile defines a lightweight RESTful interface to a patient demographics supplier leveraging technologies readily available to mobile applications and lightweight browser based applications. The functionality is identical to the PDQ Profile described in the ITI TF-1:8.

The Patient Identifier Cross Referencing (PIX) Integration Profile supports the cross-referencing of patient identifiers from multiple Patient Identifier Domains by:

  • Transmitting patient identity information from an identity source to the Patient Identifier Cross-reference Manager.
  • Providing the ability to access the list(s) of cross-referenced patient identifiers either via a query/ response or via an update notification
SVCMShared Valuesets, Codes, and Maps provides basic transactions associated with Terminology Services. Transactions are based on FHIR CodeSystem, ValueSet, and ConceptMap Resource operations. SVCM is currently in Trial Implementation status.
XDS.b Cross-Enterprise Document Sharing (XDS.b) is focused on providing a standards-based specification for managing the sharing of documents between any healthcare enterprise, ranging from a private physician office to a clinic to an acute care in-patient facility and personal health record systems.
  • No labels