US Core Implementation Guide (Release 1.1.0 Ballot )

This page is part of the US Core (v1.1.0: STU2 Ballot 1) based on FHIR R3. The current version which supercedes this version is 5.0.1. For a full list of available versions, see the Directory of published versions

SD.20 StructureDefinition-us-core-practitionerrole

Scope and Usage

This profile sets minimum expectations for the PractitionerRole resource to record, search and fetch the practitioner role for a practitioner. It identifies the mandatory core elements, extensions, vocabularies and value sets which SHALL be present in the PractitionerRole resource when using this profile. The requirements for the US Core Practitioner were drawn from the Argonaut Provider Directory, IHE Healthcare Provider Directory and the ONC Provider Directory Workshop.

Mandatory Data Elements and Terminology

The following data-elements are mandatory (i.e data MUST be present). These are presented below in a simple human-readable explanation. Profile specific guidance and examples are provided as well. The Formal Profile Definition below provides the formal summary, definitions, and terminology requirements.

Each PractitionerRole must have:

  1. An associated practitioner
  2. An associated organization
  3. A list of roles
  4. A list of specialities
  5. An associated location
  6. Contact information

Profile specific implementation guidance:

  • The Practitioner resource SHALL be included when returning the PractitionerRole resource.
  • The Endpoint resource SHALL be included when returning the PractitionerRole resource.
  • The PractitionerRole.endpoint is where the Direct address is included.
Examples

SD.20.1 Formal Views of Profile Content

Description of Profiles, Differentials, and Snapshots.

The official URL for this profile is: http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole

Published on Sun Dec 10 00:00:00 AEDT 2017 as a draft by HL7 US Realm Steering Committee.

This profile builds on PractitionerRole

Summary of the Mandatory Requirements

  1. One practitioner in PractitionerRole.practitioner
  2. One organization in PractitionerRole.organization
  3. One practitioner role code in PractitionerRole.code which has an extensible binding to:
  4. One practitioner specialty code in PractitionerRole.specialty which has an extensible binding to:
  5. One reference to a location in PractitionerRole.location
  6. At least one contact using either ‘PractitionerRole.telecom’ OR or reference to an Endpoint Resource in PractitionerRole.endpoint
NameFlagsCard.TypeDescription & Constraintsdoco
.. PractitionerRole I0..*US Core PractitionerRole Profile
pd-1: SHALL have contact information or a reference to an Endpoint
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: Common Languages (extensible)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional Content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierBusiness Identifiers that are specific to a role/location
... active Σ0..1booleanWhether this practitioner's record is in active use
... period Σ0..1PeriodThe period during which the practitioner is authorized to perform in these role(s)
... practitioner SΣ1..1Reference(US Core Practitioner Profile)Practitioner that is able to provide the defined services for the organation
... organization SΣ1..1Reference(US Core Organization Profile)Organization where the roles are available
... code SΣ1..1CodeableConceptRoles which this practitioner may perform
Binding: Argonaut Provider Directory Provider Role (NUCC) (required)
... specialty SΣ1..1CodeableConceptSpecific specialty of the practitioner
Binding: Argonaut Provider Directory Provider Speciality (NUCC) (required)
... location SΣ0..*Reference(US Core Location Profile)The location(s) at which this practitioner provides care
... healthcareService 0..*Reference(HealthcareService)The list of healthcare services that this worker provides for this role's Organization/Location(s)
... telecom SΣ0..*ContactPointContact details that are specific to the role/location/service
.... id 0..1stringxml:id (or equivalent in JSON)
.... system SΣI1..1codephone | fax | email | pager | url | sms | other
Binding: ContactPointSystem (required)
.... value SΣ1..1stringThe actual contact point details
.... use ?!Σ0..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required)
.... rank Σ0..1positiveIntSpecify preferred order of use (1 = highest)
.... period Σ0..1PeriodTime period when the contact point was/is in use
... availableTime I0..*BackboneElementTimes the Service Site is available
.... id 0..1stringxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... daysOfWeek 0..*codemon | tue | wed | thu | fri | sat | sun
Binding: DaysOfWeek (required)
.... allDay 0..1booleanAlways available? e.g. 24 hour service
.... availableStartTime 0..1timeOpening time of day (ignored if allDay = true)
.... availableEndTime 0..1timeClosing time of day (ignored if allDay = true)
... notAvailable I0..*BackboneElementNot available during this time due to provided reason
.... id 0..1stringxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... description 1..1stringReason presented to the user explaining why time not available
.... during 0..1PeriodService not availablefrom this date
... availabilityExceptions 0..1stringDescription of availability exceptions
... endpoint S0..*Reference(Endpoint)Technical endpoints providing access to services operated for the practitioner with this role

