"Build an HL7 ADT interface from Epic to our data lake. Validate every message and map MRN to patient_id."
Move healthcare data in minutes. Keep it for decades.
AI-assisted studios build your interfaces and APIs and convert legacy EHR data into Epic. Care Vault keeps the records your retired systems leave behind, one click away from the patient's chart.
Available in Azure MarketplaceOne for the data you're moving. One for the data you're keeping.
Both run in a dedicated environment inside your own Microsoft Azure tenant, behind the same identity, access control and audit.
AI Interface Engine
For integration architects, interface analysts, EHR migration teams and IT leaders.
- Studios
- Integration Studio for live interfaces, API Studio for partner APIs and feeds, Migration Studio for converting any EHR into Epic.
- Replaces
- 6–12 week interface builds, $200K+ legacy engine licenses and hand-built conversion scripts.
- Proof
- HL7 v2 · FHIR R4 · X12 · REST · versioned & rollbackable
Care Vault
For clinicians, HIM and release-of-information teams, compliance, and IT leaders retiring legacy EHRs.
- Does
- Archives the full record from retired systems and opens it read-only inside Epic, in the current patient's context.
- Replaces
- Keeping old EHRs running, licensed and patched only so staff can look up history.
- Proof
- SMART on FHIR launch · exact 3-field match · SHA-256 verified source
Four capabilities, one scroll.
Scroll through to watch each one run. Select a step to jump straight to it.
Describe the interface. Watch it build.
Type what should happen in plain English. Integration Studio proposes the flow, tests it against sample messages and waits for you to promote it.
Pick a direction. Ship an API.
Choose who sends and who collects. API Studio designs the REST exchange, dry-runs it, builds it and starts counting what flows through.
Pick your Epic templates. Watch them fill.
Template Readiness tracks every template from mapping through validation and rehearsal until its package is ready to export to Epic.
From the Epic chart to the archived record in four checks.
One click in the chart. Care Vault verifies the clinician, matches the patient exactly and opens the record read-only, with the source file's checksum and an audit entry.
Illustration with sample data and fictional, masked patients.
Three studios for every way healthcare data moves.
Integration Studio builds live interfaces. API Studio builds the APIs your partners call and the feeds you collect. Migration Studio converts legacy EHR data into Epic. Each is AI-assisted, tested before it reaches production, and versioned.
Design, deploy and manage live interfaces.
Describe the interface in your own words, or pick a type and follow the guided conversation. Test against a sample, promote to production, and roll back to any earlier version.
- HL7 v2 ADT, ORU, ORM, SIU and MDM in over MLLP, SFTP or Azure Blob; out over MLLP, HTTPS, SFTP or Blob.
- X12 EDI 837, 835, 270/271, 275, 276/277, 278, 820, 824 and 834, split by practice, payer or subscriber.
- FHIR R4, R4B, R5 and STU3 over REST, Subscriptions, Bulk $export and Messaging, validated against US Core and IPS.
- Document Intelligence reads faxed PDFs and scans, then sends HL7 ORU/MDM, a FHIR DocumentReference or C-CDA.
- Validation and code maps reject, quarantine, route to human review or warn; import code maps from CSV or Excel with version history.
- Transactions search every message, follow its lineage, bulk-retry, replay HL7 batches and send retroactive ACKs.
"Send ADT from our EHR to the analytics warehouse. Reject messages without an MRN and quarantine anything over 5 MB."
- Test against sample
- Promote to production
- Locked · v4
- Roll back to v3
Build APIs from a prompt, and see everything you send and receive in one place.
Say what should move between you and a partner. API Studio designs the REST exchange, dry-runs it, builds it and hands you the keys to test, then keeps watch once it's live.
- Four directions partners send to you, you collect from them, you deliver to them, or they collect from you.
- Any payload JSON, CSV, HL7, X12 or documents, carried over governed REST/JSON.
- Receive Data one-time feed keys for apps and partners, or Azure Blob intake.
- Send Data published services partners pull from, with acknowledgement and delivery retry.
- Monitor each API payloads, activity, access keys and settings; start or stop it; replay any payload.
- One list of every API filtered by needs attention, live, receiving, sending or drafts.
- Prompt
- Design
- Review
- Dry run
- Build
- Connect & test
Convert any EHR's data into Epic, starting from pre-built templates.
Bring extracts from Meditech, Allscripts, Cerner, NextGen, eCW, dental and practice-management systems, or anything else that exports. Pick the Epic templates you're loading, and Migration Studio shows what each one still needs until the package is ready.
- Pre-built Epic templates each carries its required fields, code sets, validation pack and output contract.
- Understand the source source intake, entity and category identification, data profiling and migration filters.
- AI Mapping Workbench proposes field mappings for your informaticists to approve, with code mapping and a transformation studio for the rest.
- Prove it before cutover validation center, migration rehearsal, data reconciliation and regression testing.
- Template Readiness shows each template's remaining steps; Output Package produces the export-ready load.
- Archive Plan sends whatever you don't convert to Care Vault, with replay and recovery.
- PatientsExport-ready
- Encounters (ADT)Export-ready
- Allergies & alertsRehearsal
- Medications (RDE)Validation
- Clinical notes (MDM)Review required
- Schedules (SIU)Mapping
Signs in to payer portals and runs eligibility checks from a CSV, returning structured JSON.
Store, view and share files from users, interfaces, migration projects and the archive.
System and interface health across every workspace, with alerts and recent events.
Who did what and when, and how much of your plan each team is using.
Retire the old EHR. Keep every chart one click from Epic.
When you move to Epic, decades of history stay behind in Meditech, Allscripts, Cerner or a dental system. Care Vault archives that history, keeps the original source files intact, and lets clinicians open it from the patient's chart without another login.
Licenses, servers and support contracts for a system nobody writes to anymore.
Old operating systems and unpatched apps holding years of PHI.
Records must stay retrievable for years, longer for minors, and under legal hold.
A second login, a different screen, or a request to HIM just to read an old note.
Illustration. Fictional patient, masked identifiers. Click a category to see how each kind of record shows its source.
What happens when a clinician clicks "Care Vault" in the chart
- LaunchEpic hands off securely
SMART on FHIR with PKCE. The Epic token stays on the server and never reaches the browser.
- VerifyThe clinician is checked
Their Epic identity must be linked to an active Care Vault account with the Archive Provider role.
- MatchThe patient is matched exactly
First name, last name and date of birth must match one archived patient. Zero or several matches open nothing.
- ViewThe record opens, read-only
Organized by category, with purpose of use recorded and every view written to the audit log.
Read-only by design
Nothing in the archive can be edited from the viewer. Preview and download pass through MedSyncAI, which re-checks access every time.
The right patient, or none
Exact demographic matching protects against opening the wrong chart. Ambiguous matches go to an archive administrator.
Original source evidence
The exact bytes from the legacy system are kept beside the readable record, with provenance for every displayed field.
Search beyond the launch
Authorized staff search by name, date of birth, MRN or identifier across the workspaces they're allowed to see.
Retention and legal hold
Retention periods, holds and restore status are visible on every package and record, so compliance can answer without IT.
Your tenant, your data
Each archive runs in a dedicated environment in your own Azure tenant, encrypted in transit and at rest.
Open old notes and results from the patient they already have open.
Find, preview and release records with purpose of use on every request.
Who looked at what, when and why. Legal holds visible per record.
Decommission legacy servers and licenses once the archive is verified.
Everything your Epic team needs to review and switch on Care Vault
Contact MedSyncAI to enable Care Vault. We send your organization's connection details and client ID for each Epic environment, and your Epic team activates the app. Non-production and production are set up separately.
/archive-viewer
SecuritySecurity overviewIsolation, identity and access, encryption, audit logging and how to report a vulnerability./security
PrivacyPrivacy policyWhat we collect, why, how long we keep it and how to make a privacy request./privacy
SupportSupporthello@medsyncai.us · Mon–Fri, 9:00–17:00 PT · first response within one business day./support
- Launch type
- SMART on FHIR EHR launch from an open patient chart
- Scopes
- launch · openid · fhirUser · user/Patient.read
- Launch URL
- https://<organization>-api.medsyncai.us/api/fhir/smart/archive-launch
- Writes to Epic
- None
Every legacy record ends up somewhere. You'll know where.
During an EHR migration, Migration Studio converts the data Epic needs through its pre-built templates. Everything else goes to Care Vault with its original source files. The reconciliation report says which path each record took.
Built for the business of healthcare.
Security isn't a feature. It's the architecture.
Each customer has its own environment, database and Epic registration. Healthcare data is stored and processed in your own Microsoft Azure tenant. MedSyncAI's control plane manages identity, access and audit, and does not store patient records.
Per-customer isolation
Dedicated environment, database and Epic registration. Flows execute and archives live in your tenant.
Privacy-first AI
The LLM has no ambient access to your data. Every AI assist is explicit, per-use and authorized; secrets are redacted before any prompt.
Audit-ready by default
End-to-end transaction lineage, and a logged purpose of use for every patient search, preview and download.
Buy MedSyncAI through Azure Marketplace.
MedSyncAI is listed in Microsoft Azure Marketplace as a managed application. Purchase with your Azure account, deploy into your own subscription, and pay on your Azure invoice.
- Azure MarketplaceChoose a plan
Pick Starter, Professional or Enterprise from the MedSyncAI listing.
- AutomaticYour organization is created
MedSyncAI sets up your organization on the plan you bought.
- Your subscriptionThe environment deploys
It installs into your Azure subscription and keeps its secrets in your Key Vault.
- EmailYour admin activates it
A one-time activation email lets your administrator set the first password.
| Starter | Professional | Enterprise | |
|---|---|---|---|
| Live interfaces | 10 | 25 | 50 |
| API assets | 10 | 25 | 50 |
| Migration projects | 5 | 15 | 30 |
| Users | 25 | 100 | 500 |
| Storage | 250 GB | 1 TB | 5 TB |
Pricing is on the Azure Marketplace listing. Care Vault is enabled per organization; ask us about adding it.
Questions integration and HIM leaders ask.
What is Care Vault? Care Vault
Care Vault is MedSyncAI's clinical archive. It keeps the records from EHRs you've retired, with their original source files, and lets authorized clinicians open them read-only from the patient's chart in Epic.
Does Care Vault write anything to Epic? Care Vault
No. It reads the clinician's Epic identity and the current patient's name and date of birth to find the matching archived record. It never writes to Epic.
Why might a record not open from Epic? Care Vault
First name, last name and date of birth must exactly match one archived patient. If nothing matches, or more than one patient does, no record opens, so the wrong chart is never shown.
Do we need the Interface Engine to use Care Vault? Care Vault
No. Care Vault works on its own for any legacy system you want to retire. Customers migrating with the Interface Engine get both from one reconciliation report.
What's the difference between Integration Studio and API Studio? Engine
Integration Studio builds live interfaces between systems: HL7 v2, FHIR, X12, documents and files, with routing, validation and code maps. API Studio builds REST/JSON exchanges with partners and apps: APIs they call, feeds you collect, and services they pull from, each with its own monitor page.
Can Migration Studio convert from any EHR to Epic? Engine
Yes. It works from the source system's extracts and flat files, whatever the vendor. Pre-built Epic templates set the required fields, code sets and validation for each kind of data, and Template Readiness shows what's left before each package can be exported.
Can we buy MedSyncAI through Azure Marketplace? Engine Care Vault
Yes. MedSyncAI is a managed application in Azure Marketplace with Starter, Professional and Enterprise plans. It deploys into your Azure subscription and is billed on your Azure invoice.
Does MedSyncAI support HL7 and FHIR integration? Engine
Yes: HL7 v2, FHIR, X12, EHR connectivity, routing, validation, mapping and production deployment.
Can MedSyncAI replace a legacy interface engine? Engine
Import existing interfaces with routing intact, then extend, refactor or document them in plain English.
How does MedSyncAI protect PHI? Engine Care Vault
Each customer has a dedicated environment, database and Epic registration in their own Azure tenant. The control plane manages identity, access and audit, and stores no patient records.
See it on your data.
Tell us what you're building or retiring. We'll show a working interface against one your team needs, or open a sample of your legacy records in Care Vault.
We respond within one business day. Never include patient information in this form. Existing customers: see Support.