Owns the health data
The patient decides whether and how their health data may be used.
Consent and access →Health data infrastructure · Thailand
Trusted health data infrastructure for Thailand
Your data. Your consent. One connected Thailand.
HealthTAG connects hospital systems through open standards and checks identity and access before permitted data is returned. The original clinical records remain in hospital source systems.
Hospital source environmentHISClinical records stay here
HealthTAGTrust and interoperability infrastructure
- Identity
- Authorization
- Audit
Patient-facing accessPHR
External evidence
Siriraj, ETDA, APICTA, and KASIKORNBANK have published records related to HealthTAG
ProgrammeSiriraj 5G Smart HospitalFaculty of Medicine Siriraj Hospital↗SandboxETDA Digital Service SandboxETDA↗AwardAPICTA · Cross Category: Start-UpAPICTA↗Strategic CollaborationOrbix Technology × HealthTAGKASIKORNBANK↗
Latest from HealthTAG · 26 Aug 2026
→MU Health Wallet exhibited at Digital Health Forum 2026
Mahidol University and HealthTAG presented MU Health Wallet at the Ministry of Public Health Bureau of Digital Health booth on 25 and 26 August 2026.
Who owns, stores, and connects health data
Health data belongs to the patient. The hospital stewards the clinical record. HealthTAG provides the infrastructure for authorized exchange.
Stewards the clinical record
The hospital stores clinical records in its source systems and remains responsible for those systems.
Hospital-held records →Connects authorized exchange
HealthTAG provides infrastructure for identity linkage, authorization, exchange, and audit.
HealthTAG platform →Platform capabilities
How HealthTAG connects data and checks access
HealthTAG connects existing HIS data through FHIR, links patient identities, checks authorization, and records consent and access events.
Data Connect
Connect an existing HIS to the hospital FHIR system through a hospital-managed script or HealthTAG FHIR Transformer.
How systems connect →Identity Connect
Link hospital-local patient identifiers to a common identity reference so records can be matched to the same person.
Follow the exchange flow →Consent and Authorization
Record the patient's consent, then evaluate each access request separately.
Consent and access →Audit and Provenance
Record consent and access events for later review while keeping the hospital source of each clinical record clear.
Audit and data sources →Information by role
Choose the information for your role
Find deployment details, technical architecture, public records, or investor information.
Deployment examples
Two hospitals, two integration paths
Siriraj uses a script developed by its hospital IT team. Khian Sa uses HealthTAG FHIR Transformer.
Siriraj 5G Smart Hospital
PHR work within a Smart Hospital programme
HealthTAG says it participated in the Permission-based Blockchain for Personal Health Record subproject. Siriraj IT uses its own HIS-to-FHIR script.
Read the Siriraj caseKhian Sa Hospital
Selected HIS data connected to FHIR R4
The Khian Sa installation uses HealthTAG FHIR Transformer to connect selected HIS data to the hospital FHIR R4 environment.
Read the Khian Sa case
HealthTAG PHR
View permitted health information in one place
HealthTAG PHR presents the health information available and permitted for each patient. Hospitals continue to store and steward the original clinical records in their source systems.
Founded from clinical work
HealthTAG began with a problem seen in patient care
Health records may exist in several systems but still be difficult to use when a patient needs care. HealthTAG starts product decisions with one question: will this improve patient care?
Founder
Dechowat Promda, M.D.
A physician-founded company working on health-data infrastructure.
Company & founderDiscuss health data infrastructure with HealthTAG
Contact the team about hospital integration, public-sector or university work, deployments, or industry partnerships.