Integration
How Patient 3-D connects to your EHR
Runs inside your EHR. Your clinicians sign every order. No data leaves your environment.
How the engine reads the record, where clinicians see its findings, how their actions return to the chart, and who does what. Epic is shown; the same standards apply to other certified EHRs.
Runs inside your environment.
The record, the engine and the integration layer are deployed in your infrastructure. No protected health information leaves it.
Uses your EHR's own standards.
The industry-standard connections your EHR vendor already publishes and certifies. No custom changes inside the EHR itself.
Clinicians sign every order.
Patient 3-D ranks, explains and suggests. Nothing is ordered until a clinician signs it in the EHR.
What your clinicians see.
Events in
A current list. An admission, discharge or new result reaches the engine within minutes, so the ranking they open reflects today.
Claims
The whole picture. Cost and use of care from your payers sit beside the clinical record, so a patient's rank reflects both.
The full record
Every patient ranked. The whole population is scored, not only the patient on screen, so no one is missed between visits.
The Patient 3-D tab
The ranked queue in the chart: the interaction named, the protocol, the assignment.
Alert at chart open or ordering
A card at the moment it matters, such as kidney function, heart failure and an NSAID on the outside medication list.
Suggested order
A referral or dose change, prepared and waiting in the order list for the clinician to sign.
Note and "done" back to the chart
A short note in the chart: what was flagged, who acted, when.
If Patient 3-D is unavailable, nothing in the EHR breaks. The tab shows unavailable, the alerts don't fire, and every workflow runs as it does today. Orders exist only once a clinician signs them.
Who does what.
Your organization
Owns the infrastructure, the access controls and the source systems. Activates the app and the alerts in the EHR, chooses which alerts fire, and runs its own security review and change control.
Hypersphere Health
Builds and supports the Patient 3-D engine, the in-chart app and the alert service; registers the app with the EHR vendor; owns clinical content and its citations.
Rhapsody
Every connection in and out: events, the full record, claims, matching each patient across systems, standard medical vocabularies, secure access for applications, and write-back to the chart.
InterSystems
The patient record the engine reads, kept in a standard format inside your environment and secured there.
ELEKS
Build, hosting operations, help desk and IT service management for the deployed stack.
The EHR vendor
Publishes the standards and the test environment. Each health system activates third-party clinician apps on its own instance.
How an engagement runs.
Approving the proof of value commits you to nothing in production. Production is described so its feasibility is not an open question.
1 · Proof of value
- One extract under a data use agreement, delivered once.
- Analyzed in an isolated U.S. environment, with no connection to your systems.
- Your clinicians review a sample of the results.
- The environment is destroyed and the destruction certified in writing.
2 · Production, two tracks in parallel
- Data pipes: Rhapsody and InterSystems stood up in your infrastructure; events, record and claims flowing.
- In-chart surfaces: the app validated in your EHR's test environment, then your security review, activation and configuration.
- Go-live under your change control, starting with one clinic or service line.
See it on your data.
A proof of value first: one extract under a data use agreement, your clinicians at the review table, results in weeks.