The FHIR STU3 (Release 3) Omnibus Care Plan (OCP) Practitioner profile uses FHIR resources and describes minimum expectations for the Practitioner 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 the below additional supported data elements to the OCP Practitioner profile as follows: Practitioner.email (1..*) (S) Practitioner.phoneNumber (1..*) (S) Also changed the cardinality of the supported data elements to the OCP Practitioner profile as follows: Practitioner.name.given(1..*)(S) Practitioner.address (0..*) (S) Dependencies: Practitioner profile that conform to this specification must include reference to other resources
  • Organization (custodian, custodians, information recipients )
  • OCP-Practitioner
 <status value="draft" /> <date value="2018-01-30" /> <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 profile describes about the Omnibus Care Plan (OCP) Practitioner who is directly or indirectly involved in the provisioning of healthcare. The profile sets minimum expectations for OCP Practitioner 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. This specification describes how OCP Practitioner populates a FHIR Practitioner resource. This OCP Practitioner profile does not use any contained resources. Contained resources allow the inadvertent sharing of Protected Information to unauthorized users and application. Therefore, any references to patients, providers, organizations are described as external references to resources stored on the same server. Practitioners include (but are not limited to): physicians, dentists, pharmacists, physician assistants, nurses, scribes, midwives, dietitians, therapists, optometrists, paramedics, medical technicians, laboratory scientists, prosthetic technicians, radiographers, social workers, professional home carers, official volunteers, receptionists handling patient registration, IT personnel merging or unmerging patient records." /> <jurisdiction> <coding> <code value="US" /> <display value="US-Realm" /> </coding> <text value="US-Realm OCP Practitioner Profile published by SAMHSA" /> </jurisdiction> <purpose value="The OCP Practitioner profile includes 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" /> <mapping> <identity value="v2" /> <uri value="http://hl7.org/v2" /> <name value="HL7 v2 Mapping" /> </mapping> <mapping> <identity value="rim" /> <uri value="http://hl7.org/v3" /> <name value="RIM Mapping" /> </mapping> <mapping> <identity value="servd" /> <uri value="http://www.omg.org/spec/ServD/1.0/" /> <name value="ServD" /> </mapping> <mapping> <identity value="w5" /> <uri value="http://hl7.org/fhir/w5" /> <name value="W5 Mapping" /> </mapping> <kind value="resource" /> <abstract value="false" /> <type value="Practitioner" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Practitioner" /> <derivation value="constraint" /> <differential> <element id="Practitioner"> <path value="Practitioner" /> <short value="OCP Practitioner" /> <definition value="This profile builds on US Core Practitioner and is basic constraint on provider for use in US Core resources." /> <alias value="Provider" /> <mustSupport value="false" /> <isModifier value="false" /> </element> <element id="Practitioner.identifier"> <path value="Practitioner.identifier" /> <definition value="An identifier that applies to this person in this role. Note: This is a business identifer, not a resource identifier" /> <requirements value="The following mandatory elements are needed for OCP Practitioner: identifier, name, and telecom." /> <min value="1" /> <mustSupport value="true" /> <isModifier value="false" /> </element> <element id="Practitioner.identifier.system"> <path value="Practitioner.identifier.system" /> <short value="NPI could be used as the identifier system in the US." /> <comment value="NPI could be used as the identifier system in the US." /> <min value="1" /> <example> <label value="General" /> <valueUri value="NPI preferred, Tax id is allowed, Local id is allowed in addition to 'authoritative' identifier" /> </example> <mustSupport value="true" /> <isModifier value="false" /> </element> <element id="Practitioner.identifier.value"> <path value="Practitioner.identifier.value" /> <min value="1" /> <mustSupport value="true" /> <isModifier value="false" /> </element> <element id="Practitioner.name"> <path value="Practitioner.name" /> <min value="1" /> <max value="1" /> <mustSupport value="true" /> <isModifier value="false" /> </element> <element id="Practitioner.name.family"> <path value="Practitioner.name.family" /> <min value="1" /> <mustSupport value="true" /> <isModifier value="false" /> </element> <element id="Practitioner.name.given"> <path value="Practitioner.name.given" /> <definition value="Given name. This repeating element order: Given Names appear in the correct order for presenting the name" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.telecom"> <path value="Practitioner.telecom" /> <slicing> <discriminator> <type value="value" /> <path value="system" /> </discriminator> <rules value="open" /> </slicing> <definition value="The profile for this data element will use slicing to distinguish the phone number from the email and ensure at least one of each was specified. A contact detail for the practitioner should be specified e.g. a telephone number and an email address." /> <comment value="Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently, and also to help with identification. These typically will have home numbers, or mobile numbers that are not role specific." /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.telecom:phone"> <path value="Practitioner.telecom" /> <sliceName value="phone" /> <definition value="A contact detail for the practitioner, e.g. a telephone number" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.telecom:phone.system"> <path value="Practitioner.telecom.system" /> <fixedCode value="phone" /> <mustSupport value="true" /> </element> <element id="Practitioner.telecom:phone.value"> <path value="Practitioner.telecom.value" /> <mustSupport value="true" /> </element> <element id="Practitioner.telecom:email"> <path value="Practitioner.telecom" /> <sliceName value="email" /> <definition value="A contact detail for the practitioner, e.g. email address." /> <comment value="Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently, and also to help with identification. These typically will have email address that are not role specific." /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.telecom:email.system"> <path value="Practitioner.telecom.system" /> <fixedCode value="email" /> <mustSupport value="true" /> </element> <element id="Practitioner.telecom:email.value"> <path value="Practitioner.telecom.value" /> <mustSupport value="true" /> </element> <element id="Practitioner.address"> <path value="Practitioner.address" /> <mustSupport value="true" /> </element> </differential> </StructureDefinition>