The FHIR STU3 (Release 3) Omnibus Care Plan (OCP) PractitionerRole profile uses FHIR resources and describes minimum expectations for the PractitionerRole resource to record [content] associated with a patient. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. Added below all the supported data elements to the OCP PractitionerRole profile: active (1..1) (S) period (0..1) (S) practitioner (1..1) (S) organization (1..1) (S) code (1..1) (S) specialty (1..1) (S) location (0..*) (S) telecom (0..*) (S) endpoint (0..*) (S) Dependencies: PractitionerRole profile that conform to this specification must include reference to other resources
  • Organization (custodian, custodians, information recipients )
  • OCP-Practitioner
  • Location
  • OCP-HealthcareService
 <status value="draft" /> <date value="2018-03-20" /> <publisher value="SAMHSA" /> <contact> <name value="Neelima Chennamaraja, , Ioana Singureanu" /> <telecom> <system value="url" /> <value value="www.eversolve.com" /> <period> <start value="1999-06-15" /> </period> </telecom> <telecom> <system value="email" /> <value value="neelima@eversolve.com" /> <use value="work" /> </telecom> </contact> <description value="This Omnibus Care Plan (OCP) PractitionerRole profile describes a specific set of roles/locations/specialties/services that a practitioner may perform at an organization for a period of time. The profile identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. PractitionerRole covers the recording of the location and types of services that Practitioners are able to provide for an organization. The role, specialty, location and telecom properties can be repeated if required in other instances of the PractitionerRole. Some systems record a collection of service values for a single location, others record the single service and the list of locations it is available. Both are acceptable options for representing this data. Qualifications (from the Practitioner resource) do not imply a Role, but might be considered when an Organization allocates practitioners to roles within their organization, and could provide useful information (such as expiry information) which could need to be tracked in some situations to ensure they continue to be eligible for a specific role." /> <jurisdiction> <coding> <code value="US" /> <display value="US-Realm" /> </coding> <text value="US-Realm OCP PractitionerRole Profile published by SAMHSA" /> </jurisdiction> <purpose value="This OCP profile for PractitionerRole resource includes supported fields not defined in US-Core Profile. This profile is intended to be implemented by OCP (Omnibus Care Plan) systems." /> <copyright value="+Copyright (c) 2017 SAMHSA. All Rights Reserved." /> <fhirVersion value="3.0.1" /> <kind value="resource" /> <abstract value="false" /> <type value="PractitionerRole" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/PractitionerRole" /> <derivation value="constraint" /> <differential> <element id="PractitionerRole"> <path value="PractitionerRole" /> <definition value="This profile describes about the Omnibus Care Plan (OCP) PractitionerRole, a specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time. The profile sets minimum expectations for OCP PractitionerRole associated with a patient. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. PractitionerRole covers the recording of the location and types of services that Practitioners are able to provide for an organization. The role, specialty, location and telecom properties can be repeated if required in other instances of the PractitionerRole. Some systems record a collection of service values for a single location, others record the single service and the list of locations it is available. Both are acceptable options for representing this data. Practitioner performs different roles within the same or even different organizations. Depending on jurisdiction and custom, it may be necessary to maintain a specific Practitioner Resource for each such role or have a single Practitioner with multiple roles. The role can be limited to a specific period, after which authorization for this role ends. Note that the represented organization need not necessarily be the (direct) employer of a Practitioner." /> </element> <element id="PractitionerRole.active"> <path value="PractitionerRole.active" /> <min value="1" /> <type> <code value="boolean" /> <profile value="http://hl7.org/fhir/StructureDefinition/boolean" /> </type> <mustSupport value="true" /> </element> <element id="PractitionerRole.period"> <path value="PractitionerRole.period" /> <definition value="The period during which the person is authorized to act as a practitioner in these role(s) for the organization. Adding to profile but may be implemented at later time to restrict the relationship to specific time period." /> <mustSupport value="true" /> </element> <element id="PractitionerRole.period.start"> <path value="PractitionerRole.period.start" /> <definition value="The start of the period. The boundary is inclusive. Start date default to current date when created." /> </element> <element id="PractitionerRole.period.end"> <path value="PractitionerRole.period.end" /> <definition value="The end of the period. If the end of the period is missing, it means that the period is ongoing. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. End Date populated with current date when status is changed to inactivate." /> </element> <element id="PractitionerRole.practitioner"> <path value="PractitionerRole.practitioner" /> <short value="Practitioner that is able to provide the defined services for the organization" /> <definition value="Practitioner that is able to provide the defined services for the organization." /> <min value="1" /> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/ocp-practitioner" /> </type> <mustSupport value="true" /> </element> <element id="PractitionerRole.organization"> <path value="PractitionerRole.organization" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="PractitionerRole.code"> <path value="PractitionerRole.code" /> <definition value="Roles which this practitioner is authorized to perform for the organization. The code is selected either from nucc codes or administrator role codes (CAREMGNR, ORGADMIN)." /> <min value="1" /> <max value="1" /> <type> <code value="CodeableConcept" /> <profile value="http://hl7.org/fhir/StructureDefinition/CodeableConcept" /> </type> <mustSupport value="true" /> </element> <element id="PractitionerRole.specialty"> <path value="PractitionerRole.specialty" /> <min value="1" /> <max value="1" /> <type> <code value="CodeableConcept" /> <profile value="http://hl7.org/fhir/StructureDefinition/CodeableConcept" /> </type> <mustSupport value="true" /> </element> <element id="PractitionerRole.location"> <path value="PractitionerRole.location" /> <definition value="The location(s) at which this practitioner provides ca re." /> <mustSupport value="true" /> </element> <element id="PractitionerRole.healthcareService"> <path value="PractitionerRole.healthcareService" /> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/ocp-healthcareservice" /> </type> </element> <element id="PractitionerRole.telecom"> <path value="PractitionerRole.telecom" /> <mustSupport value="true" /> </element> <element id="PractitionerRole.telecom.system"> <path value="PractitionerRole.telecom.system" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="PractitionerRole.telecom.value"> <path value="PractitionerRole.telecom.value" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="PractitionerRole.endpoint"> <path value="PractitionerRole.endpoint" /> <comment value="References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. May be used at later time." /> <mustSupport value="true" /> </element> </differential> </StructureDefinition>