HomeMedSyncAI Archive Viewer
Documentation & trust

MedSyncAI Archive Viewer

Documentation for clinicians, Epic analysts, and IT and security reviewers.

Overview

MedSyncAI Archive Viewer is a read-only web application for viewing legacy (historical) patient records that a healthcare organisation has archived from retired systems using MedSyncAI Migration Studio.

Clinicians can open a patient’s archived record directly from Epic, in context, without a separate login to the old system. Archived records are read-only; nothing in the archive can be edited from the viewer.

Key features

  • Launch from Epic in the current patient’s context using SMART on FHIR EHR launch.
  • Search inside the viewer by patient name, date of birth, MRN or identifier.
  • Select a workspace (archive) when an organisation has more than one archive.
  • View archived clinical information, organised by category, with read-only access.
  • Download original archived source files, with integrity verification.
  • Every patient search and record access is logged for audit.
  • Automatic sign-out after inactivity; the timeout is configurable. Default: 15 minutes of inactivity signs the user out. Each organisation can change the inactivity timeout from 1 to 120 minutes.
  • Purpose of use is recorded with each request (Treatment by default for clinicians launching from Epic).

How the Epic launch works

  1. The clinician opens “Archived Records” from the patient’s chart in Epic.
  2. Epic launches MedSyncAI using SMART on FHIR: the OAuth 2.0 authorization code flow with PKCE. The clinician approves access in Epic if prompted.
  3. Epic returns the clinician’s identity and the current patient context to the organisation’s MedSyncAI environment. The Epic access token stays on the server; it is never sent to the browser.
  4. MedSyncAI checks that the Epic clinician is linked to an authorised MedSyncAI account with the Archive Provider role.
  5. The clinician selects the archive workspace if there is more than one.
  6. MedSyncAI opens the archived record only when the patient’s first name, last name and date of birth all match exactly. If there is no exact match, or more than one, no record is opened and the clinician is told so.

Requested Epic scopes: launch, openid, fhirUser, Patient read (demographics).

User and access requirements

  • The organisation’s Epic environment must have the MedSyncAI Archive app enabled.
  • The organisation’s MedSyncAI administrator links each clinician’s Epic identity to a MedSyncAI account. Unlinked users cannot open records.
  • Users need the Archive Provider role. Access is limited to workspaces for which they are authorised.
  • Supported browsers: current versions of Microsoft Edge and Google Chrome. Inside Epic, Archive Viewer opens in Epic's embedded browser.

Organisation-specific endpoints

Each organisation has its own MedSyncAI endpoints, provided during onboarding. Examples below are illustrative, not active launch links.

Epic launch and callback
https://<organisation>-api.medsyncai.us
Archive Viewer
https://<organisation>-archive.medsyncai.us

Implementation guide for Epic analysts

This section is for the organisation's Epic analysts and IT team. MedSyncAI completes its own setup during onboarding; the steps below are what the organisation configures or provides. Each Epic environment (for example non-production and production) is set up separately.

Before you start

  • Contact MedSyncAI to enable Archive Viewer. We provide your organisation's connection details, and your Epic team activates the app in your Epic environment.
  • MedSyncAI has set up your organisation's environment and given you your two endpoints: https://<organisation>-api.medsyncai.us (Epic launch and callback) and https://<organisation>-archive.medsyncai.us (Archive Viewer).
  • Your legacy records have been archived into MedSyncAI and at least one archive workspace is ready.

Step 1 — Send MedSyncAI your Epic details

For each Epic environment you want to connect, send MedSyncAI:

ItemExampleWhy it is needed
Epic FHIR base URL (the "iss" value Epic sends at launch)https://fhir.example-health.org/api/FHIR/R4 (illustrative)MedSyncAI accepts launches only from FHIR servers registered to your organisation.
Environment nameNon-production, ProductionEach environment is registered separately.
Primary technical contactName and work emailFor launch testing and issues.

Do not send patient information. MedSyncAI tells you which Epic client ID to use for each environment during onboarding.

Step 2 — Configure the launch in Epic

