Atlas

Learn how Atlas finds the fields a workflow needs in a patient's Zus record and returns each with a citation.

Atlas gives your application the specific facts a workflow needs from a patient's Zus record, each with a citation to its source. You define what to look for, and your team or your systems decide what to do with the results. That lets you build program eligibility, intake or referral workflows, or other clinical workflows without building the record search and extraction behind them.

How it works

  1. The record. Atlas works from the patient's ZAP: clinical, pharmacy, lab and ADT data from the sources Zus connects to, plus data your organization sends.
  2. Fields. You define the fields a workflow needs and the criteria for each one, usually starting from a form or checklist you already use.
  3. Input data. You can also send input data with a request, such as dates or diagnosis details you already have about the patient, to help Atlas return better results.
  4. The search. Atlas looks for evidence for every field across the record and any input data you sent.
  5. Cited results. Each field comes back as structured data: its value and a citation to the source, such as a referral letter, a lab result or a pharmacy fill. If Atlas can't find a field, the result says so.

Atlas reports what it finds, gaps included. It doesn't make clinical judgments; those stay with your team.

Building on Atlas

One Atlas setup serves many workflows. Adding a workflow means adding a configuration, not a new build or integration. Clients use Atlas configurations for:

  • Evidence for prior authorization
  • Patient intake and registration
  • Inbound referral workup
  • Form auto-fill and validation
  • Care gap data for quality programs
  • Pre-diagnostic clearance
  • Program eligibility

Zus scopes each configuration with you, starting from the decision you need evidence for and the form or criteria you already use.

Getting results

Your application requests Atlas results and retrieves them through an API, then uses them wherever your workflow needs them. Your account team sets up access when you scope a configuration.

Related pages


Did this page help you?