SourceLace Docs
FAQOpen the app

Health records: Epic, Oracle Health and MEDITECH

How to connect an electronic health record (EHR) through its FHIR R4 API with SMART on FHIR sign-in, for read-only clinical data. One connector covers Epic, Oracle Health (Millennium, formerly Cerner), MEDITECH Expanse and other certified EHRs; a small vendor profile sets what differs between them. Each clinician signs in with their own EHR account, so the EHR's own access rules apply to every read.

Status: Pilot. New or partial, offered to pilot customers. Built against the SMART App Launch and FHIR R4 standards and the vendors' published documentation, and covered by automated tests against a simulated FHIR server. On 16 October 2026 SourceLace checked what Epic, Oracle Health and MEDITECH publish about their FHIR APIs (which resources, searches and scopes each offers), and tried read-only searches on Oracle Health's public test system, which holds only made-up patients. On 18 October 2026 SourceLace signed in to Epic's public test system with Epic's own test logins and read Epic's made-up test patients. How MEDITECH's systems answer searches has not been tried yet, and SourceLace has not yet signed in to a hospital's own system.

At a glance

Connects through Sign-in Network Status First test question
Health records (FHIR) The EHR's FHIR R4 API, with SMART on FHIR sign-in Personal sign-in Allow SourceLace's IP addresses, if the EHR limits them; a private address needs a SourceLace Runner, for AI agents only (Enterprise plan) Pilot; test data only "Which resource types does fhir:sandbox offer?"

Add each source with the usual steps. The network answers are explained in What your network needs. If the first test question fails, the error message tells you what to fix: look it up under When something goes wrong below.

Before you connect: no business associate agreement yet

A FHIR source holds protected health information (PHI). Under HIPAA, a service that stores PHI for a hospital, even briefly and encrypted, is a business associate and needs a signed business associate agreement (BAA) with the hospital first.

SourceLace has no HIPAA business associate agreement program yet, and does not claim HIPAA compliance. Until a BAA is signed between your organization and SourceLace (and SourceLace has matching agreements with the providers it uses, including the AI model provider), do not connect a FHIR source to production patient data. Use only a vendor sandbox or a test environment with synthetic patients. See Security and privacy.

What people can do

  • search_schema lists the resource types the EHR offers (from its CapabilityStatement), and describe_object lists one type's search parameters.
  • query (language fhir_search) runs one FHIR search, written as a small JSON object:
{"resource": "Observation",
 "params": {"patient": "erXuFYUfucBZaryVksYEcMg3", "category": "laboratory", "date": ["ge2026-01-01", "lt2026-07-01"]},
 "count": 50, "elements": ["code", "valueQuantity", "effectiveDateTime"]}

params are FHIR search parameters (with an optional :modifier); a list repeats a parameter, such as a date range. count is the page size (at most 200), elements limits the elements returned, include takes at most 3 _include values such as MedicationRequest:medication, and sort takes values such as -date. Anything else is refused before it is sent, and so is a parameter the EHR does not list for that resource type. SourceLace follows the result's next-page links up to the row cap and the time limit.

  • Rows have one column per element, with nested elements as dotted names such as code.coding.0.code. get_record with a resource type and id (such as Patient and 12724066) returns the whole resource.
  • Many EHRs only search clinical data for one patient at a time: find the patient's id with a Patient search first.
  • Some EHRs need a time on dates. Oracle Health refuses ge2026-10-15 on encounter and appointment searches; write ge2026-10-15T00:00:00Z (midnight, UTC) instead. A date alone works for test results (Observation).
  • Some EHRs ignore sort and elements, and send fewer rows per page than count asks for (Oracle Health sends 25). SourceLace still reads the next pages up to the row cap; sort the rows yourself if the order matters.
  • These sources never accept changes, and bulk export ($export) is not offered yet.

You can combine health records with another system in one question. Name a resource type as a table, for example "Observation", and join it to your other table by the patient's reference (subject_reference, written as Patient/123) or id. Columns are named with underscores, such as code_coding_0_code. Search with describe_object to see them. A page of records that SourceLace cannot read to the end is refused, never shown as complete. Some EHRs (Epic, Oracle Health) refuse a search that names no patient or id: start from the other table and join on the patient.

Every answer that read health records carries the note "The text below is written by the assistant from health or claims records and is not checked; check the records." by design, so it never shows "all clear"; if the line cannot be built it says "Answer check: SourceLace could not check this answer" (see The line under an answer).

