Capability C7
Practice-management, reference, email, and SMS integration
Practice-management systems, reference databases, email, and SMS are connected through adapters. Each adapter maps its system to the common model and runs under the same security and audit controls.
Partly builtReference parts exist; the solution layer is designedThe engine channel and mapping patterns have reference implementations. Each new adapter is designed for this solution and built per system.
What happens
- Each system is connected by an adapter that maps its data to the common model.
- Each adapter is tested against the same conformance checks before use.
- Each call from the adapter is authenticated, logged, and retried on failure.
How the AI platform addresses it
- Engine channels (Mirth Connect, Rhapsody, HealthShare) carry the HL7 and file exchanges, and Azure API Management carries the REST exchanges.
- Credentials are held in Azure Key Vault and used through managed identities. No credential is stored in an adapter.
- A new system is added as one adapter and one test set, without changing the rest of the pipeline.
AI role
Mapping suggestions for a new system, reviewed by an integration analyst before the mapping is used.
Approval
An integration analyst approves each new mapping.
Systems involved
- Integration engines
- Azure API Management
- Azure Key Vault
- Azure Monitor
Reference components
- Integration engine channel patterns
- FHIR and HL7 v2 mapping