"From Black Box to Glass Box"
— Making AI diagnostic rationale verifiable.
"The AI said 'cancer.' Why?
Cryptographically prove that rationale."
AI image diagnostics can now detect lesions with accuracy equal to or greater than radiologists. However, the rationale behind an AI's "positive" determination often remains a black box.
When a patient files a lawsuit, "because the AI said so" won't hold up. When regulators request an audit, "we have no logs" is unacceptable.
MAP cryptographically records every AI decision, proving "when, what data was reviewed, which model, and why that diagnosis was reached" in a tamper-proof format.
Current state and challenges of healthcare AI
"The AI decided" is not a defense in medical malpractice lawsuits. Recording the decision rationale is essential.
Performance changes with retraining. Unable to track which model version made the diagnosis.
FDA PCCP, EU AI Act, MDR require continuous performance monitoring. No technical standard exists.
Questions Raised:
Result: Insufficient evidence, settled out of court
Issues Identified:
Target systems and recording events
Image diagnostic AI, ECG analysis AI
RequiredDigital pathology, cytology AI
RequiredDrug interaction check, dosage optimization
RequiredEmergency priority determination, ICU alerts
RequiredDecision support components
RecommendedPatient screening, endpoint evaluation
RecommendedPatient Data Input
Image/Test values
Patient history
Consent info
AI Analysis
Feature extraction
Model inference
Explainability factors
Diagnosis Generated
Classification result
Confidence score
Differential diagnosis
Treatment Plan
Recommended treatment
Risk assessment
Alternative options
Patient Outcome
Actual result
Follow-up
Prognosis data
Data flow and event structure
Patient Data
AI Model (SaMD)
Clinical Decision
MAP Logger (Sidecar)
← Records all decision events
Hash Chain
Cryptographically linked
Digital Signature
Ed25519 signed
Model Hash
Version identification
Audit Storage
HIPAA/GDPR compliant, encrypted storage
{
"event_id": "019234ab-7c8d-7def-8123-456789abcdef",
"timestamp_ns": 1734567890123456789,
"event_type": "DIAGNOSIS_GENERATED",
"facility_id": "HOSPITAL_XXXXX",
"provenance": {
"actor": {
"type": "AI_MODEL",
"identifier": "chest_xray_classifier_v2.1.3",
"model_hash": "sha256:abc123...",
"training_date": "2024-06-15",
"fda_clearance": "K123456"
},
"input": {
"patient_id_hash": "sha256:patient_anonymized...",
"image_study_uid": "1.2.840.113619.2.55...",
"input_hash": "sha256:def456...",
"acquisition_timestamp": 1734567800000000000
},
"context": {
"clinical_indication": "CHEST_PAIN_EVALUATION",
"referring_physician_id": "NPI_XXXXXXXXXX",
"prior_studies_reviewed": 3,
"patient_age_range": "60-69",
"active_protocol": "EMERGENCY_TRIAGE"
},
"action": {
"diagnosis": "PNEUMONIA_SUSPECTED",
"confidence": 0.87,
"explainability": {
"method": "GRADCAM",
"attention_regions": ["RIGHT_LOWER_LOBE"],
"contributing_factors": [
{"factor": "consolidation_pattern", "weight": 0.45},
{"factor": "air_bronchograms", "weight": 0.32}
]
},
"differential_diagnoses": [
{"diagnosis": "ATELECTASIS", "confidence": 0.08},
{"diagnosis": "LUNG_CANCER", "confidence": 0.03}
],
"recommended_action": "CONFIRM_WITH_CT"
}
},
"prev_hash": "sha256:789xyz...",
"signature": "ed25519:..."
}
Correspondence with international regulations
| Regulation | Jurisdiction | Requirements | MAP Support |
|---|---|---|---|
| EU AI Act Annex III | EU | Medical device AI classified as high-risk, logging mandatory | ✅ Full |
| FDA AI/ML SaMD Guidance | USA | Continuous learning AI performance monitoring | ✅ Full |
| FDA PCCP | USA | Predetermined Change Control Plan, model change tracking | ✅ Full |
| MDR 2017/745 | EU | Medical device traceability | ✅ Complementary |
| 21 CFR Part 11 | USA | Electronic records/signatures, audit trail | ✅ Full |
| HIPAA | USA | PHI protection, access logs | ✅ Crypto-Shredding |
| GDPR | EU | Right to be forgotten, data minimization | ✅ Crypto-Shredding |
| PMDA SaMD Guidance | Japan | Continuous monitoring of AI medical devices | ✅ Planned |
✅ All events recorded in hash chain
✅ Operator identified with Ed25519 signature
✅ Tamper detection via cryptographic hash
✅ UUID v7 + NTP/PTP synchronization
✅ External anchoring prevents deletion even by administrators
| ALCOA+ Principle | Description | MAP Implementation |
|---|---|---|
| Attributable | Who recorded it | ✅ actor.identifier + signature |
| Legible | Readable | ✅ Standard JSON format |
| Concurrent | Recorded at time of action | ✅ Real-time log generation |
| Original | Originality | ✅ Proven via hash chain |
| Accurate | Accuracy | ✅ Verified with input data hash |
| Complete | Completeness | ✅ Event gaps detected via chain breakage |
| Consistent | Consistency | ✅ Linked via trace_id |
| Enduring | Durability | ✅ Cryptographically guaranteed |
| Available | Availability | ✅ Accessible via standard API |
Balancing immutable audit trails with the right to be forgotten
"Immutable Audit Trail"
Cannot delete
"GDPR Right to Erasure"
Must delete
Appears irreconcilable
Patient Data
Encryption
Encrypted Data
Record
MAP
Encryption Key → Securely stored in Key Management System
On Deletion Request:
Destroy encryption key → Data becomes unreadable → Effectively deleted
Hash chain maintained → Audit trail integrity preserved
Specific application scenarios
| Phase | Without MAP | With MAP |
|---|---|---|
| At Diagnosis | AI determines "No abnormality" | Same + Decision rationale recorded |
| Lawsuit Filed | "AI missed it" claim | Same |
| Discovery | Logs potentially tampered | Cryptographically verifiable evidence |
| Root Cause | "Model problem or data problem unknown" | "Accuracy issue under specific conditions in model v2.1.3" identified |
| Liability | Settlement with ambiguous liability | Clear causation-based judgment |
FDA Auditor
PCCP Compliance Verification Request
Audit Complete - Compliance Confirmed
CRO (Contract Research Organization)
EDC System
MAP Anchoring
Hash recorded to external blockchain
Prove "Even system admin cannot tamper"
Significantly reduced FDA Warning Letter risk
Recording the entire model lifecycle
Development
MAP Record
Validation
MAP Record
Approval
MAP Record
Deploy
MAP Record
Operation
MAP Record
Retrain
MAP Record
| GMLP Principle | MAP Implementation |
|---|---|
| Training/Test data independence | Dataset hash enables post-verification |
| Dataset representativeness | Demographic metadata recorded |
| Model transparency | Explainability factors (SHAP/LIME/GradCAM) recorded |
| Continuous performance monitoring | Operational inference results continuously recorded |
MAP technical requirements
Millisecond (NTP synchronized)
Per diagnostic event
SHA-256
Ed25519 (Future: Dilithium)
AES-256-GCM encryption + Crypto-Shredding
FHIR R4 compatible JSON
Configurable per regulatory requirements (typically 10-30 years)
MAP development schedule
Framework hierarchy
Cross-domain parent framework for all domains
Standards body that develops and maintains VAP
Finance
v1.0 ReleasedAutomotive
PlannedMedical
PlannedEnergy
PlannedPublic
PlannedWe welcome participation from medical device manufacturers, hospitals, and regulatory authorities.
"When AI says 'cancer,' what patients want to know isn't the probability. It's the rationale."
"In medicine, trust is not given. It is proven."
This content is licensed under CC BY 4.0 International
© 2024-2025 VeritasChain Standards Organization (VSO). All rights reserved.