Patient identifiers are masked by default

Every FHIR source has the option protect_patient_identifiers, which is on unless an admin sets it to off. While it is on, SourceLace masks, for every caller (AI apps, the SourceLace app and AI agents):

  • in Patient, RelatedPerson and Person resources: names, contact details, addresses, identifiers (such as medical record numbers), photos and contacts; the birth date keeps only its year;
  • in Coverage resources: member and subscriber numbers;
  • in every resource: the display name on any reference to a patient or other person, and the narrative text.

Masked values read [masked]. Clinical content and FHIR ids (such as Patient/12724066) stay, so searches and get_record still work. Masking is not de-identification: ids are still unique per patient, and free text written by clinicians (notes, attached documents) is not scanned.

Your organization's data protection rules apply on top of this. Turn on its detectors (email addresses, phone numbers, Social Security numbers, and your own patterns such as your medical record number format) to mask identifiers inside clinicians' free text too. The [masked] values cannot be shown again in the SourceLace app, and there are no per-group exceptions: the option is on or off for the whole source.

The audit trail and how long results are kept

  • The audit trail records each FHIR search's resource type, parameter names and options, but never the values typed into them: {"resource":"Patient","params":{"family":"[redacted]","birthdate":"[redacted]"}}. Text typed into search_schema for a FHIR source is not kept either.
  • Results read from a FHIR source are held for 5 minutes (the Health record results kept limit), not the usual 30, and your data retention settings can shorten that further.

Set it up

Who sets it up: for Epic and Oracle Health, SourceLace has already registered its own app with the vendor, so there is nothing to register. Your hospital's EHR team activates SourceLace's app in their Epic or Oracle Health system (step 1), then your SourceLace admin adds the source and only has to enter the FHIR base URL (step 2). MEDITECH and other EHRs still need an app registered for SourceLace, as described in Advanced: bring your own app. The detailed guide for the EHR team, per vendor, is below; support@sourcelace.com can send it as a one-page checklist.

What your EHR team does

Once per EHR environment (the hospital's test system and its live system are each activated separately). Plan for days to weeks, mostly waiting for the hospital's own approvals.

Who: the hospital's EHR administrators (for Epic, its Epic analysts; for Oracle Health, its Oracle Health administrator).

Before you start, ask SourceLace support for: the client ID of SourceLace's app for your vendor, for the right system (test or live; Oracle Health also has one per SMART version, and support tells you which). A client ID is not a password: SourceLace's app is a public client, which has no secret. Write down your EHR's FHIR R4 base URL (it usually ends in /R4, such as https://fhir.corvanta-health.org/api/FHIR/R4; not a DSTU2 or STU3 address).

  1. Activate SourceLace's app in your EHR, using the client ID, as the vendor sections below describe.
  2. Allow the app's scopes. SourceLace asks to read only (the default list, including Appointment and Coverage). If you narrow what the app may read, tell your SourceLace admin, who then lists the same scopes on the source.
  3. Decide who may use it in the EHR: SourceLace shows each clinician only what their own EHR access allows.
  4. Send your SourceLace admin the FHIR R4 base URL, and say whether it is a test or a live system.

Check that it worked: after your SourceLace admin adds the source, one person clicks Connect, signs in with their EHR login, asks "Which resource types does fhir:sandbox offer?", and then asks for a test patient's allergies. If either fails, look up the message under When something goes wrong.

The redirect URL of SourceLace's apps is already registered, so your team does not enter one. (Only if you bring your own app is it:)

https://mcp.sourcelace.ai/connect/callback

What your admin does in Epic

Who: the hospital's Epic analysts, with the security point that lets them download apps (Epic's documentation calls it "Purchase Apps"; the exact name can differ in your Epic, so ask your Epic technical coordinator). The organization may also need to have signed Epic's open.epic agreement, once for all apps; your Epic technical coordinator knows whether it is already in place.

  1. Get SourceLace's Epic client ID from SourceLace support: the Non-Production one for your test environment, the Production one for the live system.
  2. In your Epic environment, search for the app by that client ID and confirm the download, as Epic's documentation describes for apps from outside the hospital. If the form asks how long a sign-in lasts, choose a refresh token duration that suits your policy: it decides how often clinicians sign in again.
  3. Wait for the client record to reach your environments. Epic's documentation says apps that need no secret are approved automatically and then synced; how long that takes is not stated, so allow some hours and check again.
  4. Give your SourceLace admin the hospital's FHIR R4 base URL (it ends in /api/FHIR/R4) and say whether it is a test or live system.

