Shared Health Specification and Guide Version 5.0

 

3.75 StructureDefinition: Shared Health Non-Clinician Practitioner

The official URL for this profile is: 

http://sharedhealth.exchange/fhir/StructureDefinition/profile-practitioner-nonclinician

3.75.2 Formal Views of Profile Content

Download Excel representation

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

>

This structure is derived from Practitioner

NameCard.TypeConstraints and Usage
.  Practitioner 0..*PractitionerDefinition:
A person who is directly or indirectly involved in the provisioning of healthcare.


Comments:


..  id 1..1idDefinition:
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.


Comments:
Usage Note: This will usually be a GUID and is assigned by the sending application.

..  name 1..1Shared Health HumanNameDefinition:
A human's name with the ability to identify parts and usage.


Comments:
This data type is used to support both Practitioner names and Patient names. These name values are used for SAML validation (Practitioner) and eFax generation, and possibly patient matching algorithms.



Conformance Rule: For the purpose of presentation, the data elements will be organized as Prefix + Given1 + Given2 + Family + Suffix.

..  telecom 0..*Shared Health ContactPointcpt-2: A system is required if a value is provided.
Definition:
This segment provide methods of contacting the practitioner. Only numbers that have authorized to be disclosed by the practitioner should be included. For example, most practitioners do not authorize the disclosure of their cell phone number to pharmacies.


Comments:


..  practitionerRole 1..1BackboneElementDefinition:
The person's role within the organization.


Comments:


...  role 1..1CodeableConceptBinding: PractitionerRole (example): The role a person plays representing an organization


Definition:
Roles which this person practitioner is authorized to perform for the organization.


Comments:
The person's role only needs to be sent as a text value and not as a coded value. Send the person's role as stored in your application

....  text 1..1stringDefinition:
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.


Comments:
This indicates the users role within the organization e.g. 'Receptionist', 'clinic manager', office staff etc.



A person may have more than one role. At least one role is required. Multiple roles can be sent where each is comma separated.

This structure is derived from Practitioner

Summary

Mandatory: 5 elements
Must-Support: 6 elements

Structures

This structure refers to these other structures:

This structure is derived from Practitioner

NameFlagsCard.TypeDescription & Constraintsdoco
.. Practitioner S0..*PractitionerA person with a formal responsibility in the provisioning of healthcare or related services
... id S1..1idLogical id of this artifact
... name S1..1Shared Health HumanNameName of a human - parts and usage
... telecom S0..*Shared Health ContactPointDetails of a Technology mediated contact point (phone, fax, email, etc.)
... practitionerRole S1..1BackboneElementRoles/organizations the practitioner is associated with
.... role S1..1CodeableConceptRoles which this practitioner may perform
..... text S1..1stringPlain text representation of the concept

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. Practitioner S0..*PractitionerA person with a formal responsibility in the provisioning of healthcare or related services
... id SΣ1..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: http://tools.ietf.org/html/bcp47 (required): A human language.


... text 0..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..*IdentifierA identifier for the person as this agent
... active Σ0..1booleanWhether this practitioner's record is in active use
... name S1..1Shared Health HumanNameName of a human - parts and usage
... telecom SI0..*Shared Health ContactPointDetails of a Technology mediated contact point (phone, fax, email, etc.)
... address Σ0..*AddressAddress(es) of the practitioner that are not role specific (typically home address)
... gender Σ0..1codemale | female | other | unknown
Binding: AdministrativeGender (required): The gender of a person used for administrative purposes.

... birthDate Σ0..1dateThe date on which the practitioner was born
... photo 0..*AttachmentImage of the person
... practitionerRole S1..1BackboneElementRoles/organizations the practitioner is associated with
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... organization 0..1Reference(Organization)Organization where the roles are performed
.... role SΣ1..1CodeableConceptRoles which this practitioner may perform
Binding: PractitionerRole (example): The role a person plays representing an organization

..... id 0..1idxml:id (or equivalent in JSON)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... coding Σ0..*CodingCode defined by a terminology system
..... text SΣ1..1stringPlain text representation of the concept
.... specialty Σ0..*CodeableConceptSpecific specialty of the practitioner
Binding: PractitionerSpecialty (example): Specific specialty associated with the agency


.... identifier Σ0..*IdentifierBusiness Identifiers that are specific to a role/location
.... telecom Σ0..*ContactPointContact details that are specific to the role/location/service
.... period Σ0..1PeriodThe period during which the practitioner is authorized to perform in these role(s)
.... location 0..*Reference(Location)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)
... qualification 0..*BackboneElementQualifications obtained by training and certification
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... identifier 0..*IdentifierAn identifier for this qualification for the practitioner
.... code 1..1CodeableConceptCoded representation of the qualification
Binding: ANZSCO -- Australian and New Zealand Standard Classification of Occupations, 2013, Version 1.2 (example): Specific qualification the practitioner has to provide a service

.... period 0..1PeriodPeriod during which the qualification is valid
.... issuer 0..1Reference(Organization)Organization that regulates and issues the qualification
... communication 0..*CodeableConceptA language the practitioner is able to use in patient communication
Binding: http://tools.ietf.org/html/bcp47 (required): A human language.



doco Documentation for this format

Grid View

This structure is derived from Practitioner

NameCard.TypeConstraints and Usage
.  Practitioner 0..*PractitionerDefinition:
A person who is directly or indirectly involved in the provisioning of healthcare.


Comments:


