Hospital readiness checklist
Evaluation, not certification
EchoReview supports study handoff, cardiologist review, and documented sign-off. This is a workflow evaluation offer, not a validated clinical service. No HIPAA compliance, SOC 2 attestation, ISO certification, regulatory clearance, or guaranteed turnaround is asserted here.
Required agreements and provider coverage
BAA and DUA drafts are discussion templates, not executed agreements or evidence that identifiable patient data may be handled. Hospital counsel must approve the scope and execute required agreements. Verify coverage for every service receiving data before any identifiable data is sent.
Review the actual data flow
Routine single and bulk uploads and connector deliveries do not invoke experimental hosted AI. Routine reporting excludes AI findings and AI-seeded drafts. Separate research benchmarks remain available to administrators; verify the approved data flow before a hospital patient-data pilot. AI must never guide clinical urgency, routing, diagnosis, or treatment.
Validate access and audit records
Workspace access, role controls, sign-off locking, and audit features exist in the app. Test approved accounts, image authorization, workspace isolation, revocation, and correction records. Do not assume every event or field is captured; confirm required coverage with evidence.
Obtain security and operational evidence
Confirm hosting and processing regions, encryption configuration, subprocessor contracts, risk assessment, independent security testing, retention and deletion, incident procedures, backups, and restoration tests. Published wording is not proof of these controls. Any required SSO, MFA enforcement, or service levels need site-specific verification.
Report return to the chart: today and Phase 2
Today (pilot): signed reports are returned manually. Staff copy the signed report into the chart using the hospital's own case number, then confirm placement in EchoReview. The confirmation covers the exact signed report and addendums, and any new addendum requires reconfirmation, so misplaced or missing reports are visible.
Phase 2 (planned, not yet built): structured exports designed to drop into EHR templates without retyping: a fixed-section text report matching common echo report templates, HL7 v2 ORU result messages, and FHIR R4 DiagnosticReport resources, delivered back through the hospital's interface engine. Each format will be built and tested with the hospital's IT team before use.
Test image delivery at the hospital
The on-site connector is available for evaluation, not a hospital-validated integration. Test fidelity, frame order, timing, complete-study reconciliation, supported formats, duplicates, failed deliveries, retries, and recovery. Metadata stripping does not remove text burned into pixels or identifiers in notes.
Agree clinical and evaluation responsibilities
Confirm reader availability, licensing, credentialing, insurance, escalation ownership, support, fees, and success measures. Keep the hospital’s established clinical read and escalation process authoritative. Local governance determines whether research / QI review or IRB approval is required; AI regulation is a separate future assessment.