Home
An Academic Systems Analysis of FHIR R5 Interoperability, Clinical Decision Support, Federated Learning, Tamper-Evident Audit, and Blockchain-Mediated Consent
Repository: github.com/Ciprian-LocalPulse/MedIntelOS · License: MIT · Status: Alpha, Educational Reference Implementation
MedIntelOS is an open-source, educational reference implementation that explores how five traditionally separate concerns in digital health engineering — standards-based interoperability, clinical decision support, privacy-preserving multi-institution machine learning, tamper-evident provenance, and patient-mediated consent — can be composed into a single, modular codebase without collapsing their trust boundaries into one another.
This wiki presents a structured academic analysis of the repository as retrieved from source: its architecture, module boundaries, data flow, algorithmic content, security posture, and stated limitations, illustrated throughout with original Mermaid diagrams grounded directly in the project's own module structure, request handlers, and contract functions.
A note on scope. Consistent with the maintainers' own documentation, this wiki treats MedIntelOS as what it explicitly claims to be: a rigorously honest, non-clinical, non-production teaching artifact. It is not a production EHR, not a complete FHIR implementation, not a medical device, and not evidence of regulatory compliance.
| Pillar | What is implemented | Explicit boundary |
|---|---|---|
| FHIR R5 | JSON resource builders, in-memory CRUD, a narrow search subset, version IDs, ETags, a CapabilityStatement endpoint | Not a conformance-tested or persistent FHIR server |
| CDS Hooks / CDSS | Discovery endpoint and a patient-view service; qSOFA, NEWS2, an AKI rule, and a CHA₂DS₂-VASc helper | Educational rules only; not clinically validated |
| Federated Learning | Sample-weighted aggregation, a pluggable update callback, a Gaussian differential-privacy experiment, basic outlier detection | No secure aggregation or formal privacy accountant |
| Audit | An in-memory SHA-256 hash chain over structured entries | Tamper-evident within one process; not durable or externally anchored |
| Consent | Solidity consent and audit-ledger contracts with Hardhat tests | Identity, legal authority, erasure, governance, and key custody remain off-chain |
| If you want to... | Read, in order |
|---|---|
| Understand the design philosophy | Introduction → Standards → Architecture |
| Go deep on one pillar | FHIR · CDSS · Federated Learning · Audit · Consent |
| Assess security & production-readiness | Threat Model → Comparison → Limitations |
| Run the project & contribute | Getting Started → API Reference → Contributing |
| Look something up quickly | Glossary · FAQ |
MedIntelOS · A Reference Architecture for Interoperable, Explainable, and Federated Clinical Software Systems
Introduction · Architecture · Security · Getting Started · Glossary · FAQ
Status: Alpha · Educational Reference Implementation — not a production EHR, not a certified FHIR server, not a medical device, and not evidence of regulatory compliance.
Licensed under the MIT License · github.com/Ciprian-LocalPulse/MedIntelOS
© 2026 MedIntelOS Contributors. This documentation is provided "as is," without warranty of any kind.