Zus

Owner: federico@pairteam.com

Intro

Zus Health is the platform utilized by Pair Team to access patient historical clinical data. Our current implementations are:

1. Elation - Zus integration
2. Patient Transitions of Care (TOC)

Elation - Zus integration

Care team members can access patients' clinical data directly in Elation, which includes:

• Encounters, along with related diagnoses
• Comprehensive clinical history

Patient Transitions of Care (TOC)

The primary resource we obtain from ZUS includes details on patient hospitalizations, related diagnoses, and identified care gaps. The key entry point for accessing this data is the Transitions of Care Lens API, which provides EpisodeOfCare FHIR resources that ZUS creates and manages.

We leverage these resources to effectively handle ARC hospitalizations.

• Hospitalizations consolidate multiple encounters.
• A received Zus::Event will create a workflow if:
  • The discharge type is either 'emergency' or 'inpatient'; all other types will be disregarded.
  • If the hospitalization is still active: The hospitalization admission within the last 30 days.
  • If the hospitalization is discharged: The hospitalization discharge within the last 30 days.
  • The patient is actively enrolled in ECM.
• When a Zus EpisodeOfCare is received:
  • If the discharge type is 'emergency' or 'inpatient', a Workflow will be created:
    • If the related hospitalization is still active (the patient is currently hospitalized), the created Workflow will be read-only, with no actions required.
    • If the related hospitalization has been discharged, the created Workflow will be active, allowing user interaction.
  • If a Workflow already exists, any updates must apply to that Workflow, including transitions from an admission Workflow to an active Workflow.
• Multiple admitted Workflows can be active simultaneously, but only one discharged (active) Workflow is permitted at any given time:
  • Upon patient discharge from a hospitalization, the corresponding Workflow must be converted to "active" meaning we have work to do on it.
  • If a new discharge is received for the same patient: the oldest discharged Workflow should be closed first. The form/SMS will be resent only if the previous form was completed and at least 5 days have passed since its completion.

Code References

• Entry point webhook
• Hospitalizations upsert
• Transitions of Care Lens API
• Zus Client

Resources

Tools

FHIR EMR	ZUS Admin App
https://fhirplace.zusapi.com/#/Patient	https://app.zushealth.com/admin