This page helps teams assess an HL7 or FHIR requirement using the MDriven integration areas documented in Integration. It does not confirm HL7 or FHIR product support or compatibility.
Documented integration areas
MDriven Integration documentation includes the following relevant areas:
| Integration need | Documented area |
|---|---|
| Authentication and security | BankID, OpenID Connect, OAuth2, Azure AD with OpenID, single sign-on, JWT authentication, ASP.NET Identity, and header-based authentication |
| External APIs and services | SPA integration with Turnkey, REST API integration, SOAP protocol overview, exposing REST services, and web API integration |
| Data import and export | SQL Server import, XML and JSON import, SQL import with associations, data convergence, and Excel integration |
HL7 and FHIR assessment
Before selecting an implementation approach, document the requirements supplied by the external healthcare system:
- Required standard, version, and exchange format.
- Inbound, outbound, or bidirectional data flow.
- Transport or interface requirements.
- Authentication and authorization requirements.
- Required data mapping, validation, error handling, retry, and audit behavior.
- Sample messages, resources, schemas, or interface specifications.
Review the documented general integration areas above, then confirm with MDriven whether they meet the specific HL7 or FHIR requirement.
Get support
For confirmation of an HL7 or FHIR requirement, contact MDriven support at support@MDriven.net or register a support ticket on the wiki. Include the interface specification and representative sample data where available. MDriven states that support requests are answered as soon as possible, with requests from customers holding active Software Assurance contracts prioritized.