Shared Health Specification and Guide Version 2.0 Revision F

 

The official URL for this profile is:

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

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..*Definition:
A person who is directly or indirectly involved in the provisioning of healthcare.


Comments:
Note that a cab driver no longer fits the bill. You probably would be interested in the organization rather than the individual?

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


Comments:
Conformance Note: This will be a GUID assigned by the sending application in the form urn:uuid:[guid]. Ideally, this guid will be consistent for all messages referencing the same practitioner.

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


Comments:
Conformance Rule: Legal name is mandatory. Set use = Professional; Alias is optional

Conformance Rule: Name structure is defined by Shared Health Human Name data type. Please refer to Shared Health Human Name data type profile.

..  telecom 0..*Shared Health ContactPointcpt-2: A system is required if a value is provided.
Definition:
Used to convey the private number of the prescriber and may be used if the pharmacy needs to contact directly. This is typically a cell number. Conformance Rule: Telecom structure is defined by Shared Health contact point data type. Please refer to Shared Health ContactPoint data type profile.


Comments:
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.

..  practitionerRole 1..1BackboneElementDefinition:
The list of roles/organizations that the practitioner is associated with.


Comments:
The address to be used for this PractitionerRole is in the referenced location (removing duplication across all the services provided at the location).

...  role 1..1CodeableConceptBinding: PractitionerRole (example)
Definition:
Roles which this practitioner is authorized to perform for the organization.


Comments:
A person may have more than one role. At least one role is required.

....  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 'title' of the non-clinician practitioner. E.g. 'Receptionist', 'clinic manager', etc.

This structure is derived from Practitioner

Summary

Mandatory: 5 elements
Must-Support: 6 elements

Structures

This structure refers to these other structures:

NameFlagsCard.TypeDescription & Constraintsdoco
.. Practitioner S0..*A 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)
... 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..*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)
... 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)
..... 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)
.... 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)
.... 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)

doco Documentation for this format

Grid View

This structure is derived from Practitioner

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


Comments:
Note that a cab driver no longer fits the bill. You probably would be interested in the organization rather than the individual?

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


Comments:
Conformance Note: This will be a GUID assigned by the sending application in the form urn:uuid:[guid]. Ideally, this guid will be consistent for all messages referencing the same practitioner.

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


Comments:
Conformance Rule: Legal name is mandatory. Set use = Professional; Alias is optional

Conformance Rule: Name structure is defined by Shared Health Human Name data type. Please refer to Shared Health Human Name data type profile.

..  telecom 0..*Shared Health ContactPointcpt-2: A system is required if a value is provided.
Definition:
Used to convey the private number of the prescriber and may be used if the pharmacy needs to contact directly. This is typically a cell number. Conformance Rule: Telecom structure is defined by Shared Health contact point data type. Please refer to Shared Health ContactPoint data type profile.


Comments:
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.

..  practitionerRole 1..1BackboneElementDefinition:
The list of roles/organizations that the practitioner is associated with.


Comments:
The address to be used for this PractitionerRole is in the referenced location (removing duplication across all the services provided at the location).

...  role 1..1CodeableConceptBinding: PractitionerRole (example)
Definition:
Roles which this practitioner is authorized to perform for the organization.


Comments:
A person may have more than one role. At least one role is required.

....  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 'title' of the non-clinician practitioner. E.g. 'Receptionist', 'clinic manager', etc.

This structure is derived from Practitioner

Summary

Mandatory: 5 elements
Must-Support: 6 elements

Structures

This structure refers to these other structures:

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Practitioner S0..*A 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)
... 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..*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)
... 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)
..... 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)
.... 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)
.... 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)

doco Documentation for this format

 

Other representations of profile: Schematron

Terminology Bindings

PathNameConformanceValueSet
Practitioner.language?extrequiredhttp://tools.ietf.org/html/bcp47
Practitioner.genderAdministrativeGenderrequiredAdministrativeGender
Practitioner.practitionerRole.rolePractitionerRoleexamplePractitionerRole
Practitioner.practitionerRole.specialtyPractitionerSpecialtyexamplePractitionerSpecialty
Practitioner.qualification.codeANZSCO -- Australian and New Zealand Standard Classification of Occupations, 2013, Version 1.2exampleANZSCO -- Australian and New Zealand Standard Classification of Occupations, 2013, Version 1.2
Practitioner.communication?extrequiredhttp://tools.ietf.org/html/bcp47

Constraints

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