Adding Your Data

Put Zus to work on your data

The Zus platform is far more powerful when you combine your own data about your patients with data obtained from our data services. Here are just a few of the benefits of having an integrated view of your patients and populations on Zus:

  • Intelligent refresh: Zus takes on the work of ensuring you always have the latest external data about your patient. Load your appointments so we can refresh the ZAP in advance. Load your referrals or orders so we can proactively close the loop.
  • Unified clinician views: Zus front-end capabilities apply the our cleansing and summarization magic to your data. Give your clinicians an integrated view of key summarized data points (conditions, etc.) and a complete trend for lab results.
  • Clean, analytics-ready data: Focus your analytics team on insights, not cleansing. Zus will incorporate your data into insight-ready Data Marts.
  • Deliver coordinated care: Zus makes clinical data available to other treating providers on the Zus, Commonwell, and Carequality networks. Ensure your patients get quality care by providing visibility to the rest of their team (and adhering to interoperability requirements and quality standards while you’re at it).
  • What to contribute
    You may contribute any data that your clinical team documents about your patients, as well as any data from payers or employers that you have rights to share with other treating providers. Zus will only share data that is part of our defined designated record set [LINK].

For patients you have already seen, we recommend incorporating information captured from your care interactions. This might include encounter information, clinical notes, diagnoses, lab results and orders, prescriptions, referrals, care plans, and upcoming appointments.

For patients you have not yet seen, consider data points regarding upcoming appointments, patient insurance coverage, or any known medical history.

Zus makes it easy

We offer several easy ways to integrate your data onto Zus.

  • EHR integrations: If you are using one of our EHR partners, key data elements will automatically sync to Zus, no effort required! Your EHR not on Zus yet - let us know!
  • APIs: Leverage our robust FHIR APIs to write individual data points to the platform. Soon, you’ll also be able to use our C-CDA parser API to pass a C-CDA to Zus (and let us do the hard work of turning it into FHIR).
  • CSV import: If bulk data is easier for your organization, please contact your customer success team and we may be able to help you with import.
  • Snowflake sync: We are piloting a direct import from customer Snowflake instances. If this is interesting to your organization, please contact your customer success team.

With all of these, make sure data is associated with your organization’s version of the patient and not the UPID. When you create this data, an Access Control Tag indicates that your Builder is the resource's owner.

Access Control Tag example:

"meta": {
    "tag": [
            "system": "",
            "code": "builder/<BuilderID>",
            "display": "Builder Name"

Access Control Tag Permissions

Only Zus has the ability to create, modify, or delete Access Control Tags.

If a user attempts to create, modify, or delete an Access Control Tag in the process of creating or modifying a resource, the creation or modification operation on the resource will proceed, but any Access Control Tag changes will not be recognized by Zus (i.e., an error response will not be returned).

Users can only read tags for resources they have permission to see.

Data network best practices

The clinical data that Zus provides operates on the principles of a healthcare information exchange that relies on participants to contribute data in addition to querying for it. While there is no hard and fast rule for “reciprocity”, there are a few guiding principles here. Zus (and our network partners) monitor customer adherence to these best practices and may reach out to your team to discuss improvement opportunities.

  • Timeliness: Best practice is to contribute data in advance of querying whenever possible. In cases where patients have not yet been seen, organizations may contribute minimal data (e.g. upcoming appointment) in advance and follow up with richer clinical data within 30 days of the appointment.
  • Frequency: Your users and the network want fresh data! Best practice is to continuously incorporate new and updated data into the ZAP.
  • Comprehensiveness: The usefulness and impact of clinical data is dependent on how rich and comprehensive it is. If you and your team are power users of the ZAP, please consider contributing data in the same spirit of comprehensiveness (it’ll make your experience better too!).
  • Uniqueness: At Zus, we’re pro’s at handing duplicates, but can’t say we love ‘em. Whenever possible, contribute data that is unique about the patient - not what is already reflected in the ZAP.
  • Provenance: When, where, and who documented data matters.