Patients decide whether and how their health data may be used. Hospitals store and safeguard clinical records in their source systems. HealthTAG links identities, checks access, supports authorized exchange, and records events for later review.
Health data belongs to the patient. The hospital stores and stewards the clinical record in its source FHIR system. After authorization is checked, that source system can return the permitted response.
The identity linkage service connects the patient identifier used by each hospital to a common identity reference.
The authorization service checks a 15-minute access window defined from blockchain state before the source system returns the permitted information.
The API Gateway provides the TLS gateway and authentication boundary. Credentials, firewall rules, encryption, and hospital operations provide the other safeguards.
Blockchain records consent and access events in a history that is difficult to alter. Clinical records stay in hospital systems.
Before medical AI uses health data, the data source, patient consent, authorization, and access history must be clear. HealthTAG uses this principle to guide future development. Current systems do not train AI or run a clinical AI pipeline.
Blockchain stores the history of consent and access. Clinical records remain in hospital FHIR systems, while authentication, encryption, API configuration, and hospital operations are handled outside blockchain.
See how these systems work together on How it works →
