Interoperability control plane
Standards become testable contracts before they become live healthcare connectors.
SCRIMED defines and validates standards-aware synthetic connector contracts. No registry entry authorizes live data exchange, autonomous clinical action, diagnosis, payer submission, or production record mutation.
Health records
No-PHI extraction, source attribution, and patient-safety lint sit beside standards conformance.
Health Records Safety Exchange
SCRIMED Health Records Safety Exchange defines no-PHI health-record ingestion, extraction, normalization, interoperability, and patient-safety controls for synthetic and customer-approved sandbox evaluation. It does not authorize live PHI ingestion, production EHR access, patient matching, diagnosis, treatment, emergency triage, order entry, prescribing, payer submission, patient outreach, autonomous clinical decisions, record mutation, or production connector execution.
5 capabilities · 5 hard-stop workaroundsExecutable evidence
Synthetic test kits make conformance targets inspectable while retaining every production blocker.
FHIR R4 and US Core Intake Test Kit
live-blocked · 3 pre-live checks blocked
FHIR R4 with deployment-selected US Core 8.0.1 profilesSMART App Launch Authorization Test Kit
live-blocked · 4 pre-live checks blocked
SMART App Launch 2.2.0 with FHIR R4 launch contextDICOMweb Imaging Exchange Test Kit
live-blocked · 3 pre-live checks blocked
DICOM current edition with deployment-scoped DICOMweb servicesHL7 v2 ADT / Order / Result Event Test Kit
live-blocked · 3 pre-live checks blocked
Deployment-selected HL7 v2 ADT, ORM, and ORU message profilesX12 Payer / RCM Evidence Test Kit
live-blocked · 3 pre-live checks blocked
Trading-partner-selected X12 eligibility, authorization, claim, remittance, and acknowledgement guidesStandards registry
Exchange, imaging, payer, pharmacy, device, profile, and terminology boundaries.
FHIR
exchange · HL7 International
Use deployment-approved FHIR R4 or R4B profiles for current enterprise integrations; monitor R5 and require explicit version negotiation.SMART
profile · HL7 International
Use SMART App Launch profiles for approved user-facing FHIR applications with least-privilege scopes and tenant-aware authorization.USCDI
data-set · Office of the National Coordinator for Health IT
Map synthetic extraction targets to USCDI data classes before SCRIMED represents health-record coverage for U.S. buyers.TEFCA
network · Office of the National Coordinator for Health IT
Treat nationwide exchange as a governance and participant-path readiness track, not a direct SCRIMED live-exchange claim.HL7 v2
exchange · HL7 International
Negotiate message versions, local profiles, segment requirements, acknowledgements, and replay behavior per source system.DICOM
imaging · DICOM Standards Committee
Use approved DICOM and DICOMweb services for imaging exchange, with a deployment-specific conformance statement and no diagnostic interpretation by the connector.X12
administrative · X12
Select payer-approved transaction versions and implementation guides before eligibility, claim, remittance, status, or authorization exchange.CMS APIs
administrative · Centers for Medicare & Medicaid Services
Prepare payer, provider, and prior-authorization workflows for API-based evidence packets while retaining payer/trading-partner approval and no-guarantee reimbursement boundaries.C-CDA
exchange · HL7 International
Use deployment-approved C-CDA document templates when clinical document exchange is required alongside resource-level FHIR exchange.IHE
profile · IHE International
Select deployment-specific IHE profiles to constrain standards into testable cross-enterprise workflows.NCPDP SCRIPT
pharmacy · National Council for Prescription Drug Programs
Select the approved SCRIPT version and transaction scope before any pharmacy or electronic-prescribing integration.ISO/IEEE 11073
device · ISO and IEEE
Select device classes, transport profiles, and validation procedures before ingesting wearable or medical-device observations.Terminology
terminology · SNOMED International, Regenstrief Institute, and U.S. National Library of Medicine
Govern code systems, value sets, mappings, licenses, versions, and validation timestamps independently from transport standards.Standards and profile registry
Typed registry exposes steward, implementation target, profiles, capabilities, evidence, controls, and primary-source references.
- Registry definition is planning evidence only; it does not prove a connector is conformant.
Contract-to-standard binding
Every external connector contract declares standards and deployment-specific conformance targets.
- A bound contract must still pass implementation, security, privacy, and trading-partner review.
Synthetic conformance fixtures
Non-synthetic contracts require deterministic synthetic request, expected response, safeguard mapping, and diff fingerprints.
- Synthetic fixtures cannot substitute for production conformance, certification, or partner acceptance testing.
Identity, consent, and audit linkage
Tenant identity, patient-context authorization, consent, purpose-of-use, and durable audit decisions remain explicit readiness gates.
- Live exchange stays denied until these controls are approved and tested.
Implementation testing and certification
Each deployment needs selected versions, profiles, conformance artifacts, partner tests, and owner approval.
- No standard is marketed as implemented merely because it appears in the registry.
Discrepancy control