Wiki Home and Navigation

20. Wiki Home and Navigation

MedIntelOS — A Reference Architecture for Interoperable, Explainable, and Federated Clinical Software Systems

Repository: github.com/Ciprian-LocalPulse/MedIntelOS · License: MIT · Status: Alpha, Educational Reference Implementation

This wiki presents a structured academic analysis of MedIntelOS as retrieved from source: its architecture, module boundaries, data flow, algorithmic content, security posture, and stated limitations, illustrated with original Mermaid diagrams grounded in the project's own module structure, request handlers, and contract functions. 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 — rather than as a candidate for clinical deployment.

20.1 Full Table of Contents

flowchart TB
    P1["1. Introduction & Motivation"] --> P2["2. Standards & Research Context"]
    P2 --> P3["3. System Architecture Overview"]
    P3 --> P4["4. FHIR R5 Interoperability Layer"]
    P4 --> P5["5. Clinical Decision Support Subsystem"]
    P5 --> P6["6. Federated Learning Subsystem"]
    P6 --> P7["7. Tamper-Evident Audit Layer"]
    P7 --> P8["8. Blockchain-Mediated Consent Management"]
    P8 --> P9["9. Security Architecture & Threat Model"]
    P9 --> P10["10. Deployment, Operations & Configuration"]
    P10 --> P11["11. Validation Strategy & Evidentiary Gaps"]
    P11 --> P12["12. Limitations, Ethics & Future Work"]
    P12 --> P13["13. Conclusion & References"]
    P13 --> P14["14. Glossary of Terms"]
    P14 --> P15["15. Frequently Asked Questions"]
    P15 --> P16["16. Getting Started"]
    P16 --> P17["17. API Reference Summary"]
    P17 --> P18["18. Comparison to Production-Grade Systems"]
    P18 --> P19["19. Contributing & Roadmap"]
    P19 --> P20["20. Wiki Home & Navigation"]

Loading

Figure 18. Full linear reading path of the wiki, from motivation through the five core pillars, cross-cutting concerns, and reference material.

20.2 Reading Paths by Interest

Table 12. Suggested reading paths

If you want to...	Read, in order
Understand the project's overall design philosophy	Introduction and Motivation → Standards and Research Context → System Architecture Overview
Go deep on one pillar	Any of Sections 4–8: FHIR, CDSS, Federated Learning, Audit, Consent
Assess security and production-readiness	Security Architecture and Threat Model → Comparison to Production-Grade Systems → Limitations, Ethics, and Future Work
Run the project and start contributing	Getting Started → API Reference Summary → Contributing and Roadmap
Look something up quickly	Glossary of Terms · Frequently Asked Questions

20.3 The Five Pillars, at a Glance

Table 13. Implemented pillars and their explicit boundaries

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

20.4 A Note on Scope

This wiki is a software and architecture analysis, not a clinical-safety endorsement — a distinction the project's own documentation draws repeatedly and one this wiki adopts as its own governing principle throughout, as restated in Validation Strategy and Evidentiary Gaps, Section 11.3.

---

Previous: ← Contributing and Roadmap · Back to: Introduction and Motivation ↑