Cohorts allow you to configure shared patient settings.
For example, you could create one cohort to monitor a group of
chronically-ill individuals with all features enabled (e.g., ADTs, pharmacies, laboratory, HIE), and another cohort
that monitors a less critical group of individuals with just HIE data enabled.
If you’d like us to create a cohort that includes ADT, pharmacy, or laboratory monitoring,
please note these are premium features and require those services to be activated
on your account. Let us know if you’d like to add them.
Getting Started
Every cohort has a unique name and a collection of settings which apply to all patients within that cohort.
These settings control what data sources are monitored, how frequently queries are run, and what notifications are sent.A patient can be in multiple cohorts, which allows for flexible monitoring configurations.
If any cohort enables a particular monitoring feature, that feature will be active for the patient.
In Metriport, a cohort is simply a label that can be given to any number of patients. You can
use that label to apply common settings across a group of patients,
or retrieve the members of that cohort via API.
{ "name": "High Risk", "description": "Members of this cohort are opted-in to all available data sources.", "color": "red", "settings": { "monitoring": { "adt": { "enabled": true }, "hie": { "enabled": true, "frequency": "weekly" }, "pharmacy": { "notifications": true, "schedule": { "enabled": false, "frequency": "monthly" } }, "laboratory": { "notifications": true } } }}
See Here for a detailed explanation of the available settings.
Monitoring Patients with Cohorts
Metriport allows you to monitor patients and receive notifications about them over time.To do this, ask us to create a cohort for you and specify the settings you wish to have. Then add patients that need to be monitored to the cohort.
The settings of the cohort are now applied to the patient (what monitoring is set, schedule, etc.).
// 1. Get the cohort created by Metriportconst cohortId = "00000000-0000-0000-0000-000000000000";// 2. Add patients to the cohortconst patientsInCohort = await metriportApi.addPatientsToCohort({ cohortId, patientIds: [ "11111111-1111-1111-1111-111111111111", "22222222-2222-2222-2222-222222222222", ]});
Setting a patient’s cohorts as you create them is the
easiest way + recommended way of enabling monitoring.
Alternatively, just create your patients as usual (via API call or bulk patient create) and specify the desired cohorts.
// Create a patient and assign to existing cohortsconst patient = await metriportApi.createPatient( { firstName: "John", lastName: "Doe", dob: "1990-01-01", genderAtBirth: "M", address: [ { addressLine1: "123 Main St", city: "Anytown", state: "CA", zip: "12345", country: "USA", }, ], // Assign cohorts during creation cohorts: [ "00000000-0000-0000-0000-000000000000", "11111111-1111-1111-1111-111111111111" ], }, facilityId);// The patient is now automatically subscribed to the monitoring settings of the 2 cohorts
Adding Patients to Cohorts
Patients can be added to cohorts on creation, or added to and removed from different cohorts as needed.During creation:
In Bulk Patient Create
there is a cohort-N column header for specifying the starting cohorts for a patient. See here.
In Create Patient
there is a cohorts array parameter to set any number of cohorts on a patient. See here.
Treatment cohorts require patients to have treatment relationship consent (treatmentRelationship: true). Patients without consent cannot be assigned to treatment cohorts, and revoking consent automatically removes the patient from all treatment cohorts.Update a patient’s consent programmatically via the Treatment Relationship API reference.
Available Settings
Use settings to enable monitoring for certain data sources.To configure cohort settings, please contact us.
object
Hide monitoring object properties
object
HIE-based document monitoring - subscribes patients to HIE-based
document monitoring (non-ADT) / medical record refresh based on the cadence.
Show hie object properties
boolean
Enable or disable scheduled data pulls for HIE monitoring. Defaults to disabled.
When disabled, no scheduled pulls will occur regardless of the frequency setting.
string
How often scheduled data pulls should occur, can be one of daily, weekly, biweekly or monthly. Defaults to monthly.
ADT (Admission, Discharge, Transfer) monitoring - subscribes patients to ADT notifications
based on their primary address.
Show adt object properties
boolean
Enable or disable ADT monitoring notifications. Defaults to disabled.
object
Pharmacy / medication history monitoring - enables retail fill data monitoring where available.
Show pharmacy object properties
boolean
Enable/disable pharmacy monitoring notifications. Defaults to disabled.
Pharmacy notifications are coming soon! While this feature is not yet live, you can configure
your Pharmacy notification settings now. These settings will automatically take effect when the feature launches.
object
Enable pharmacy data pulls at scheduled dates.
Show schedule object properties
boolean
Enable or disable scheduled data pulls for pharmacy monitoring. When disabled, no
scheduled pulls will occur regardless of the frequency setting. Defaults to disabled.
string
How often scheduled data pulls should occur, can be one of weekly, biweekly or monthly. Defaults to monthly.