Hospital IT script
A hospital IT team can use its own script to send data to the FHIR Server. Siriraj uses this method.
Read the Siriraj case →HealthTAG / Interoperability
Connect an existing HIS to a hospital-managed FHIR system
Health data belongs to the patient while hospitals store and steward clinical records in their source systems. Hospital teams can use their own integration script or HealthTAG FHIR Transformer without replacing the existing HIS.
The hospital environment separates the FHIR Server, relational database, API Gateway, identity linkage, and authorization. Connected services support PHR access and audit.
The diagram shows system responsibilities. An existing HIS uses a hospital IT script or HealthTAG FHIR Transformer to send data to a FHIR Server backed by a relational database. An API Gateway protects the FHIR API. Identity and authorization services link hospital-local patient identifiers and check a 15-minute access window defined from blockchain state. Authorized PHR applications receive permitted FHIR responses. Blockchain receives consent and access events, while clinical records remain in hospital systems.
Hospital source environment
Existing HISExisting hospital system
Choose one ingestion path
Hospital IT scriptHospital-managed integration
HealthTAG FHIR TransformerConfigured transformation
FHIR ServerHL7 FHIR R4
Relational databaseFHIR persistence
API GatewayFHIR API boundary
Identity and authorization serviceIdentity linkage and authorization inside the hospital network
Inside the hospital environmentFHIR Server · API Gateway · supporting services
HealthTAG services connected to the hospital node
Patient identity linkageStores linkage for hospital-local patient identities
Audit ledgerStores consent and access events; clinical records remain in hospital systems
Clinical-data pathPermission / audit event
Two ways to send HIS data to FHIR
Both methods send data to the hospital FHIR system. The hospital chooses the method that fits its existing integration work.
HealthTAG FHIR Transformer
HealthTAG FHIR Transformer maps selected HIS data to FHIR R4. The resource list depends on each installation.
Read the Khian Sa case →FHIR system
What each component does
- FHIR Server
- Stores health data in the HL7 FHIR R4 format.
- Relational database
- Provides persistent storage for the FHIR Server.
- API Gateway
- Provides the TLS gateway and protects access to the FHIR API.
- Identity and authorization service
- Links patient identity and checks authorization inside the hospital network.
DESIGN PRINCIPLES
Keep records at source and use open standards
Data stays at source
The hospital remains responsible for storing and stewarding the clinical record. HealthTAG connects the systems around an authorized exchange instead of putting clinical records on blockchain.
Open standards let systems from different vendors exchange data
HL7 FHIR R4 gives connected systems a shared data structure. Open standards help different vendors communicate, reduce dependence on one proprietary format, and leave room for future integrations.
FHIR resources used at Khian Sa
Khian Sa uses four FHIR resources in this installation.
PatientAllergyIntoleranceEncounterMedicationDispense
Discuss the technical architecture