We are excited to introduce the "Intelligent Refresh" feature for patients in a ZAP Lite or ZAP Pro subscription package. Now, we will automatically search for and update clinical documents within a patient's ZAP after two key clinical events. (click for more!)

Appointment Preparation: Just before the start of any of your upcoming appointments written to Zus, we will initiate a refresh to ensure your clinical history is up-to-date, giving you a complete picture of your patient's health.

Post-Discharge Follow-up: After receiving an ADT discharge, we will refresh EHR documents to capture follow-up documentation from recent hospital stays.

We hope this update will enhance the accuracy and completeness of your patient records, empowering you with better insights for delivering quality care.

The Diagnostic component now indicates which diagnostic reports have historical lab trend data. Trending is now available for lipid panel results (HDL, LDL, total cholesterol, and triglycerides) and is also now available to all Builders.

Care team users can now view lab trends for hemoglobin a1c and glucose for patients with these data available in the Diagnostics component. We are planning to make trends available for additional labs (e.g., cholesterol, triglycerides, GFR) in the near future. This trending feature is currently only available to Builders on an opt-in basis. If you would like the ability to view lab trends, please reach out to our Support team.

Diagnostic reports (i.e., labs, imaging, clinical studies, etc.) can now be viewed in a separate Diagnostics component. The new Diagnostics component allows you to "dismiss" diagnostic reports to hide them from your view and visually distinguishes between viewed vs. not viewed diagnostic reports. The Timeline component still retains diagnostic reports in addition to encounters if you prefer to look at both encounters and diagnostic reports in the same timeline view.

The Medications List and Outside Medications components have now been merged into a single Medications List component in the standalone Zus App. This component contains medications from external providers in addition to medications you have added to your own record. The new component visually distinguishes between your records vs. external medications, as well as viewed vs. not viewed medications.

Zus embeddable components are now powered by the Zus FHIR GraphQL Service, significantly improving page load times and solving several issues which caused data to fail to be surfaced across components.

The Conditions List and Outside Conditions components have now been merged into a single Conditions List component in the standalone Zus App. This component contains conditions from external providers in addition to conditions you have added to your own record. The new component also visually distinguishes between internal vs. external data, as well as viewed vs. not viewed conditions.

The Documents component now includes encounter dates associated with documents (where applicable) and incorporates encounter dates in the Documents list deduplication logic. Clinicians can now prioritize and sort documents to review based on encounter date and there will be more documents available to review as a result of the improvement to the deduplication logic.

The Medications component's Outside Medications tab now shows all summarized medications from outside sources, not just those which Zus determines are active. The Outside Medications tab now also shows medications without medication activity dates to provide a more comprehensive view to clinicians performing medication reconciliation.

We are excited to announce our new /patient-history/jobs API, which comes with improved functionality to schedule a Patient History job and other enhanced features.

🚧

On August 8th, the following endpoints will be deprecated:

• Start a job - /patient-history/patient/{patient-id}/refresh
• Check the status of a job - /patient-history/message-status/{message-id}
• Get job messages - /patient-history/messages

To ensure a smooth transition and minimize any disruptions to your projects, we have prepared this guide to help you convert your existing requests to the new API.

Create a patient history job

Whereas the /refresh endpoint does not have a request body, the new /jobs endpoint does.

{  
    "data": {  
        "type": "patient-history/jobs",  
        "attributes": {  
            "requestConsent": true,  
            "practitioner": {  
                "npi": "1013085661",  
                "name": "Testfirstname Testlastname",  
                "role": "309343006"  
            }  
        },
       "targetDate": "2023-09-01",
        "relationships": {  
            "patient": {  
                "data": {  
                    "type": "fhir/Patient",  
                    "id": "{patient-id}"  
                }  
            }  
        }  
    }  
}

Check the status of a patient history job

Please see below for the differences in the response bodies.

{  
    "data": {  
        "id": "{job-id}",  
        "type": "create_patient_history_job",  
        "attributes": {  
            "message_status": "done",  
            "messages": [  
                {  
                    "services": "commonwell",  
                    "status": "done"  
                },  
                {  
                    "services": "surescripts",  
                    "status": "done"  
                }  
            ]  
        }  
    }  
}

{  
    "data": [  
        {  
            "type": "patient-history/jobs",  
            "id": "{job-id}",  
            "attributes": {  
                "createdAt": 1681406975,  
                "jobStatus": "in_progress",  
                "lastUpdatedAt": 1687809292,  
                "practitioner": {  
                    "npi": "1013085661",  
                    "name": "Testfirstname Testlastname",  
                    "role": "309343006"
                },  
                "providers": [  
                    {  
                        "service": "commonwell",  
                        "status": "done"  
                    },  
                    {  
                        "service": "surescripts",  
                        "status": "done"  
                    }  
                ]
            },  
            "relationships": {  
                "patient": {  
                    "data": {  
                        "type": "fhir/Patient",  
                        "id": "{patient-id}"  
                    }  
                }  
            }  
        }  
    ],  
    "links": {  
        "self": "<https://api.zusapi.com/patient-history/jobs?page[count]=50&page[offset]=0>"  
    },  
    "meta": {  
        "totalResultCount": 1  
    }  
}

Get jobs