doco Documentation for this format

Summary of the Mandatory Requirements

  1. One practitioner in PractitionerRole.practitioner
  2. One organization in PractitionerRole.organization
  3. One practitioner role code in PractitionerRole.code which has an extensible binding to:
  4. One practitioner specialty code in PractitionerRole.specialty which has an extensible binding to:
  5. One reference to a location in PractitionerRole.location
  6. At least one contact using either ‘PractitionerRole.telecom’ OR or reference to an Endpoint Resource in PractitionerRole.endpoint

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. PractitionerRole I0..*US Core PractitionerRole Profile
pd-1: SHALL have contact information or a reference to an Endpoint
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: Common Languages (extensible)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional Content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierBusiness Identifiers that are specific to a role/location
... active Σ0..1booleanWhether this practitioner's record is in active use
... period Σ0..1PeriodThe period during which the practitioner is authorized to perform in these role(s)
... practitioner SΣ1..1Reference(US Core Practitioner Profile)Practitioner that is able to provide the defined services for the organation
... organization SΣ1..1Reference(US Core Organization Profile)Organization where the roles are available
... code SΣ1..1CodeableConceptRoles which this practitioner may perform
Binding: Argonaut Provider Directory Provider Role (NUCC) (required)
... specialty SΣ1..1CodeableConceptSpecific specialty of the practitioner
Binding: Argonaut Provider Directory Provider Speciality (NUCC) (required)
... location SΣ0..*Reference(US Core Location Profile)The location(s) at which this practitioner provides care
... healthcareService 0..*Reference(HealthcareService)The list of healthcare services that this worker provides for this role's Organization/Location(s)
... telecom SΣ0..*ContactPointContact details that are specific to the role/location/service
.... id 0..1stringxml:id (or equivalent in JSON)
.... system SΣI1..1codephone | fax | email | pager | url | sms | other
Binding: ContactPointSystem (required)
.... value SΣ1..1stringThe actual contact point details
.... use ?!Σ0..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required)
.... rank Σ0..1positiveIntSpecify preferred order of use (1 = highest)
.... period Σ0..1PeriodTime period when the contact point was/is in use
... availableTime I0..*BackboneElementTimes the Service Site is available
.... id 0..1stringxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... daysOfWeek 0..*codemon | tue | wed | thu | fri | sat | sun
Binding: DaysOfWeek (required)
.... allDay 0..1booleanAlways available? e.g. 24 hour service
.... availableStartTime 0..1timeOpening time of day (ignored if allDay = true)
.... availableEndTime 0..1timeClosing time of day (ignored if allDay = true)
... notAvailable I0..*BackboneElementNot available during this time due to provided reason
.... id 0..1stringxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... description 1..1stringReason presented to the user explaining why time not available
.... during 0..1PeriodService not availablefrom this date
... availabilityExceptions 0..1stringDescription of availability exceptions
... endpoint S0..*Reference(Endpoint)Technical endpoints providing access to services operated for the practitioner with this role

doco Documentation for this format

Downloads: StructureDefinition: (XML, JSON, CSV), Schema: XML Schematron

 

SD.20.2 Quick Start

Below is an overview of the required set of RESTful FHIR interactions - for example, search and read operations - for this profile. See the Conformance requirements for a complete list of supported RESTful interactions for this IG.

GET [base]/PractitionerRole?practitioner.identifier=[system]|[code]

Example: GET [base]/PractitionerRole?practitioner.identifier=http://hl7.org/fhir/sid/us-npi%7C14|97860456

Support: Mandatory to support search by Practitioner identifier.

Implementation Notes: Search based on Practitioner identifier (NPI) (how to search by token).

GET [base]/PractitionerRole?practitioner.family=[string]&given=[string]

Example: GET [base]/PractitionerRole?practitioner.name=Henry

Support: Mandatory to support search by Practitioner name.

Implementation Notes: Search based on text name (how to search by string).

GET [base]/PractitionerRole?specialty=[system]|[code]

Example: GET [base]/PractitionerRole?specialty=http://hl7.org/fhir/practitioner-specialty%7Ccardio

Support: Mandatory to support search by Specialty.

Implementation Notes: Search based on specialty (how to search by token).

Searches to consider for future

GET [base]/PractitionerRole?location.address-city=[city]

GET [base]/PractitionerRole?location.address-city=[city]&specialty=[string]

GET [base]/PractitionerRole?location.near=-72.519854,42.373222&near-distance=2m

Implementation Notes: Search based on location (how to search by reference).