Security, interoperability, and clinical workflow, for teams taking the waiting-on list out of memory.
It lives in their head or on paper. We asked more than 30 clinicians how they track what they're waiting on, and not one physician named the EHR.
Semblance holds that list for the whole team, with four facts for every item: what is pending, who has it, how old it is, and whether it moved.
Semblance is built for HIPAA-regulated environments. These are the questions a compliance review asks first.
Semblance is built for HIPAA-regulated environments, with HIPAA-ready architecture and safeguards. Data is encrypted end to end, in transit and at rest.
Access is role-based, and activity is kept in an audit trail on a FHIR R4 data model.
Yes. A BAA is available on request. Semblance is built on Google Cloud infrastructure that is covered under a BAA.
Not yet. Our controls are aligned to SOC 2 and we are in controls readiness. A formal SOC 2 Type II audit is on our roadmap.
A Type II report covers how controls operate over a period of time, so readiness comes first. Until the report exists, we share our security overview for your review.
No. Clinical data is never used to train models.
Yes. Access is role-based and activity is recorded in an audit trail on a FHIR R4 data model.
Every commitment also exports as FHIR Provenance and AuditEvent records, so its history can sit with your EHR's own record.
Start with the security overview and the BAA. Both are available on request from our team.
Semblance reads from the systems you already use and hands closure back in standard FHIR. No rip and replace.
No. Semblance works alongside the systems you already use. Your EHR keeps doing its job.
Semblance adds what it doesn't track: one accepted owner, a due time, live status, escalation, and evidence that the work closed.
SMART on FHIR is an open HL7 standard for connecting an app to an EHR. The app reads data through the EHR's FHIR API, and access is authorized through OAuth 2.0 with scopes your organization approves.
To read orders, results, and schedules. That context ties each commitment to the patient, keeps ownership visible over time, and shows when work moves, such as a result landing.
Every commitment exports as a FHIR Task, Provenance, and AuditEvent, so closure is anchored to your EHR's own record.
In FHIR R4, a Task tracks an activity and its status, Provenance records who and what produced a record, and an AuditEvent logs the events around it.
Source: HL7 FHIR R4 resource list
Semblance is designed to work with your existing tools, including Epic, Cerner, MEDITECH Expanse, OpenMRS, and Amion for scheduling. Tell us what you run and we'll confirm how Semblance fits it.
FHIR R4. The audit trail and the exported Task, Provenance, and AuditEvent records use the R4 data model.
That is where follow-up goes quiet. Epic tracks what Epic ordered. It doesn't track what you're waiting on from a contracted group, an outside facility, or an insurer.
Semblance watches for signals that already exist, like a result landing, a note appearing, or a call coming back. It asks nothing new of the other side.
State a request once. Semblance turns it into one accepted commitment and keeps it visible until there is evidence it closed.
A clinician speaks, types, or forwards the request once. Semblance structures it into patient, action, and urgency, and the clinician confirms it before it routes.
The right owner accepts it. From there, Semblance tracks status and blockers until closure.
Each confirmed commitment is held on a FHIR R4 data model and exports as a FHIR Task with its owner and status, plus Provenance and AuditEvent records.
The record then shows what was asked, who owned it, and how it closed.
The clinician. Semblance structures what was said, and the clinician confirms the patient, action, and urgency before anything routes. Ownership is accepted by a person, never assumed.
No. Semblance is not a scribe, not another inbox, and not a task manager. It holds what was asked for, with one owner and evidence of closure.
Accept, decline, and delegate are built in. Each commitment carries one accepted owner, so it is clear who has it instead of two teams each assuming the other does.
Semblance tracks status and blockers on every commitment and escalates by your team's rules. A patient's related commitments are grouped into one workflow, so the full picture for that patient sits in one place.
A commitment closes only when the completing evidence exists, such as a result reviewed, a callback documented, or an order signed. A ticked checkbox isn't enough.
Physicians who carry the waiting-on list in their head, and the nurses, APPs, case managers, MAs, and front-desk staff who finish the work with them. It adds no new heavyweight workflow.
From the BAA to how Semblance connects to your EHR, we'll walk your IT and clinical leads through it.
