Skip to content

Add FHIR R4, SMART on FHIR, HL7 v2, eval/drift monitoring, and clinic… - #61

Merged
voidstackloop merged 1 commit into
mainfrom
codex/release-validation-2026-08-31
Sep 3, 2026
Merged

Add FHIR R4, SMART on FHIR, HL7 v2, eval/drift monitoring, and clinic…#61
voidstackloop merged 1 commit into
mainfrom
codex/release-validation-2026-08-31

Conversation

@voidstackloop

Copy link
Copy Markdown
Owner

…al MCP control plane

Implements the full clinical-capability backlog plus its UI wiring:

  • FHIR R4 read-only facade (Patient/ImagingStudy/DiagnosticReport/DocumentReference)
  • SMART on FHIR: resource-server discovery/scope enforcement, and a full client-role launch flow (PKCE, trusted-issuer allowlist, token storage) - gated behind an already-authenticated ModelForge session by design
  • HL7 v2: ER7 parser/builder, ORU^R01 outbound, inbound ORU/ADT parsing, ACK/NACK, an MLLP TCP listener, and a match/apply/review ingestion pipeline with the same "ambiguous match always needs human review" rule imaging's own DICOM patient matching uses
  • Evidence provenance citations for scalar case fields, prompt versioning, online eval/drift monitoring, and quality-aware multi-model routing
  • Electron UI: External EHR page (trusted-issuer admin, SMART launch trigger, session management) and an HL7 Inbox review queue, both wired through new IPC handlers and preload bridges
  • Managed clinical MCP integration: short-lived context grants, exact-operation approval tickets, and structured operation provenance for modelforge-clinical-mcp

Each capability's scope and disclosed gaps are documented in docs/{FHIR_INTEGRATION,SMART_LAUNCH,HL7_V2_INTEGRATION,CLINICAL_AI_EVALUATION, CLINICAL_MCP_INTEGRATION}.md. Full server/app/frontend suites passing, 0 Semgrep findings across touched files.

…al MCP control plane

Implements the full clinical-capability backlog plus its UI wiring:

- FHIR R4 read-only facade (Patient/ImagingStudy/DiagnosticReport/DocumentReference)
- SMART on FHIR: resource-server discovery/scope enforcement, and a full
  client-role launch flow (PKCE, trusted-issuer allowlist, token storage) -
  gated behind an already-authenticated ModelForge session by design
- HL7 v2: ER7 parser/builder, ORU^R01 outbound, inbound ORU/ADT parsing,
  ACK/NACK, an MLLP TCP listener, and a match/apply/review ingestion
  pipeline with the same "ambiguous match always needs human review" rule
  imaging's own DICOM patient matching uses
- Evidence provenance citations for scalar case fields, prompt versioning,
  online eval/drift monitoring, and quality-aware multi-model routing
- Electron UI: External EHR page (trusted-issuer admin, SMART launch
  trigger, session management) and an HL7 Inbox review queue, both wired
  through new IPC handlers and preload bridges
- Managed clinical MCP integration: short-lived context grants,
  exact-operation approval tickets, and structured operation provenance
  for modelforge-clinical-mcp

Each capability's scope and disclosed gaps are documented in
docs/{FHIR_INTEGRATION,SMART_LAUNCH,HL7_V2_INTEGRATION,CLINICAL_AI_EVALUATION,
CLINICAL_MCP_INTEGRATION}.md. Full server/app/frontend suites passing,
0 Semgrep findings across touched files.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@voidstackloop
voidstackloop merged commit cb0ade0 into main Sep 3, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant