EHR › Interoperability
Patient Groups
Groups of patients a back-end service may export together (FHIR Bulk Data Group/$export): a payer's members, an ACO's attributed patients, a registry.
Where to find it
- Module: EHR
- Group: Information & Population
- Section: Interoperability
- Screen: Patient Groups
Address in the console: /ehr/patient-groups
List · 5 columns · 5 fields on its form · 2 of them required · 2 actions
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| Code | Code | code |
| Group | Text | name |
| Purpose | Status | purpose |
| Patients | Number | members |
| Active | Yes or no | is_active |
The form
What is asked for when a record is created here. Required fields are marked; a choice drawn from a configuration list is one an administrator can extend without a release.
| Field | Type | Choices | Notes |
|---|---|---|---|
| Code required | Text | ||
| Name required | Text | ||
| Description | Long text | ||
| Purpose | Choice | export, registry, aco, payer, research | |
| Active | Yes or no |
What you can do here
Members
Add patient
Asks for: Patient*
* required
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.
- Creating a record — required fields, where choices come from, and how the number is allocated.
- Importing a spreadsheet — this screen accepts one, and it runs through the same rules as typing.