Organization Profile¶
| Canonical | ../StructureDefinition/nexus-emr-core-organization |
|---|---|
| Status | draft · 1.26.0 |
| Base | Organization (constraint) |
| Source | FSH · JSON |
Generic Nexus EMR core profile for Organization, based on CA Core+. Designed to support a broad range of integration needs.
Overview
Overview
The Nexus EMR Core Organization profile represents primary care organizations that own and control EMR instances within the Nexus EMR ecosystem. This profile captures essential information about primary care entities such as family medicine clinics, primary care networks, and group practices that operate EMR systems.
Purpose and Scope
The Organization resource in Nexus EMR specifically represents:
- Primary care clinics and practices
- Family medicine groups
- Primary care networks
- Group practices operating EMR systems
Each Organization resource identifies the administrative entity responsible for a primary care EMR instance and its data governance.
Key Features
EMR Ownership
The Organization profile identifies the entity that owns and operates a primary care EMR instance. This relationship establishes:
- Data governance and ownership
- Administrative responsibilities
- System access control
- Compliance oversight
Identifier Requirements
Identifier is optional (0..*). A Nexus EMR canonical identifier is recommended (not required):
- When present, it should use a Nexus EMR canonical system URI
- Format:
../NamingSystem/organization-identifier, with the installation's own stable slug as thevalue. The system carries no instance segment: it is thevaluethat distinguishes one installation from another, and it must be unique across all of them. - A source/raw identifier SHOULD be carried where the record was converted from another system.
Recommended, and as of 1.21.0 not checked: the
organization-has-raw-identifierwarning that used to nudge for it was removed along with its 33 siblings - Supports consistent organization tracking across systems
Active Status
The active element is optional:
- When absent, the organization is assumed to be active
- Only set to
falsewhen explicitly deactivated - Supports soft-delete patterns for maintaining historical records
Relationships to Other Resources
Device
Device.owner references the Organization, establishing the EMR ownership relationship and defining administrative boundaries for the EMR instance.
PractitionerRole
Links practitioners to their practice organization, defining scope of practice and establishing practice affiliations.
Location
Physical sites managed by the organization, supporting multiple service delivery locations per organization.
Validation
Identity rests on the FHIR logical id plus any business identifiers present. There is no hard
has-nexus-emr-id requirement, and as of 1.21.0 no invariant on this profile checks identifiers at
all -- the warning-severity organization-has-raw-identifier was removed. Carrying at least one
source/raw identifier that is not the Nexus EMR canonical one is still the right thing to do where
the resource was converted from a source EMR, but a validation run will no longer say so.