EHR data readiness supports institutional work.
VitaSignal's existing EHR and Data Pathway prototype is supporting infrastructure for institutional reviews. Its working application name is VitaSignal EHR Data & AI Evaluation Readiness. It supports scoped institutional work.
No production FHIR connector, USCDI v7 implementation, conformance claim, certified mapping, live provenance bridge, or partner deployment is represented on this page.
What exists today
Clinical AI Buyer Readiness is in private preview on its own website. EHR and Data Pathway and Governance remain private prototypes. Institutional engagements require an agreed scope, delivery capacity and separate authorization. No app access is included in a public inquiry.
The public demo illustrates intended roles with synthetic material and simulated handoffs. Internal synthetic structural checks are developer testing only; neither establishes a live product handoff, partner-site conformance, security acceptance or clinical validation.
Epic is the initial integration design target. Other adapters would require justified demand, funding and their own review. No vendor-specific connector is available today.
Intended functions cover use-case setup, authorized read-only data pathways, field availability, data quality, provenance, reviewer controls and a versioned EHR Data Readiness Summary. A starting feasibility review may use approved nonpatient documents and stakeholder conversations. A live EHR connection is not required for every use case.
Last updated: October 27, 2026
EHR and Data Pathway: technical concepts under evaluation
FHIR R4 study
Candidate resources and local data semantics are under evaluation. Production connectivity and external conformance are not established.
SMART on FHIR concept
Bounded, authorized access is a design target, not an available vendor-certified connector.
Provenance and audit concepts
Source traceability and accountable records are design targets. Complete implementation and independent assessment are not established.
Approved retrospective pathways
A future site-specific review could use an approved export rather than a live connector. Scope and permissions must be agreed first.
Supporting technical responsibilities
Distinct technical roles. Separately authorized work.
The technical roles below explain the supporting apps, not a required buying sequence or a completed workflow. Institutional Feasibility Review and Governance Evaluation are separate commercial scopes. Vendor evidence still needs local review. No automatic transfer, shared access or completed integration is established.
Clinical AI Buyer Readiness
Vendor preparation: intended use, claims, supporting sources, gaps and limitations. A prepared record is not independent validation.
EHR and Data Pathway
Local data context: availability, provenance, mapping and workflow suitability. Private prototype in development, not a deployed connector.
Governance
Institutional review: evidence, uncertainty, required controls and accountable decisions. Private prototype in development.
Health-system decision owner
The institution retains authority. VitaSignal recommends; the health system decides. No product output authorizes clinical use.
Company-wide boundaries
Clear scope before any connection.
Separate scopes: vendor evidence software, institutional feasibility and governance evaluation are optional offerings. The EHR data-readiness app supports institutional work. Each engagement has its own scope.
Planned handoffs are not live integrations. No shared sign-in, automatic transfer or connected product system is represented.
Any future local data access requires explicit authorization, bounded scope and applicable site approvals. Read-only concepts contemplate no EHR write-back.
Public demonstrations use fictional or generated material. Synthetic examples do not establish interoperability, clinical performance or local validity.
VitaSignal recommends; the health system decides. Evidence preparation and recommendations do not authorize deployment or patient-care changes.
Before any future site connection
These are prerequisites for a future site-specific pathway, not a current onboarding service or a completed partner sequence. Scope, duration and responsibilities require a written agreement. A synthetic demo cannot satisfy these requirements.
Required gate 01
Define the local use and decision owner
Agree the evidence question, intended use, accountable reviewers and stopping conditions. Company information or a demo does not constitute an engagement.
Required gate 02
Authorize the data pathway
Institutional technical, privacy, security and governance stakeholders determine the permitted data scope and access. No public pathway for PHI exchange is offered.
Required gate 03
Review mappings and source meaning
A future site-specific mapping must account for timing, missingness, documentation context and source provenance. A vendor record does not establish local suitability.
Required gate 04
Test in an approved environment
Any future connection requires site or vendor sandbox testing and applicable conformance and security review. Internal synthetic checks do not satisfy these gates.
Required gate 05
Return evidence to institutional governance
The institution reviews limitations, unresolved questions and required controls before deciding any next step. Independent partner validation remains required before operational or clinical-facing use is considered.
Discuss a defined clinical AI use case.
Request a nonconfidential scope discussion about vendor evidence, institutional feasibility or a separately authorized evaluation. An initial discussion does not include an assessment, app access or an engagement commitment. Do not send PHI, patient-level data, credentials or confidential technical information.
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.