Configure an EHR launch (SMART on FHIR) for the MedSyncAI Archive app from the patient's chart, for example an 'Archived Records' activity or link. In Epic this is typically done by your Epic analyst through the app's integration (FDI) configuration.

SettingValue
Launch typeSMART on FHIR EHR launch (from within a patient's chart)
Launch URLhttps://<organisation>-api.medsyncai.us/api/fhir/smart/archive-launch
Parameters Epic must sendiss (your Epic FHIR base URL) and launch (Epic's one-time launch token) — Epic adds these automatically for a SMART EHR launch
Redirect URI (registered on the app)https://<organisation>-api.medsyncai.us/api/fhir/smart/callback
Scopes requestedlaunch, openid, fhirUser, user/Patient.read
Patient contextRequired — the launch must be made from an open patient chart
Client IDProvided by MedSyncAI for each environment
The launch URL and redirect URI use your organisation's own MedSyncAI address. Do not use another organisation's address or a generic medsyncai.us address. MedSyncAI registers the redirect URIs on MedSyncAI's Epic app, one set per organisation, for example https://<organisation>-api.medsyncai.us/api/fhir/smart/callback. The organisation does not configure them.

Step 3 — Link clinicians to MedSyncAI accounts

MedSyncAI opens archived records only for Epic clinicians who are explicitly linked to an active MedSyncAI account that has the Archive Provider role. A clinician who is not linked cannot open any archived record.

Epic identifies each clinician by a FHIR Practitioner reference (the 'fhirUser' value, for example Practitioner/eAbC123). Your organisation's MedSyncAI administrator links each of these to the clinician's MedSyncAI account. Links can be disabled at any time to remove access.

Provide for each clinicianNotes
Epic Practitioner FHIR ID (fhirUser)One per Epic environment; non-production and production IDs can differ
Name and work emailUsed to create or find the MedSyncAI account
Archive workspaces they may accessAccess is limited to these workspaces

Your organisation's Epic or IT administrator approves the list of clinicians who may use Archive Viewer and sends it to MedSyncAI through a secure channel agreed during onboarding. Do not send patient information with the list.

Step 4 — Check patient demographics

MedSyncAI opens an archived record only when the Epic patient's first name, last name and date of birth exactly match one archived patient. Matching ignores letter case and extra spaces, and accepts any of the patient's recorded names, but does not match nicknames, initials or misspellings. Patients without a first name, last name or date of birth in Epic cannot be matched.

Step 5 — Test the launch

  1. In the Epic environment you are testing, open the chart of a test patient who also exists in the archive.
  2. Open the MedSyncAI Archive activity or link. Approve access if Epic asks.
  3. Choose the archive workspace if you are asked to.
  4. Confirm the Archive Viewer opens that patient's archived record.
  5. Also test a patient who is not in the archive: no record should open, and the viewer should say no archived patient matches.
  6. If anything fails, see Troubleshooting below and send MedSyncAI the request reference shown on screen.

Going live

  • Repeat steps 1–5 for the production Epic environment; production uses its own Epic FHIR base URL, client ID and clinician IDs.
  • Production launches use the same two organisation-specific MedSyncAI addresses unless MedSyncAI tells you otherwise.
  • To remove a clinician's access, ask your MedSyncAI administrator to disable their link or account.

Troubleshooting

If a launch fails, note the time, the message shown and any request reference, and contact Support. Never send patient details or screenshots that show patient information.

What you seeWhat it meansWhat to do
Archived patient not found — No archived patient matches the patient opened in Epic.No archived patient has exactly the same first name, last name and date of birth in the selected workspace.Check you selected the right workspace. Check the patient's name and date of birth in Epic. If the patient should be in the archive, contact your archive administrator.
Patient match requires review — More than one archived patient matches the Epic patient context. Contact an archive administrator.More than one archived record has the same name and date of birth, so no record is opened, to avoid showing the wrong patient.Contact your archive administrator; use the viewer's patient search to review the candidates if you are authorised.
Epic launch expired — Return to Epic and open Archived Records again.The one-time launch link is valid for 5 minutes and can be used once.Start the launch again from the patient's chart in Epic.
Access denied — You do not have access to this archive context.Your account is not authorised for this workspace or action.Ask your archive administrator to check your workspace access and role.
"Session expired — Sign in again to continue." / "You were signed out after N minutes without activity."Your session ended, or you were inactive longer than the timeout.Open the activity again from Epic.
Request timed out — MedSyncAI did not respond in time. Try again.A temporary delay.Try again. If it keeps happening, contact Support with the time and request reference.
"Archive unavailable" or "MedSyncAI could not be reached."MedSyncAI or the network is temporarily unavailable.Try again later; contact Support if it continues.
"Epic account not linked — Your Epic user is not linked to a MedSyncAI Archive account." / "Archive access not enabled" / "Archive account unavailable"Your Epic user is not linked to a MedSyncAI account, or the linked account is inactive or is not an Archive Provider.Ask your organisation's MedSyncAI administrator to link your Epic user or enable the account (see Implementation guide, step 3).
Patient details incomplete — The patient in Epic needs a first name, last name and date of birth before archived records can be matched.Matching is not safe without all three.Complete the patient's demographics in Epic, or locate the record with the viewer's search.
No patient selected — Open Archived Records from within a patient's chart in Epic.The app was launched without an open patient chart.Launch it from within a patient's chart.
"Access not approved" or "Epic sign-in failed" / "Epic sign-in incomplete" / "Epic patient unavailable" / "Epic launch failed"Epic did not approve the access request, or Epic could not complete the sign-in or return the patient.Return to Epic and open Archived Records again. If it keeps happening, contact Support with the time.
A technical error page that mentions archive_smart_issuer_not_registeredThe Epic environment you launched from is not registered with your MedSyncAI environment.Ask your Epic analyst to contact MedSyncAI (Implementation guide, step 1).
An Epic error about the redirect URI, or "invalid client"The redirect URI or client ID in Epic does not match your MedSyncAI setup.Your Epic analyst should check the settings in Implementation guide, step 2.

Message wording may change slightly between releases. The request reference is the most useful detail to send to Support.

Frequently asked questions

Does MedSyncAI write anything to Epic?

No. The app reads the clinician's identity and the current patient's demographics only.

What does MedSyncAI read from Epic?

The clinician's Epic identity (fhirUser) and the current patient's name and date of birth, used to find the matching archived record. Other identifiers and gender may be read but are not used for matching and are not stored by the launch.

Is the Epic access token stored in the browser?

No. It stays on the MedSyncAI server and is used only to read the patient's demographics during the launch.

Can a clinician open any patient in the archive?

From an Epic launch, only the archived record that exactly matches the patient open in Epic. Using the viewer's own search, Archive Providers can search the workspaces they are authorised for; every search and record view is logged for audit.

Why didn't the record open even though the patient is in the archive?

The first name, last name and date of birth must match exactly, and only one archived patient may match. See Troubleshooting.

Can archived records be edited?

No. The Archive Viewer is read-only.

How long does a clinician stay signed in?

The session ends after a period of inactivity. Default: 15 minutes of inactivity signs the user out. Each organisation can change the inactivity timeout from 1 to 120 minutes.

Do we need separate setup for non-production and production?

Yes. Each Epic environment has its own Epic FHIR base URL, client ID and clinician IDs, and is registered separately.

Data handling

Each organisation’s archive runs in a dedicated environment. Customer healthcare data is stored and processed in the customer's own Microsoft Azure tenant. MedSyncAI's control plane manages identity, access and audit, and does not store patient records.

Archived data is encrypted in transit using HTTPS/TLS and at rest. MedSyncAI reads only the Epic patient demographics needed to find the matching archived record (name and date of birth); it does not write to Epic.

Read the security overview and Privacy Policy.

Support

Email: hello@medsyncai.us.

Monday to Friday, 9:00 to 17:00 Pacific Time, excluding US public holidays. First response is within one business day.

See Support for what to include in a request. Never send patient details or protected health information (PHI) by email.