Scopes: Epic says it takes SMART v2 scopes, so SourceLace asks for user/Patient.rs and the like. If Epic refuses them with invalid_scope, ask your SourceLace admin to set Scope syntax to v1.

Check that it worked: as above. If the sign-in is refused, check that the client ID you activated is the one for this address (test ID with a test system, production ID with the live one) and that the download shows as approved.

Epic's own guide: Epic on FHIR.

What your admin does in Oracle Health

Who: the hospital's Oracle Health administrator, who decides for each domain which apps may run and which users and roles may use them (Oracle Health's documentation says each customer decides this domain by domain).

  1. Get SourceLace's Oracle Health client ID from SourceLace support, and note which SMART version (v1 or v2) it was registered with.
  2. In Oracle Health, make the app available in your domain (test domain for testing, live domain for real use) and choose which users and roles may use it. Oracle Health's guide is "Making Self-Developed SMART Apps Available in Your Domain" in its Millennium documentation. The screens differ by Oracle Health setup and are not described in Oracle's public pages, so if you cannot find them, ask your Oracle Health contact.
  3. Give your SourceLace admin the domain's FHIR R4 base URL (on cerner.com, ending in /r4/ and the domain's id), the SMART version of the app you enabled, and whether it is a test or live domain.

Scopes: SourceLace asks Oracle Health for SMART v1 scopes (user/Patient.read) by default. If you enabled the SMART v2 app, your SourceLace admin sets Scope syntax to v2, and SourceLace asks for read-and-search scopes such as user/Patient.rs. The scope syntax must match the app's SMART version: a mismatch is refused with invalid_scope. Oracle Health does not accept wildcard scopes such as user/*.read, and it has no user/Medication.read (medications are read through MedicationRequest), so SourceLace does not ask for it.

Searches Oracle Health does not offer. Oracle Health searches encounters, conditions and coverage for one patient at a time, and appointments only for one location, patient or practitioner, always with a date range that has times. It cannot search encounters by class (inpatient or outpatient) or conditions by code. So on Oracle Health the healthcare pack sets up only the eligibility check, which searches one clinic at a time (see Which healthcare agents work with your EHR).

Finding your clinics' Location ids (for the eligibility check's Clinic locations): ask your Oracle Health administrator for the location ids of the clinics whose schedules to check, or, once connected, ask SourceLace: {"resource": "Location", "params": {"address-city": "<the clinic's city>"}} and copy the id column (a number such as 32216049). Oracle Health refuses a Location search by name alone: give a city, another part of the address, or a location type. A patient's appointments also name their clinic's Location among the participants.

Oracle Health's own guide: Oracle Health Millennium FHIR.

What your admin does in MEDITECH

SourceLace does not have its own MEDITECH app yet, so MEDITECH needs your own app. Who: the hospital's MEDITECH contact. MEDITECH issues the client id (and secret) through its Greenfield program; each hospital then enables the app for its own system.

  1. Ask MEDITECH, through Greenfield, to register an app for SourceLace as a clinician app with standalone launch and SourceLace's redirect URL (shown above).
  2. Ask for read access to every resource type in SourceLace's default list, including Appointment and Coverage.
  3. Give your SourceLace admin the client id (and the secret, for a confidential client).
  4. Use MEDITECH's US Core STU6 FHIR base URL, which looks like https://greenfield-prod-apis.meditech.com/v2/uscore/STU6 (your hospital's may differ). Do not use the older address ending in /uscore/R4: it does not offer Coverage, so the eligibility check cannot read insurance there.
  5. Your SourceLace admin sets EHR vendor to MEDITECH (SourceLace also picks it for an address on meditech.com), so the client secret is sent the way MEDITECH expects.

Scopes: MEDITECH says it takes SMART v2 scopes, but lists only the older form for some resources (user/Patient.read, user/Appointment.read, user/Condition.read, user/Observation.read and user/DocumentReference.read). With Scope syntax on automatic (the default), SourceLace asks for each resource in the form MEDITECH lists, and for the others in the v2 form (user/Encounter.rs). Leave it on automatic unless MEDITECH tells you otherwise.

Check that it worked: as above. If the sign-in is refused with invalid_scope, ask MEDITECH which scopes the app has, and make scopes match them.

