The Architecture of Interoperability
A transparent look at how PPUSSH Health moves an authorized clinical summary between two facilities — illustrated with our early emergency-exchange flow.
Illustrative exchange flowConnect (The Adapter)
Each facility connects through an adapter that speaks its local format — no rip-and-replace. Below is an illustrative example, not live telemetry.
Discover (Network Registry)
Search connected facilities for a patient match — name plus date of birth — before any record is requested.
ID: eki_0184_x
ID: lag_8821_y
Authorize (Consent & Policy)
Recorded patient consent (or documented emergency break-glass reason) and organizational data-sharing policies checked before transmission.
Patient Consent Recorded
Method + consenter stored with request
Organization Policy Check
Source authorization + audit trail
Exchange (Secure Payload Transport)
The requested payload is structured, encrypted, and delivered horizontally to the requesting application.
{
"patient": { "name": "Ibrahim Yusuf" },
"allergies": [{ "substance": "Penicillin" }],
"medications": [{ "name": "Amlodipine" }],
"source": { "organizationName": "Teaching Hospital Ekiti" },
"metadata": { "scope": "emergency-summary" }
}