Practitioner Profile

Canonical	../StructureDefinition/nexus-emr-core-practitioner
Status	draft · 1.26.0
Base	Practitioner (constraint)
Source	FSH · JSON

Represents a human that practices medicine -- the stable clinical identity that an EMR user login resolves to. Practitioner holds identity, demographics, and qualifications, and carries the EMR user-account identifier. The person's role(s) at organizations/locations are represented by PractitionerRole (0..*), which is the tenant-scoped role binding -- NOT the EMR user. A person may work at multiple organizations, each represented by a PractitionerRole.

Access

What the endpoint offers

Declared for Practitioner by the capability statements this IG publishes. One row per statement; follow it for the rest of what that statement says about this type.

Capability statement	Interactions	Search parameters
Server Capability Statement	read vread history-instance search-type	none declared

A cell reading none declared means that statement declares none, which is not the same as the endpoint having none. See how to read a capability statement for what a declared interaction and a declared search parameter do -- and do not -- promise.

SMART on FHIR scopes

Practitioner is reachable by a SMART on FHIR app. These are the scopes an app can request, and the platform permission each one resolves to.

Request this scope	Grants	Permission required
user/Practitioner.rs	Read and search	practitioner:read

Practitioner is not in the FHIR patient compartment, so only the user context applies. A patient/Practitioner.rs scope has nothing to narrow to and is not grantable.

Narrowed exposure

Practitioner declares no write or delete permission, so an app cannot create or update or delete it however the scope is written.

Reading the suffix

A clinical scope is <context>/<ResourceType>.<interactions>.

• Context is patient (the launch patient's data only, and only for resource types in the FHIR patient compartment) or user (everything the authenticated user may see, valid for any type). There is no system context.
• Interactions are the letters c create, r read, u update, d delete, s search, written in cruds order. Order does not matter on the way in: Practitioner.sr and Practitioner.rs are the same scope.
• The older SMART v1 suffixes still work and fold on arrival: .read becomes .rs, .write becomes .cud, and .* becomes .cruds.
• Wildcards (patient/*.rs) expand over the SMART-exposed resource types only, never over everything this IG profiles.

Ask for a whole permission, or none of it

The platform has one read permission covering both r and s, and one write permission covering both c and u. A scope asking for half of either could only be granted by handing over more than it asked for, so it is refused rather than quietly widened: request Practitioner.rs, not Practitioner.r.

An unrecognised or ungrantable scope is rejected outright. It never silently resolves to an empty grant, which a caller could mistake for "no narrowing needed".