ZAP Data and Access

The Zus Aggregated Profile (ZAP) is a single view of a patient's clinical data: what your organization contributes, plus records from health data networks and other organizations on Zus. It can also include Lens summaries built from that data.

What's in a patient's ZAP

• First-party data is what your organization contributes, through the Zus APIs, an EHR integration or the Zus App.
• Third-party data comes from outside your organization: health data networks and other organizations on Zus.

Ways to access the ZAP

Each user and App Client also needs a role that allows the access method they use.

What your organization can see

A matching Universal Patient Identifier (UPID) doesn't by itself give you the full ZAP. What you can see depends on your relationship with the patient, access rules, and data restrictions.

• First-party data is always available to you.
• Third-party data requires an active relationship with the patient, which you assert with the FHIR Patient.active field. See Patient Relationships and Data Access for how to set it and how long access lasts after unenrollment.

For what other organizations can see of the data you contribute, see Common Patient Record within Zus.

Related pages

• Patient Relationships and Data Access
• Universal Patient Identifier (UPID)
• Common Patient Record within Zus
• Embedding the ZAP