Introduction

Background

Verto's Digital Twin ingests data from primary care EMRs and standardizes / codifies it to create a structured, machine readable copy for downstream analysis and automation. The goal of the Cohort Search API is to make this structured and augmented dataset available to be used for downstream clinical actions or applications.

Objects in Verto's Analytical Data Layer

Within the Cohort Search API, there exist three main objects through which the API can be queried:

• Patient: Contains summary information about the patient, including their Date of Birth, Gender, and any other demographic information that eCE's bots require
• Concept: A named and coded entity from the UMLS metathesaurus. The concept object is used to associate clinical entities to the patient, and provide additional detail about those clinical entities found in the patient record such as their clinical status or verification status. It also provides information related to the UMLS metathesaurus to further categorize and link entities, enhancing the information available.
• Event: An event corresponds to a single mention of a concept within the patient record, and includes information such as the timestamp at which the data was entered and the provider who entered that data (if available). Think of events as transactional elements, with a new event created each time an entity is mentioned in the EMR. Multiple events may roll up to the same concept, and events may be duplicated within a patient record as they represent individual mentions of a clinical entity.

The patient cohort API does not surface these objects individually, but instead amalgamates them according to a set of filters specified in the body of the request. The resulting response from the API will include the relevant patient information, as well as a list of concepts related to the filters specified for each patient. While the concepts listed represent a deduplicated set of events for that patient, the timestamp on each concept represents the most recent event corresponding to that concept, which can be used in tandem with other information to assess its relevance.

More information regarding the API response can be found on the "API Requests" page.