HealthTAG / Platform

Connect health data while hospitals keep the clinical records

HealthTAG connects existing hospital systems through HL7 FHIR R4, links patient identities, checks access, and records consent and access events. Patients own their health data. Hospitals continue to store and steward clinical records in their source systems.

See how it worksTalk to HealthTAG

Data, identity, access, and audit are handled separately

Hospital systems retain the clinical records. Identity Connect links patient identifiers, Hospital API checks access requests, and blockchain records consent and access events.

  1. 01

    Data Connect

    Moves selected data from an existing HIS into a hospital-stewarded HL7 FHIR R4 system. Hospital IT can use its own integration script or HealthTAG FHIR Transformer.

    Data interoperability
  2. 02

    Identity Connect

    Links the patient identifier used by each hospital to a common identity reference. The linkage is stored in a cloud database, while clinical records remain in hospital systems.

    Identity and PHR
  3. 03

    Consent and authorization

    Records the patient's consent, while Hospital API evaluates each access request. It checks the current access window before the source system returns permitted information.

    Consent, trust and access
  4. 04

    Audit and provenance

    Records consent and access events for later review and keeps the hospital source of the clinical record clear. Clinical records are not stored on blockchain.

    Audit and record sources
RESPONSIBILITY FIRST

Patients retain ownership while hospitals retain the records

This conceptual diagram describes responsibility boundaries. It does not prescribe the physical request sequence of every installation.

Conceptual responsibility model for authorized health-data exchange.
Read the diagram as text
  1. The patient owns their health data and controls consent and use.
  2. The hospital stores and stewards the clinical record in its source systems.
  3. HealthTAG supplies infrastructure for identity linkage, authorization, permitted exchange, and audit.
  4. Clinical records do not pass through blockchain. Blockchain records consent and access events.
FOR HOSPITAL LEADERS

Connect without replacing the core HIS

The hospital keeps custody of its records and chooses the ingestion path that fits its IT capability. Siriraj uses a hospital-developed script. Khian Sa uses HealthTAG FHIR Transformer for four confirmed FHIR resources.

Compare deploymentsDiscuss an integration
FOR IT TEAMS

Two ingestion paths support different hospital IT models

A hospital may use an IT-managed script or HealthTAG FHIR Transformer. The current hospital-side architecture separates FHIR storage, API protection, identity linkage, and authorization.

Technical boundary and current implementation
Ingestion
Hospital IT script or HealthTAG FHIR Transformer.
FHIR system
HAPI FHIR Server using HL7 FHIR R4, with PostgreSQL persistence and Kong API Gateway.
Access check
HealthTAG Module, also called Hospital API, checks identity and the current authorization window inside the hospital network.
Interoperability components Conceptual exchange flow Official Data Source Node architecture

Choose a starting point

Compare deployments, inspect technical components, check published records, or see the PHR.

  • 01

    Hospital leaders

    Compare the two confirmed hospital integration paths and the responsibilities that remain with each hospital.

    Review deployments
  • 02

    Hospital IT teams

    Review ingestion options, FHIR components, access checks, and the hospital-side architecture.

    Open the technical overview
  • 03

    Public-sector and university partners

    Check externally sourced programme, sandbox, award, and collaboration records.

    Review evidence
  • 04

    Patients and general visitors

    See how authorized records can appear in a Personal Health Record.

    Explore PHR

Siriraj, ETDA, and APICTA have published records related to HealthTAG

Siriraj published the 5G Smart Hospital programme, ETDA recorded HealthTAG's Digital Service Sandbox participation, and APICTA named Healthtag as the 2022 Cross Category: Start-Up winner.

Deployment

Siriraj and Khian Sa

Two confirmed hospital cases use different HIS-to-FHIR ingestion paths.

Compare both cases
Award

APICTA · Cross Category: Start-Up

APICTA’s official winner list names Healthtag of Thailand and BLOCKCHAIN-BASED PHR & HEALTH DATA MANAGEMENT PLATFORM as the Cross Category: Start-Up winner.

Evidence record APICTA
Sandbox

ETDA Digital Service Sandbox

ETDA lists the HealthTAG service in its Digital Service Sandbox, including the testing period and an exit status after meeting the defined goals and success indicators.

Evidence record ETDA
NEXT STEP

Discuss the systems you need to connect

Tell us which hospital systems need to connect and who will use the exchange. Do not send patient, medical, credential, or other sensitive data.

Contact HealthTAG