Planned interoperability and semantic-provenance pathway
VitaSignal has completed a nonconfidential concept specification for evaluating the semantic provenance required when standards-based clinical data are reused for documentation-derived AI. Current work is design and planned mapping only.
No production FHIR connector, USCDI v7 implementation, conformance claim, certified mapping, live provenance bridge, or partner deployment is represented on this page.
Current validation status
VitaSignal has run a controlled local structural check of its own synthetic test harness using synthetic FHIR R4 resources, Provenance, and AuditEvent records. This is a self-run developer test of internal data structures, not a step in the site-approved evaluation sequence below.
These results are limited to a local synthetic environment. They do not demonstrate a production EHR connector, external conformance certification, partner-environment interoperability, production throughput, cybersecurity approval, or clinical validation.
Epic, Oracle Health, and MEDITECH remain future integration targets. No vendor-specific connector is available today.
A pilot may begin with a site-approved retrospective export and does not require a completed FHIR connector.
Last updated: August 19, 2026
Standards under evaluation (planned)
Planned FHIR R4 resource study
Candidate resource families and data semantics are being evaluated for future site-specific mapping and conformance testing. No current implementation or conformance is claimed.
SMART on FHIR concept only
Scoped, token-based access is described as a future design target. No connector is implemented, certified, or available.
Planned privacy and audit controls
Design targets for encryption, audit records, and bounded scope. Implementation completeness and independent assessment have not been established.
HL7 pathway concept
A read-only inbound ingestion pathway is described as a concept where FHIR is unavailable. No write-back to the EHR is contemplated and nothing is implemented.
Planned architecture concept
A concept for a governed research layer between standards-based data and retrospective review.
The diagram below describes a design concept, not an implemented system. Each layer is a planned target that would require site approval, local mapping, sandbox conformance testing, and independent partner validation.
EHR System of Record (interoperability target)
Epic, Oracle Health, MEDITECH named as future targets only. No partnership, certification, or completed integration.
Planned FHIR R4 resource study
Candidate resource families and data semantics under evaluation. No current implementation or conformance is claimed.
VitaSignal research layer (prototype)
Design targets for governance, subgroup review, explainability, and audit records. Implementation completeness has not been established.
Planned retrospective review surface
Concept for leadership-facing aggregate summaries. Not a clinical-facing surface and not deployed.
Design targets (planned)
Stated intent, not implemented capability.
Design target: outputs are intended for retrospective, aggregate review rather than a clinical-facing surface. Nothing is deployed inside a clinical workflow today.
Design target: read-scoped access only. VitaSignal's concept consumes documentation events and contemplates no write-back to the EHR.
Design target: per-site data boundaries, per-site audit records, and per-site model versioning. Implementation completeness has not been established.
Policy: research and decision-support framing only, never autonomous action. Human oversight is required.
Design target: outputs carry model version, source reference, and known limitations. End-to-end lineage and deterministic re-derivation have not been established.
Future evaluation sequence
None of the steps below has been completed. Each requires written agreement, local technical review, and site approval. The completed local synthetic harness check described above is internal developer testing and does not satisfy any step in this sequence.
Planned step 01
Site-approved data-pathway and semantic review
Nonconfidential review of candidate data pathways and data semantics with health system informatics, security, and privacy stakeholders.
Planned step 02
Planned FHIR or approved export mapping
Design of a site-specific mapping using FHIR resources or an approved export. Mapping is design work only until reviewed and approved locally.
Planned step 03
Site sandbox implementation and conformance testing
Implementation and conformance testing in a site or vendor sandbox environment on de-identified or synthetic data. Not started. Internal local harness checks do not substitute for site-environment conformance testing.
Planned step 04
Provenance and audit-event testing
Testing of provenance and audit-event concepts, including source reference, model version, timing, status, and known limitations.
Planned step 05
Independent partner validation
Independent partner validation would be required before any operational or clinical-facing use is considered. This has not occurred.
Reviewing the planned pathway?
Request the nonconfidential concept overview, which describes the planned architecture, the candidate resource study, and the future evaluation sequence for your IT and informatics teams.
Intended use, product classification, and the applicable regulatory pathway remain under evaluation. References to third-party EHR vendors and to FHIR, SMART on FHIR, HL7, Provenance, and AuditEvent describe interoperability targets, planned pathways, or concepts only. They do not imply endorsement, partnership, certification, completed integration, or production availability.