..  id 1..1idDefinition:
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.


Comments:
Usage Note: This will usually be a GUID and is assigned by the sending application.

..  name 1..1Shared Health HumanNameDefinition:
A human's name with the ability to identify parts and usage.


Comments:
This data type is used to support both Practitioner names and Patient names. These name values are used for SAML validation (Practitioner) and eFax generation, and possibly patient matching algorithms.



Conformance Rule: For the purpose of presentation, the data elements will be organized as Prefix + Given1 + Given2 + Family + Suffix.

..  telecom 0..*Shared Health ContactPointcpt-2: A system is required if a value is provided.
Definition:
This segment provide methods of contacting the practitioner. Only numbers that have authorized to be disclosed by the practitioner should be included. For example, most practitioners do not authorize the disclosure of their cell phone number to pharmacies.


Comments:


..  practitionerRole 1..1BackboneElementDefinition:
The person's role within the organization.


Comments:


...  role 1..1CodeableConceptBinding: PractitionerRole (example): The role a person plays representing an organization


Definition:
Roles which this person practitioner is authorized to perform for the organization.


Comments:
The person's role only needs to be sent as a text value and not as a coded value. Send the person's role as stored in your application

....  text 1..1stringDefinition:
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.


Comments:
This indicates the users role within the organization e.g. 'Receptionist', 'clinic manager', office staff etc.



A person may have more than one role. At least one role is required. Multiple roles can be sent where each is comma separated.

This structure is derived from Practitioner

Summary

Mandatory: 5 elements
Must-Support: 6 elements

Structures

This structure refers to these other structures:

Differential View

This structure is derived from Practitioner

NameFlagsCard.TypeDescription & Constraintsdoco
.. Practitioner S0..*PractitionerA person with a formal responsibility in the provisioning of healthcare or related services
... id S1..1idLogical id of this artifact
... name S1..1Shared Health HumanNameName of a human - parts and usage
... telecom S0..*Shared Health ContactPointDetails of a Technology mediated contact point (phone, fax, email, etc.)
... practitionerRole S1..1BackboneElementRoles/organizations the practitioner is associated with
.... role S1..1CodeableConceptRoles which this practitioner may perform
..... text S1..1stringPlain text representation of the concept

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Practitioner S0..*PractitionerA person with a formal responsibility in the provisioning of healthcare or related services
... id SΣ1..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: http://tools.ietf.org/html/bcp47 (required): A human language.


... text 0..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..*IdentifierA identifier for the person as this agent
... active Σ0..1booleanWhether this practitioner's record is in active use
... name S1..1Shared Health HumanNameName of a human - parts and usage
... telecom SI0..*Shared Health ContactPointDetails of a Technology mediated contact point (phone, fax, email, etc.)
... address Σ0..*AddressAddress(es) of the practitioner that are not role specific (typically home address)
... gender Σ0..1codemale | female | other | unknown
Binding: AdministrativeGender (required): The gender of a person used for administrative purposes.

... birthDate Σ0..1dateThe date on which the practitioner was born
... photo 0..*AttachmentImage of the person
... practitionerRole S1..1BackboneElementRoles/organizations the practitioner is associated with
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... organization 0..1Reference(Organization)Organization where the roles are performed
.... role SΣ1..1CodeableConceptRoles which this practitioner may perform
Binding: PractitionerRole (example): The role a person plays representing an organization

..... id 0..1idxml:id (or equivalent in JSON)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... coding Σ0..*CodingCode defined by a terminology system
..... text SΣ1..1stringPlain text representation of the concept
.... specialty Σ0..*CodeableConceptSpecific specialty of the practitioner
Binding: PractitionerSpecialty (example): Specific specialty associated with the agency


.... identifier Σ0..*IdentifierBusiness Identifiers that are specific to a role/location
.... telecom Σ0..*ContactPointContact details that are specific to the role/location/service
.... period Σ0..1PeriodThe period during which the practitioner is authorized to perform in these role(s)
.... location 0..*Reference(Location)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)
... qualification 0..*BackboneElementQualifications obtained by training and certification
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... identifier 0..*IdentifierAn identifier for this qualification for the practitioner
.... code 1..1CodeableConceptCoded representation of the qualification
Binding: ANZSCO -- Australian and New Zealand Standard Classification of Occupations, 2013, Version 1.2 (example): Specific qualification the practitioner has to provide a service

.... period 0..1PeriodPeriod during which the qualification is valid
.... issuer 0..1Reference(Organization)Organization that regulates and issues the qualification
... communication 0..*CodeableConceptA language the practitioner is able to use in patient communication
Binding: http://tools.ietf.org/html/bcp47 (required): A human language.



doco Documentation for this format

 

Other representations of profile: Schematron

3.75.3 Terminology Bindings

Terminology Bindings

PathConformanceValueSet
Practitioner.languagerequiredhttp://tools.ietf.org/html/bcp47
Practitioner.genderrequiredAdministrativeGender
Practitioner.practitionerRole.roleexamplePractitionerRole
Practitioner.practitionerRole.specialtyexamplePractitionerSpecialty
Practitioner.qualification.codeexampleANZSCO -- Australian and New Zealand Standard Classification of Occupations, 2013, Version 1.2
Practitioner.communicationrequiredhttp://tools.ietf.org/html/bcp47

3.75.4 Constraints

Constraints

IdPathDetailsRequirements
cpt-2Practitioner.telecomA system is required if a value is provided.
: value.empty() or system.exists()