Skip to content

Other EHRs

These EHRs do not yet have enough material for a page of their own. Contributions are welcome.

  • Separate staging and production hosts, plus a public endpoint directory.
  • The only vendor we have seen that needs client_id and client_secret as POST parameters in addition to the signed JWT assertion.
  • Keycloak token endpoint; the token URL is also the JWT aud.
  • ES384 is required; RS384 is rejected.
  • The base URL ends in /V1 or /V3 depending on the EHR version the practice runs.

The mirror image of Nextech: one client id for every practice, with a per-practice workspace base URL.

Per-patient Observation and Encounter searches from a patient list have worked for diabetes (A1c) and blood pressure measures.

Partner API authenticated with an API-key header; no OAuth.

Delivered as a ZIP of per-patient Bundles:

  • Encounter.status is absent or unknown — treat completed visits as finished.
  • The NPI is carried under the NPI OID rather than the us-npi system; rewrite it.

No FHIR extraction notes yet — data has come through lab files instead.