Decentralized healthcare is often described as healthcare without a central authority. That description does not mean putting medical records on a blockchain or transferring every data responsibility to the patient. A practical model separates the responsibilities of different systems, then connects them through standards and rules that participants can inspect.
Hospitals continue to control clinical records. Patients take part in authorizing access within the boundaries supported by the system and the law. An exchange layer delivers only authorized information, while a separate audit layer can record consent and access events without containing clinical data.
Moving from central control to shared responsibilities
A centralized system is not inherently wrong. A hospital needs a reliable system to store and use its own medical records. Problems arise when exchange between providers relies on a single point of control, or when patients cannot see the conditions under which someone requested their information.
A system with distributed responsibilities can include hospital data sources, identity services, authorization, exchange standards, and an audit record. No single part needs to know or store everything. This design can limit the impact of a failure in one component, although it does not eliminate security risk.
Where the information remains
In the HealthTAG model, medical records remain in systems controlled by each hospital. Information selected for exchange is represented as HL7 FHIR R4 within the hospital environment. It reaches the FHIR layer through a hospital-managed script or the HealthTAG FHIR Transformer, depending on the implementation.
The HealthTAG Module, also called the Hospital API, runs within the hospital network to support identity linkage and authorization checks. When an application or PHR requests information, the system checks permission before releasing data within the approved scope. The medical record never passes through or resides on the blockchain.
Data sovereignty in healthcare
In this article, data sovereignty means giving patients clear rights and practical ways to access information about themselves and participate in decisions about who may use it for a particular purpose. Those rights operate alongside hospital responsibilities, data protection law, and clinical recordkeeping requirements.
Calling a patient the “owner of the medical record” can be misleading because the hospital controls and remains responsible for that record. A useful system makes patient rights actionable. Depending on the applicable rules, patients may view available information, request a transfer, and manage consent when consent is the relevant legal basis.
Scoped and time-limited authorization
Authorization does not need to be an all-or-nothing choice. A system can limit access by information type, requester, purpose, and time. A patient might, for example, authorize a verified professional to view a specific item during a defined period.
The current HealthTAG architecture defines a 15-minute access window from blockchain state, which the Hospital API checks. Expiration reduces the chance that an authorization remains open longer than necessary. The implementation still needs appropriate identity checks, revocation handling, event records, and procedures for exceptional or emergency access.
Blockchain as an audit record, not a medical record store
Blockchain can support events that several parties may need to verify, including consent or authorized access. When properly designed and operated, its ledger structure makes retrospective alteration easier to detect.
Sensitive health information should not be written to that ledger. Blockchain records are difficult to remove or correct, which conflicts with important data protection and clinical requirements. HealthTAG therefore separates clinical information from the event record. Encryption alone is not a sufficient reason to place a medical record on a blockchain.
Benefits for continuity of care
When providers use a shared data standard and a clear authorization process, patients do not need to restart every time they visit a different facility. Care teams can request relevant information when needed, and patients can view authorized information through a PHR.
Good exchange can reduce repeated work and make important information available sooner. The outcome still depends on data quality, identity matching, and agreements between organizations. Interoperability means more than successfully connecting an API. The receiving system must interpret the information as the sender intended.
Other applications need a separate boundary
Healthcare discussions also propose blockchain and smart contracts for research, payments, insurance, and pharmaceutical supply chains. These ideas may benefit from auditable events or automated conditions, but each use case needs trustworthy input data, governance, and a way to correct errors.
In research, a participant might authorize the use of de-identified information for a named study and a defined period. The agreement could include compensation or another benefit for the participant, with a smart contract recording whether the agreed conditions were met. The study would still need ethics review, a consent-withdrawal process, and controls for the risk that information could be linked back to a person.
The phrase “the patient holds the key” needs to be read in the context of the implemented architecture. Patients manage access through the authorization process, hospitals control clinical records, and the responsible systems manage credentials and keys within their own boundaries. Control over permission does not mean that a patient’s device holds the keys to every medical record.
They are examples of decentralized healthcare in general, not confirmation of current HealthTAG features or deployments. HealthTAG’s documented scope covers FHIR connectivity, identity linkage, authorization, access auditing, and the PHR experience.
Useful decentralized healthcare is not a system without accountable organizations. It is a system that defines accountability clearly. Hospitals control medical records, patients exercise their rights through understandable tools, and participants exchange only the information needed under verifiable authorization.
Sources
- Original article in the HealthTAG CMS (HealthTAG)
- Data Source Node architecture (HealthTAG)