Six stages from HIS ingestion to audit
Patients control consent. Hospitals steward the source systems. HealthTAG provides identity and access infrastructure. The technical request sequence may differ between installations.
Clinical records stay with the hospital
The hospital stewards its HIS and FHIR environment. Identity and authorization services support permitted exchange, while consent and access events go to the audit ledger.
The physical request sequence may differ between installations.
- 01
Connect
Send HIS data to the hospital FHIR system through an IT script or HealthTAG FHIR Transformer.
Read about interoperability - 02
Standardize
Use HL7 FHIR R4 so connected systems share the same data structure.
Read about interoperability - 03
Identify
The identity linkage service connects each hospital-local patient identifier to a common identity reference.
Explore PHR
Consent comes before the access decision
Consent states the patient’s choice. Authorization evaluates a specific request. A permitted response comes from the hospital source system, and the access event remains available for audit.
- 01ConsentThe patient defines whether and how data may be used.
- 02AuthorizationThe system evaluates the request against the applicable permission.
- 03Permitted responseThe hospital source returns only the response allowed for that request.
- 04AuditConsent and access events are recorded for later review.
Patients own the data. Hospitals keep the records. HealthTAG supports the exchange.
Clinical records: stored and stewarded in hospital source systems.
Authorization: checked for a defined access window.
Blockchain: records consent and access events.