Healthcare Interoperability at Scale: Standards-Based EHR–PMS Synchronization

Challenge

The client needed to integrate two essential clinical systems without disrupting day-to-day care delivery. The challenge was to achieve this while addressing the following requirements:

• Keep EHR and PMS data consistent and up to date at the point of care.
• Implement HL7 FHIR interoperability in compliance with strict security and regulatory requirements (HIPAA/GDPR).
• Unify authentication/authorization across on-prem and cloud systems with SSO.
• Provide auditable logs, monitoring, and governed change without disrupting clinical work.

Project Scope

Functional

The functional scope focused on enabling secure, real-time data exchange and unified access across systems, and included:

• Real-time, bidirectional data exchange over FHIR APIs.
• SSO with standards (OIDC/OAuth2/SAML) and token-based access (JWT).
• Event logging, auditing, and monitoring.

Technical

The technical scope was designed to support interoperability at scale while meeting security, reliability, and compliance requirements, and included:

• On-premises middleware (custom Java/Node.js service or NextGen Mirth Connect) acting as a FHIR transformation and orchestration layer to facilitate bidirectional data exchange with the master EHR.
• Secure connectivity from on-prem to AWS (TLS 1.2+, Site-to-Site VPN or Direct Connect).
• Cloud EHR API backend (Amazon API Gateway + AWS Lambda in Java/Node.js) with Cognito authorization.
• Data persistence in Amazon Aurora PostgreSQL; backups to S3/Glacier via AWS Backup.
• Observability with CloudWatch (logs/metrics) and CloudTrail (audit).
• Private networking (VPC, private subnets, Security Groups/NACLs) and controls (KMS, AWS WAF).

Solution We Delivered

This solution provides real-time synchronization of critical patient information, ensuring clinicians have accurate, up-to-date data at the point of care. We achieved this by delivering the following components:

1. FHIR-based middleware in the practice environment to normalize, validate, and route messages, including:

• Transformation layer: HAPI FHIR (Java) or node-fhir libraries to map PMS data to FHIR resources.
• Token strategy: JWT issuance/verification (Cognito/JWKS) for secure API access.
• Connectivity: Hardened TLS, VPN/Direct Connect, and least-privilege access.

2. EHR API on AWS with API Gateway + Lambda, integrated with Cognito for authentication/authorization and rate limiting.

3. Identity federation with common IdPs (Okta, Azure AD, Auth0, Keycloak) to provide SSO across on-prem apps and cloud services.

4. Observability & governance: Centralized logging, auditing, and alerts; change control and rollout playbooks.

5. Deployment options:

• Custom executable/daemon (Java Spring Boot JAR or Node.js service) on practice desktops/servers, or
• Mirth Connect as the integration engine, with third-party tooling preferred.

Client’s Results

As a result of the implemented solution, the client achieved the following outcomes:

• Enabled real-time access to synchronized clinical data (medications, procedures) across EHR and PMS.
• Standardized data exchange with HL7 FHIR, minimizing custom integrations and long-term maintenance risk.
• Unified access and security through SSO, JWT-based authorization, encryption, and full auditability.
• Increased operational reliability with centralized monitoring, alerting, and backups.
• Built an extensible integration layer that simplifies onboarding new clinics, vendors, or system modules.