HL7v3 R02.04.03 Terminology questions

Here are descriptions associated with the terms Alan posted above.


ACAD: Academic: Applies to providers who are providing academic education preparation. These providers do not provide patient care directly but require a license to supervise the education of students.

ADMIN: Administrative: A provider who is in an Administrative role. For example, a provider in an executive administrative or research role that is fully licensed, but not practicing in the profession. For example, a provider who is authorized by an employing health care body

AF: Armed Forces: Limited to practicing on armed forces personnel or while on base.

ASSC: Associate: Associate members are licensed providers who continue to be recognized by their college but are not actively practicing in the jurisdicition.

COURREG: Courtesy Register: Indicates a limitation imposed via the courtesy register license.

EDUD: Education: Education only license for a student.

ENH: Enhanced Scope of Practice: A condition type identifying enhanced practice privileges within a particular role that have been authorized on a provider’s license.

EXP: Expertise: Practice limited to a specific area of expertise.

FULLRESTRICT: Full license with Restrictions: Represents restrictions on a STANDARD condition license.

GPH: Graduate Permit Holder: Temporary permit holders for nurses

HONOR: Honorary: Has achieved a recognition of long-term service, has an active license but is restricted in practice.

INTERN/RESIDEN: Intern or Resident: Post graduate training positions

LMCC: Lic. of Med.Council of Canada: Second exam from Medical Council of Canada written by foreign and domestic medical graduates

LOC: Location: Practice limited to specific geographical locations.

MCCEE: Med. Counc. Canada Eval. Exam: Evaluation exam from Medical Council of Canada written by foreign medical students

NON-RX: Non-Prescribing: Practice limited with regards to prescribing.

OTH: Other Conditions: A Condition whose actual value is not an element in the value domain (e.g., concept not provided by required code system).

PCYTYPE: Pharmacy Type: Indicates a limitation and/or enhancement imposed via a pharmacy license.

PRAC: Practice Restriction: Practice limited by the licensing body.

REGISTRY: Registry: License limited by conditions of registration.

SPECMED: Special Medical: Limited to a specific license for a location.

SPECREG: Special Register: Indicates a limitation imposed via the special register license

STANDARD Standard: Conditions set to the standard for license and jurisdiction in question.

TIME: Time limitation: Limited to a specific period in time

I've updated the PPT at ic.infoway-inforoute.ca/en/resources/docs/hl7/412-2015-09-01-terminology-requests with some more details and examples.

I've uploaded a PowerPoint to further describe our requests at ic.infoway-inforoute.ca/en/resources/docs/hl7/412-2015-09-01-terminology-requests

Thanks Wendy for your feedback. After discussion with Kris Lewis, here's our input:

TerritorialAuthorityRoleType
- "Province" is in use in BC, AB, NFLD
- For the next version of PRS, we need these concepts: (1) Licensing authority, (2) Non-licensing authority

RestrictionToPracticeType
At least AB makes use of the codes stated earlier (i.e. 'ACAD', 'Academic', etc.)

AssignedRoleType
- For the next version of PRS, we need these concepts: (1) WorkLocation, (2) InformationRoute, (3) HealthCareOrganization

x_BasicPersonNamePartQualifier
We will order the name elements according to preference and provide those implementing appropriate guidance. No datatype change to PN.FULL is necessary.

Correction re: x_BasicPersonNamePartQualifier value set, PRS would be using preferred name on the interaction PRPM_IN301030CA - Add Provider Notification (rather than Add Provider Request)

Hi Alan,

I reviewed one of the information models which uses the value set TerritorialAuthorityRoleType. Based on the interpretation, it's unclear if a concept such as "province" aligns with the intended semantics to be conveyed with TerritorialAuthorityRoleType. TerritorialAuthorityRoleType value set is used to represent the role of the authoritative organization which a provider in a designated role represents.

Using one of the information model which references this (Add Provider, TerritorialAuthority.code): infocentral.infoway-inforoute.ca/extra/ca/mr020501-html/html/message.html?PRPM_MT301010CA.TerritorialAuthority.code, the intended semantics is likely the following (using example concepts in each piece of the information model component to illustrate the semantics):

AssignedEntity (specific role a provider plays in a specific context) e.g. public health nurse
Organization (name of the represented organization which assigned the role): e.g. ABC Public Health Unit
TerritorialAuthority (the role of the represented organization): public health authority
Jurisdiction (the boundary that the represented organization operate in): e.g. Alberta

Based on the above semantics interpretation, some example concepts could be: public health authority, judicial authority and national authority.

In terms of using "Province" as the value in the TerritorialAuthority - can you confirm implementations using the PRS product are using this value? I would like to gauge the adoption of this information model component and the active use of the "Province" concept in the existing implementations to propose some suggestions for the community's consideration.

Perhaps the model can be simplified a bit, and I would encourage implementations based on the pan-Canadian Provider Registry standard to chime in provide your business requirements which would use this value set and the values you are using today.

In terms of RestrictionToPracticeType value set - are there other implementations which has implemented this function of the provider profile?

HealthcareProviderRoleType value set - can you provide more details around this "Pharmacy" concept? This value set contains provider types as assigned by the professional colleges in the jurisdictions. We have a concept called "Pharmacist" with code "PHARM" to address the "pharamcy" aspect. I am struggling to see how "pharmacy" would be a provider type. Are you trying to use it in another context?

x_BasicPersonNamePartQualifier value set - this is fixed to a specific data type usage - Basic Person name (PN.BASIC). If the requirement is to include a preferred name (the concept would be "call me"), then the change would need to be change the data type from Basic Person Name (PN.BASIC) to Full Person Name (PN.FULL). I think we need a broader community discussion on this one to understand the impact to all existing implementations. Theoretically, existing implementations using the Basic Person Name data type would be a proper a constraint of the Full Person Name data type however I encourage those who are using the Provider Registry standard, specifically the following interactions to participate in this discussion we put the big picture together.

PRPM_IN306011CA - Provider Details Query Response
PRPM_IN306051CA - Provider Associated Identifiers Query Response
PRPM_IN301010CA - Add Provider Request
PRPM_IN303030CA - Update Provider Notification

I encourage all those who are interested in this topic to participate in the discussion.

Best regards,
Wendy Huang