How Data is Shared

Zus is a shared health data platform. Therefore, patient data you store on the Zus platform will be available to other healthcare organizations in two ways:

  1. On the Zus platform, with other organizations that have asserted a TPO relationship with this patient using the FHIR field
  2. As part of requests from networks such as CommonWell and Carequality, so long as the requesting party from those networks has a relationship with the patient for TPO purposes, unless that data is flagged as “restricted” (more details below).

In both scenarios, Zus only shares data that is part of the Designated Record Set and excludes any data that is Restricted. Additionally, the other organization must also provide enough demographic information on a patient to match them in our Universal Patient Index.

Designated Record Set

Zus has also defined a minimum set of resource types for patients as a “Designated Record Set” that your users and app clients can access from other Builders on Zus that have relationships with your patients, without explicit patient consent. This Designated Record Set aligns with the requirements of the 21st Century Cures Act, ONC Information Blocking rules, and HIPAA. See below for the full list of resource types included in the Designated Record Set.

Resource Types in the Designated Record Set:

ℹ️ Today, Zus shares binaries as part of the designated record set to support access to content such as CCDAs and raw ADT messages. If you intend to write binaries to Zus and would like to withhold them from the DRS, please reach out to your Customer Success contact.

Zus also provides access to a small set of foundational resources (see below) owned by other Builders if they are referenced by Designated Record Set resources. For example, a care team user viewing a patient’s ZAP may want to know who ordered a MedicationRequest from another Builder. The MedicationRequest resource contains a reference to a Practitioner resource in the other Builder. Thus, the care team user can see the Practitioner referenced by the MedicationRequest. However, the user cannot query directly for the Practitioner resource. The Practitioner resource is only accessible as part of a query for the MedicationRequest resource.

Foundational Resources Referenced by Designated Record Set Resources:

  • Location
  • Medication
  • Organization
  • Practitioner
  • PractitionerRole
  • Provenance


Inactive Patients Included in the ZAP

Other Builders on Zus can view Designated Record Set data for your inactive patients via the ZAP if these Builders have a relationship with the patients.

Responses to EHR Networks

Today, when Zus received an inbound data request from CommonWell or Carequality for a patient, we respond with a Continuity of Care Document (CCD) that incorporates the following resource types:

  • AllergyIntolerance
  • Appointment
  • Care Plan
  • Care Team
  • Condition
  • Coverage
  • DiagnosticReport
  • DocumentReference
    • Note: Zus will only incorporate Document References that contain clinical notes in the context of an encounter. If you are syncing clinical notes to Zus, please make sure they meet the following requirements:
      • DocumentReference.category must have a value of clinical-note(as defined here; example)
      • The note content must be inDocumentReference.content.attachment as Base64-encoded text
      • DocumentReference.context must contain a reference to a single Encounter resource.
  • Encounter
  • Immunization
  • MedicationDispense
  • MedicationStatement
  • Observation
  • Procedure