Oracle Integration for Healthcare Support for HL7

Oracle Integration for Healthcare enables you to create integrations that interact with healthcare organizations that use HL7.

Oracle Integration for Healthcare provides the following capabilities:
  • Available for use with Oracle Integration through installation of the Healthcare edition in the Oracle Cloud Infrastructure Console. See Oracle Integration Editions in Provisioning and Administering Oracle Integration 3.
  • Supports HL7 version 2.
  • Supports the following versions of the HL7 version 2 standard: 2.3.1, 2.4, 2.5.1, 2.5, 2.6, 2.7, 2.7.1, 2.8.1, 2.8, 2.8.2, and 2.9.
  • Supports HL7 applications on different versions interacting with each other through Oracle Integration for Healthcare.
  • Supports creating healthcare integrations in projects or in standalone environments (outside of a project). See Design, Manage, and Monitor Integrations in Projects in Using Integrations in Oracle Integration 3
  • Supports common healthcare interoperability use cases, including:
    • Transfer of care
    • Inventory synchronization – employee medical record (EMR) and enterprise resource planning (ERP)
    • Payer/provider
    • Modernization programs:
      • Exposure of health data using Fast Healthcare Interoperability Resources (FHIR)
      • Mobile applications
      • Patient portal
    • Update of a state immunization registry upon patient checkout
  • Supports message standards and transport protocols commonly used in the healthcare interoperability (integration) market:
    • Supports the Minimal Lower Layer Protocol (MLLP). MLLP is a TCP-based standard for sending and receiving HL7 messages. You configure the MLLP Adapter to receive inbound (trigger) HL7 messages or send outbound (invoke) HL7 messages. See MLLP Adapter Capabilities in Using the MLLP Adapter with Oracle Integration 3.
    • Supports Fast Healthcare Interoperability Resources (FHIR). FHIR is a set of rules and specifications for exchanging electronic healthcare data over the REST protocol in XML or JSON format. You configure the FHIR Adapter to invoke FHIR resources (for example, a patient resource, encounter resource, and others) in outbound messages in Oracle Integration. See FHIR Adapter Capabilities in Using the FHIR Adapter with Oracle Integration 3.
  • Supports defining the connections to external systems with which to exchange HL7 messages.
  • Supports designing and customizing the HL7 messages to exchange. See Create Oracle Integration for Healthcare Schemas and Documents.
  • Supports integrating and processing HL7 messages in integrations with the healthcare action. The healthcare action converts inbound HL7 messages to XML format and outbound messages from XML format to HL7 format. See Design an Integration with a Healthcare Action.
  • Supports tracking and monitoring HL7 integrations at runtime.
  • Supports retaining runtime data for 184 days when selecting the Production tracing level during integration activation. See Activate an Integration in Using Integration Insight in Oracle Integration 3