MEDITECH's own guide: MEDITECH Greenfield.

Advanced: bring your own app

Most organizations should use SourceLace's own app (above). Register your own app only if your organization's rules require an app it owns, or the EHR is MEDITECH or another vendor SourceLace has no app for. It is more work and more to maintain, and the redirect URL below must stay registered.

Who: the hospital's EHR administrators, with a developer account on the vendor's site where the vendor asks for one.

  1. Register an app with the EHR, for clinicians (not patients), with standalone launch and the redirect URL above.
  2. Choose public or confidential. Ask for a public client (no secret, PKCE instead) where the EHR offers it. If the EHR issues a client secret, SourceLace stores it encrypted and never shows it again. Tell your SourceLace admin which it is: a public client's secret field stays empty.
  3. Match the scopes. The scopes registered for the app must include those SourceLace asks for (the defaults, or the source's scopes), including Appointment and Coverage, or the sign-in is refused with invalid_scope (see the table below).
  4. Give people access in the EHR.
  5. Send your SourceLace admin the app's client id (and secret), which they enter on the source under Client ID (bring your own app).

In Epic, register on fhir.epic.com (Build Apps) for clinicians or administrative users, select the R4 read and search APIs of every resource type in the default list, and use the Non-Production Client ID for test systems and the Production Client ID for live ones; your Epic analysts then activate it as above. In Oracle Health, register in the code console (code-console.cerner.com) as a provider app with standalone launch and Offline access, tick each user/<Resource>.read (SMART v1) or .rs (SMART v2) scope in the default list, and your Oracle Health administrator then makes it available in their domain.

This redirect URL is built from SourceLace's web address. If that address ever changes, the redirect URL changes with it: every app of your own then needs the new redirect URL added to its registration, keeping the old one until the change is finished, or sign-ins fail with a redirect URL error.

Add the source (SourceLace admin)

Kind: Health records (FHIR) (fhir). For Epic and Oracle Health you only need the base URL (and, if the address does not show it, the vendor and whether it is a live or test system).

Option Type Default Example What it is
base_url Address (required) https://fhir.corvanta-health.org/api/FHIR/R4 The EHR's FHIR R4 base URL, from the hospital's EHR team. Must start with https://. A copied .../metadata or .../.well-known/smart-configuration address also works.
vendor (EHR vendor) Choice from the address Epic Epic, Oracle Health, MEDITECH or another SMART on FHIR server: picks SourceLace's app (Epic and Oracle Health), the default scopes, how a client secret is sent and which healthcare pack agents are set up. Left empty, an address on cerner.com means Oracle Health, one on meditech.com means MEDITECH, and one ending in /api/FHIR/R4 means Epic.
ehr_environment (Live or test system) Choice from the address Test Which of SourceLace's apps for the vendor is used: the one for live systems or the one for test systems. Left empty, Epic's and Oracle Health's public sandboxes count as test and every other address as live. Choose Test for a hospital's own test environment.
client_id (Client ID, bring your own app) Text (empty) 0f4b7c3e-... Advanced. Leave empty to use SourceLace's own app (Epic and Oracle Health). Fill in to use an app your organization registered (how); required for MEDITECH and other EHRs.
client_secret Secret (none) Only with your own client_id, and only for a confidential client. Stored encrypted, never shown again.
scopes Text (the profile's list) openid fhirUser offline_access user/Patient.read user/Observation.read Normally left empty, so SourceLace asks for the default list below. Fill it in only to replace that list, such as when the app was activated with fewer scopes. This is not where you choose SMART v1 or v2: that is Scope syntax, the next option. Only user/ read scopes and openid, fhirUser, profile, offline_access, online_access are accepted.
scope_version (Scope syntax) Choice the vendor's v1 v1 (user/Patient.read), v2 (user/Patient.rs) or automatic. Automatic uses v2 when the EHR's SMART configuration says it supports it, and for each resource the form the EHR's published scope list names, where it names only one (MEDITECH lists user/Patient.read but not user/Patient.rs). The Oracle Health profile uses v1 unless you choose v2 here, for the SMART v2 app; with SourceLace's own Oracle Health app this also picks which of its two apps is used. Choosing v1 or v2 here writes every scope that way, including the default list used when scopes is empty.
protect_patient_identifiers (Mask patient identifiers) On or Off On Off Masks patient identifiers for every caller, as described above.

The default scopes are openid fhirUser offline_access plus a read scope for each of these resource types: the US Core set (Patient, Encounter, Condition, Observation, DiagnosticReport, MedicationRequest, Medication, AllergyIntolerance, Procedure, Immunization, DocumentReference, CarePlan, CareTeam, Goal, Practitioner, Organization and Location), plus Appointment (upcoming and past visits) and Coverage (the patient's insurance: plan, status and dates), which the healthcare pack's visit and eligibility checks use. For Oracle Health the list has no Medication: Oracle Health has no Medication resource and no user/Medication.read scope. If the app as activated in your EHR does not include Appointment or Coverage, ask your EHR team to add them, or set scopes to leave them out; the agents that need them then say they could not read them. offline_access gives a refresh token where the EHR allows it, so people do not sign in again every few minutes; it is stored encrypted like every other sign-in.

Saving the source reads the EHR's public SMART configuration (.well-known/smart-configuration, or its CapabilityStatement), without any credentials, to find where people sign in. If the base URL changes later, everyone signs in again: a sign-in is never sent to another address.

Which healthcare agents work with your EHR

The healthcare pack's agents need some searches across the whole hospital, such as "every inpatient admitted in the last 24 hours". Not every EHR offers them. What was checked on 16 October 2026: what each vendor publishes about its FHIR API, and, for Oracle Health only, read-only searches on its public test system.

Agent Epic Oracle Health MEDITECH
Daily admissions digest Not yet checked Does not work: no hospital-wide encounter search Not yet checked
Care gap focus list Not yet checked Does not work: conditions are searched one patient at a time, and not by code Not yet checked
Weekly readmissions watch Not yet checked Does not work: no hospital-wide encounter search Not yet checked
Readmission alert Not yet checked Does not work: no hospital-wide encounter search, and no search by class (inpatient) Not yet checked
Discharge follow-up check Not yet checked Does not work: no hospital-wide encounter search Not yet checked
Eligibility before the visit Not yet checked Works one clinic at a time: fill in Clinic locations Not yet checked
  • Not yet checked means Epic's and MEDITECH's published descriptions offer the searches the agent uses, but no search has been tried on their systems yet. If the EHR refuses a search, the agent stops and says so in its run; it does not search patient by patient.
  • Does not work on Oracle Health: Oracle Health searches encounters, conditions and coverage for one patient at a time only. When you choose an Oracle Health source for the healthcare pack, these five agents are left out, and the pack's suggestions say why. Making one of them from its template with an Oracle Health source is refused with the same reason. Instead, ask about a short list of patients with the pack's skills (Readmission review, Discharge follow-up check, Health records questions), giving their FHIR ids.
  • Eligibility before the visit on Oracle Health: Oracle Health searches appointments only for one location, patient or practitioner. Fill in the agent's Clinic locations with your clinics' FHIR Location ids, separated by commas (how to find them); the agent then checks each clinic's schedule in turn. Without them it stops and says it needs them.

Whichever EHR you use, these agents read and report only. A qualified person on your team makes every clinical, billing and coverage decision, and the pack is for test data only until business associate agreements are in place. Using it does not meet HIPAA's requirements for you: SourceLace does not claim HIPAA compliance.

When something goes wrong

What you see What to do
"... is a FHIR DSTU2 address; SourceLace needs the EHR's FHIR R4 base URL ..." (or STU3) Ask the EHR administrators for the R4 base URL (usually ending in /R4).
"Sign-in to ... failed: the EHR did not accept SourceLace's client (...)..." With SourceLace's own app (Epic, Oracle Health): your EHR team has not activated it yet for this system, or activated the other one (test instead of live, or the other SMART version). Check with them, and check Live or test system and Scope syntax on the source. With your own app: check whether it is public or confidential: a confidential client needs its secret, a public one none. Set EHR vendor so the secret is sent the way that EHR expects.
"SourceLace's own ... app is not set up for live (or test) systems yet, and ... has no client id of its own." SourceLace has not yet been given its app's client ID for that kind of system. Contact support@sourcelace.com, or enter your own app's client id under Client ID (bring your own app).
"The option ehr_environment of ... must be production or test." Choose Live or Test under Live or test system, or leave it empty.
"Sign-in was not completed: ... (error invalid_scope). The EHR refused the scopes SourceLace asked for ..." Make scopes match what your EHR team allowed the app to read (step 2 of What your EHR team does), and set Scope syntax to the SMART version the app was registered with (v1 or v2; for Oracle Health, the code console's SMART Version). An app registered before SourceLace added Appointment and Coverage to its defaults needs those two added to its registration, or left out of scopes.
"SourceLace could not find the sign-in addresses of ..." Check base_url with the EHR administrators: it must be the FHIR R4 base URL that supports SMART on FHIR.
"... is a private network address ..." SourceLace's cloud only calls EHRs on the internet. Use the hospital's public FHIR address, or a SourceLace Runner inside its network.
"'automatic' in ...'s Scopes is a scope syntax, not a scope. Leave Scopes empty ..." (or 'auto', 'v1', 'v2') Someone typed the SMART version into Scopes. Empty the Scopes field (SourceLace then uses its default list) and choose automatic, v1 or v2 under Scope syntax instead.
"The scope '...' in ...'s scopes is not allowed." Use only user/ read scopes.
"Oracle Health does not accept wildcard scopes ..." List each resource, such as user/Patient.read user/Observation.read.
"... did not say who signed in." Keep openid fhirUser in the scopes, and ask your EHR team to allow them for the app.
"... refused to show ...: your sign-in does not include permission for it." Ask your EHR team to allow that resource's read scope for the app, add it to scopes if you narrowed them, then connect again.
"... only searches ... for one patient at a time." Add the patient's id to the search. On Oracle Health this is how encounters, conditions and coverage are always searched; see Which healthcare agents work with your EHR.
"... only searches Appointment with location, patient or practitioner given." Oracle Health searches appointments for one clinic, patient or practitioner at a time. Add one of them, such as {"location": "<Location id>"}. For the eligibility check, fill in its Clinic locations with your clinics' FHIR Location ids (how to find them).
"... only searches Appointment with date given." Add a date range with times, such as "date": ["ge2026-10-17T00:00:00Z", "lt2026-10-18T00:00:00Z"].
"... needs a time on ... dates: write ge2026-10-15T00:00:00Z, not ge2026-10-15." Oracle Health refuses a date without a time on encounter and appointment searches (the server says "date: must have a time"). Add T00:00:00Z (midnight, UTC) or the time you mean to each date.
An agent says the EHR does not offer hospital-wide encounter or appointment searches. The EHR searches one patient at a time. See Which healthcare agents work with your EHR for what works instead.
"... does not work with Oracle Health: ..." (making an agent from a template) That agent needs searches Oracle Health does not offer. Use the alternative the message names.
"... does not search ... by ...". Use a search parameter that describe_object lists. Oracle Health does not search encounters by class or conditions by code: leave them out and pick the rows by class.code or code.coding yourself.
"... is limiting how fast SourceLace may call it." Wait the time shown, or narrow the search.
"... took too long to answer this ... search (HTTP 504). Narrow it ..." The EHR gave up on a search that covers too much. Trying again gives the same answer, so narrow it: a shorter date range (about a week for appointments), or, for a patient's conditions, add clinical-status (such as active).
"... took too long to answer, so SourceLace stopped reading." Narrow the search, such as with a date range or a smaller count.
"The option vendor of ... must be one of ...." or "The option scope_version of ... must be v1, v2 or auto." The option holds a value SourceLace does not offer.
"... needs the option 'base_url': the FHIR R4 base URL, such as ...." or "... needs the option 'client_id': ..." The source is missing its address or the id of the app your EHR team registered.
"The ... of ... must be a plain https:// address, such as ..., with no user name, password, ?query or #fragment." The address has extras, or does not start with https://.
"... did not send its CapabilityStatement (.../metadata), so SourceLace cannot tell which resources it offers. Check base_url." or "... answered with something other than FHIR JSON (HTTP ...). Check base_url." The address is not the FHIR R4 base URL, or the server answered with a web page.
"SourceLace could not reach ... at .... Check base_url, and that the server can be reached from the internet." or "The address ... of ... could not be found." The address is misspelt, or the server is not reachable from the internet.
"... has no ... with id .... Ids come from a search's id column." No resource has that id, or the sign-in cannot see it.
"... had a problem of its own (HTTP ...). Try again in a minute." The EHR's FHIR service failed.
"... sent back data in an unexpected shape." or "... pointed its next page at another address, so SourceLace stopped reading." The EHR's answer was not in the form SourceLace expects. Rows read so far were not kept.