×

To enhance security, Multi-Factor Authentication (MFA) is mandatory for all HL7 users. More information

Section 1h: Cross-paradigm/Domain Analysis Models
Section 4: Rules and References

HL7 Informative Document: Health Services Orchestration Blueprint, Edition 1

DESCRIPTION

These Orchestration Blueprints guide users to make informed design decisions using visual “blueprints” to introduce key concepts, tradeoffs, and impacts. Focused on service orchestration, the blueprints traverse from a primer through to a reference example on use of an intermediary coordination layer contrasted with a FHIR type request-response.

ALTERNATIVE NAMES

HL7 Informative Document: Health Services Orchestration Blueprint, Edition 1 may also go by the following names or acronyms:

"HL7 Informative Document: Health Services Orchestration Blueprint, E1",,Orchestration Blueprint

BENEFITS

  • Creates overarching patterns and best practices that help guide or govern use of integrated components
  • Enables effective communication of possible or intended interactions among these capabilities
  • Illustrates how orchestration approaches can be used in concert to meet specific situational needs and requirements.

RELATED DOCUMENTS

HL7 Informative Document: Health Services Orchestration Blueprint, Edition 1

(Download)

ADDITIONAL DETAILS

There is a spectrum of ways that system interactions can be realized leveraging FHIR and interaction patterns, and at present the understanding and guidance about how those systems come together to meet business needs is often addressed use-case by use-case. Other industries often have overarching patterns and best practices that help guide or govern use of integrated components. By creating a blueprint, HL7 will be able to more effectively communicate possible or intended interactions among these capabilities. Through the blueprint metaphor, visual representations of these approaches and technologies will illustrate misconceptions and how orchestration approaches can be used in concert to meet specific situational needs and requirements.

BALLOT TYPE

  • Informative

STATUS DATE

2025-11-24

RESPONSIBLE WORK GROUP

Orchestration Services and Architecture

PRODUCT TYPE

  • White Paper

STAKEHOLDERS

  • Clinical Decision Support Systems Vendors
  • EHR, PHR Vendors
  • Healthcare Institutions
  • HIS Vendors
  • Standards Development Organizations (SDOs)

FAMILY

  • Cross-paradigm

CURRENT STATE

  • Active

REALM

  • Universal