FHIR and HL7 interoperability

The supplied MDriven documentation indexes integration topics for external APIs and services, REST API integration, exposing REST services, and framework extension and customization. Neither supplied documentation passage describes FHIR or HL7 interoperability.

Do not infer FHIR or HL7 support, supported versions, resource or message coverage, transport behavior, or implementation requirements from the Integration or Framework index pages alone.

Relevant MDriven documentation areas

For a proposed healthcare-system integration, begin with the documented areas below and confirm the required product behavior with MDriven before selecting an implementation design.

Integration need	Relevant documented area
Connect to an external API or service	Integration lists External APIs & Services, including REST API Integration, SOAP Protocol Overview, Exposing REST Services, and Web API Integration.
Manage authentication and security considerations	Integration lists Authentication & Security Integration topics, including OpenID Connect, OAuth2, JWT authentication, and header-based authentication.
Extend or customize framework behavior	Framework lists Extending and Customizing MDriven, including custom code and custom persistence mappers.

Confirmation required

Before implementing FHIR or HL7 exchange, obtain authoritative confirmation of:

1. Whether MDriven provides supported FHIR or HL7 functionality.
2. Any supported standard versions, resource or message coverage, and interface behavior.
3. The applicable authentication, authorization, validation, audit, and error-handling responsibilities.
4. The relevant setup documentation, product-version requirements, and tested examples.

See also

• Documentation:Integration
• Documentation:Framework