Implementation Guide
23.1.0 - R4 APIs

Publish Box goes here

Resource Profile: Profile - Athena PractitionerRole

Official URL: https://docs.mydata.athenahealth.com/fhir-r4/StructureDefinition/athena-practitionerrole-profile Version: 23.1.0
Active as of 2022-03-01 Computable Name: AthenaPractitionerRole

Defines constraints and extensions on the practitionerrole resource as supported by Athena Products.

This PractitionerRole profile is part of the set of resource profiles supported by the API Server used with the athenaPractice and athenaFlow products. It further describes read and search capabilities of these products. Note: The create and update operations are NOT supported for this resource.

Overview

This resource records the person who is directly or indirectly involved in the provisioning of healthcare. For ambulatory clinics, this is typically the physician or nurse attending to a patient.

Scope and Usage

This profile is used to define the content that will be returned by the API Server in response to requests to access PractitionerRole resources. All elements listed in the differential profile view are Supported, which means that the API Server is capable of supplying these fields from the product database when they have been populated via the product or its APIs.

Source

The PractitionerRole resource describes a specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time. It is derived from the DoctorFacility and SERVPROV tables in athenaPractice and the USR, SERVPROV and PERSON tables in athenaFlow. Specific detail can be found in the Mappings tab in the profile detail page.

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from PractitionerRole

NameFlagsCard.TypeDescription & Constraintsdoco
.. PractitionerRole 0..* PractitionerRole Roles/organizations the practitioner is associated with
... id 0..1 id Logical id of this artifact
... meta 0..1 Meta Metadata about the resource
.... versionId S 0..1 id Version specific identifier
.... Slices for profile 2..* canonical() Profiles this resource claims to conform to
Slice: Unordered, Open by value:uri
..... profile:USCore PractitionerRole Profile 1..1 canonical() Profiles this resource claims to conform to
Fixed Value: http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole
..... profile:Athena PractitionerRole Profile 1..1 canonical() Profiles this resource claims to conform to
Fixed Value: https://docs.mydata.athenahealth.com/fhir-r4/StructureDefinition/athena-practitionerrole-profile
... Slices for identifier S 1..* Identifier Business Identifiers that are specific to a role
Slice: Unordered, Open by value:type
.... identifier:PRACTITIONERID 0..1 Identifier Business Identifiers that are specific to a role/location
..... use 1..1 code usual | official | temp | secondary | old (If known)
..... type S 0..1 CodeableConcept Description of identifier
...... coding 1..1 Coding Code defined by a terminology system
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://terminology.hl7.org/CodeSystem/v2-0203
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: PN
..... system S 1..1 uri The namespace for the identifier value
..... value S 1..1 string The value that is unique
.... identifier:NPI 0..1 Identifier Business Identifiers that are specific to a role/location
..... use 1..1 code usual | official | temp | secondary | old (If known)
..... type S 0..1 CodeableConcept Description of identifier
...... coding 1..1 Coding Code defined by a terminology system
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://terminology.hl7.org/CodeSystem/v2-0203
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: NPI
..... system S 1..1 uri The namespace for the identifier value
Fixed Value: http://hl7.org/fhir/sid/us-npi
..... value S 1..1 string The value that is unique
.... identifier:TAX 0..1 Identifier Business Identifiers that are specific to a role/location
..... use 1..1 code usual | official | temp | secondary | old (If known)
..... type S 0..1 CodeableConcept Description of identifier
...... coding 1..1 Coding Code defined by a terminology system
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://terminology.hl7.org/CodeSystem/v2-0203
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: TAX
..... system S 1..1 uri The namespace for the identifier value
Fixed Value: urn:oid:2.16.840.1.113883.4.2
..... value S 1..1 string The value that is unique
... practitioner S 1..1 Reference(Practitioner) Practitioner that is able to provide the defined services for the organization
... organization S 1..1 Reference(Organization) Organization where the roles are available
... code S 0..1 CodeableConcept Role which this practitioner may perform
... specialty S 0..1 CodeableConcept Specific specialty of the practitioner
... location S 0..1 Reference(Location) The location at which this practitioner provides care
... endpoint 0..* Reference(Endpoint) Technical endpoints providing access to services operated for the practitioner with this role

doco Documentation for this format

 

Other representations of profile: CSV, Excel, Schematron

Notes:

Supported Interactions

Interactions supported by this resource are listed below.

Search Parameters

Search parameters are executed as specified in the HL7 FHIR RESTful API implementation definition. To search for PractitionerRole resources, an application shall perform an HTTP GET, specifying the query parameters associated with the resource.

GET [base]/fhir/r4/PractitionerRole?{search-parameters}{&_count=[max-results]&_format=[json|xml]&_summary=[true|text|data]}

Where:

Name Description
[base] Specifies the base URL of the FHIR Server, e.g., https://apsandbox.fhirapi.athenahealth.com/demoAPIServer
[_count] Specifies the maximum number of search results to return in a single query. Note: The count of results does not limit the number of additional resources returned via the _include parameter. No more than max-results PractitionerRole resources which match the search criteria will be returned. The API Server has default and maximum limits for the value that can be specified for this parameter. These limits may vary depending upon the client application vendors participation level in the Athenahealth Partner program. Note: The API Server support the HL7 FHIR Paging capability.
[_format] Specifies the format of the output and may be xml or json. When present, the _format value overrides the value of the Accept header in the request.
[_summary] Filters the output to include only narrative elements (_summary=text), summary elements (_summary=true) or to omit the generated narrative (_summary=data). Note: If the generated html narrative for the resource is not going to be used by the call, using _summary=data provides improved API response times, especially when returning larger result sets.
_id (token) The ID of the resource
active (token) Whether this practitioner role record is in active use
identifier (token) A practitioner's Identifier
location (reference) One of the locations at which this practitioner provides care
organization (reference) The identity of the organization the practitioner represents / acts on behalf of
practitioner (reference) Practitioner that is able to provide the defined services for the organization
role (token) The practitioner can perform this role at for the organization
specialty (token) The practitioner has this specialty at an organization
endpoint (reference) Technical endpoints providing access to services operated for the practitioner with this role
HTTP Response Codes

The following HTTP response codes are returned by this API call:

200 OK The query was performed and any results found are contained within the body of the HTTP response. Note: The search API will return 200 OK when the query itself is successful, regardless of whether or not any matching results were found.
401 Unauthorized Authorization is required for this request, and either the Authorization header is missing or the supplied user credentials in the Authorization header are not valid or have expired. The body of the HTTP response will contain an OperationOutcome resource that indicates that Authorization is required.
500 Server Error The server may return other error codes to indicate other error conditions. The body of the HTTP response will contain an OperationOutcome resource that indicates the nature of the error.