What is the difference between using blockchain for medical records and using it for supply chain tracking?

Why This Matters for Security Teams

Blockchain changes the trust model, but it does not erase the governance differences between protected health information and product movement data. Medical records are governed by patient consent, minimum necessary access, retention rules, and a high bar for privacy. Supply chain tracking is usually about provenance, custody, and authenticity, where the main risk is tampering or substitution rather than disclosure. Those are not interchangeable requirements.

For security teams, the practical mistake is assuming that a ledger automatically makes data “secure” in both settings. In healthcare, even an immutable record can become a liability if sensitive data is written on-chain or linked too broadly across systems. In supply chain environments, the same design pressure may favour broader read access, stronger integrity checks, and event-level traceability instead of confidentiality controls. Current guidance suggests the architecture should start from the data sensitivity and threat model, not from the blockchain itself. The difference matters because identity, access, and audit needs diverge quickly once many parties need to participate.

NHIMG research on secrets exposure shows why this distinction is operational, not theoretical: the The State of Secrets in AppSec report found that organisations still struggle to keep sensitive credentials under control, which is exactly the kind of failure that becomes more damaging when access patterns are overly broad.

In practice, many security teams discover the mismatch only after sensitive records or trusted custody events have already been published into a design that cannot be easily undone.

How It Works in Practice

In medical records, blockchain is usually better treated as a coordination layer for consent, provenance, and audit logging than as the system of record for full clinical content. A common pattern is to keep the actual health data off-chain in a controlled repository, then store hashes, pointers, or transaction proofs on-chain so multiple providers can verify integrity without exposing everything to every node. That approach supports controlled sharing across care settings, but it still requires strong off-chain identity, access control, and revocation.

Supply chain tracking uses blockchain differently. The ledger records discrete custody or production events, such as manufacture, shipping, receipt, inspection, or temperature checkpoint. The main value is a shared timeline that resists silent alteration. Participants often need broader visibility into product state, but not into unrelated personal data. So the system emphasises immutability, chain-of-custody, and reconciliation across organisations rather than patient consent workflows.

Practitioners usually separate the two designs like this:

• Medical records: minimise on-chain data, protect confidentiality, and enforce consent-aware sharing.
• Supply chain: maximise event integrity, timestamping, and non-repudiation across partners.
• Both: use strong identity, access review, and off-chain governance for anything sensitive or revocable.

For integrity and privacy controls, teams should align with NIST SP 800-53 Rev 5 Security and Privacy Controls and the OWASP Non-Human Identity Top 10 when blockchain participants rely on service accounts, APIs, or machine credentials to write and verify ledger events. This is where the ledger’s trust boundary meets real operational identity.

That guidance tends to break down when organisations try to store regulated personal data directly on-chain, because immutability conflicts with deletion, correction, and access-limitation requirements.

Common Variations and Edge Cases

Tighter ledger governance often increases operational overhead, so organisations must balance auditability against privacy, latency, and interoperability. That tradeoff is especially visible when the same consortium includes hospitals, labs, insurers, manufacturers, and logistics providers.

One common edge case is a hybrid design where medical workflows and supply chain workflows share the same blockchain platform. Best practice is evolving, but the two data classes should still be separated by policy, not just by application logic. Health data often needs selective disclosure, role-based access, and the ability to limit downstream propagation. Supply chain data more often needs durable, shared verification across many participants, including external auditors and regulators.

Another edge case is when product provenance is linked to patient-facing outcomes, such as device recalls or pharmaceutical traceability. In those scenarios, the blockchain may support both traceability and clinical safety, but the privacy model must still treat the patient record as the more sensitive asset. NHIMG’s analysis of the 52 NHI breaches Report reinforces a broader lesson: machine identities and shared service access are often the weak point, not the ledger itself.

Where this breaks down most often is in consortium deployments that assume every participant should see the same data, when in reality the healthcare side requires narrower visibility than the logistics side.

Related resources from NHI Mgmt Group

• What is the difference between direct account compromise and SaaS supply chain compromise?
• What is the difference between software supply chain risk and NHI risk?
• What is the difference between SaaS supply chain security and software supply chain security?
• What is the difference between secret rotation and supply chain trust controls?