Integrations
Partners
DisEASE runs stand-alone in any browser, with no integration work at all. Where an organization wants it inside the chart, it is registered as a provider-facing SMART on FHIR app for Epic.
Stand-alone
The path that needs nothing from your IT team.
A clinician signs in, completes the workup and gets a ranked recommendation with its trace. No integration, no interface engine, no project. This is how most clinicians use DisEASE today and it is the fastest way to evaluate whether the engine earns a place in your workflow.
Epic on FHIR
Launched from the patient chart, with the workup pre-filled from chart data.
A clinician opens a chart in Epic and launches DisEASE. The app retrieves the fields the rules need, pre-fills the workup, and returns a ranked recommendation the clinician acts on inside their normal Epic workflow. The integration is read-only: DisEASE never writes to the EHR, and it registers no outgoing APIs, so Epic never initiates a call to our infrastructure. Chart data is used for the duration of the session and is not retained afterward.
| Epic API | What it is for |
|---|---|
| Patient.Read (Demographics) | Age and sex as rule inputs. |
| Condition.Search (Problems) | Problem list, for module selection and comorbidity rules. |
| Observation.Search (Vital Signs) | Blood pressure, heart rate, weight. |
| Observation.Search (Labs) | A1c, renal function, electrolytes. |
| MedicationRequest.Search | Active medications, for interaction and optimization rules. |
| Medication.Read | Resolves an order to a drug identity for rule matching. |
| AllergyIntolerance.Search | Documented allergies and intolerances. |
The integration deliberately excludes chart data it does not need: no clinical notes or documents, and no insurance or coverage information.
Epic is a trademark of Epic Systems Corporation. DisEASE is an independent product of DisEASE LLC and is not endorsed, certified, or sponsored by Epic.
Other systems
An honest answer rather than a roadmap.
Epic is the only EHR DisEASE integrates with today. The integration is built on FHIR R4 because that is the version certified EHRs are required to serve, which means the same shape of integration is available in principle elsewhere. We are not naming other vendors or dates until one is actually built. If your system matters to you, tell us and it will inform what we build next.
Start a conversation
Integration questions, or an EHR you want us to support.