HL7v3 R02.04.03 Terminology questions

TerritorialAuthorityRoleType - the Provider Registry System (PRS) currently uses "Province" in its reference implementation

RestrictionToPracticeType - again, in its reference implementation PRS uses the following:
'ACAD', 'Academic'
'ADMIN', 'Adminstrative'
'AF', 'Armed Forces'
'ASSC', 'Associate'
'COURREG', 'Courtesy Register'
'EDUD', 'Education'
'ENH', 'Enhanced Scope of Practice'
'EXP', 'Expertise'
'FULLRESTRICT', 'Full license with Restrictions'
'GPH', 'Graduate Permit Holder'
'HONOR', 'Honorary'
'INTERN/RESIDENT', 'Intern or Resident'
'LMCC', 'Lic. of Med.Council of Canada'
'LOC', 'Location'
'MCCEE', 'Med. Counc. Canada Eval. Exam'
'NON-RX', 'Non-Prescribing'
'OTH', 'Other Conditions'
'PCYTYPE', 'Pharmacy Type'
'PRAC', 'Practice Restriction'
'REGISTRY', 'Registry'
'SPECMED', 'Special Medical'
'SPECREG', 'Special Register'
'STANDARD', 'Standard'
'TIME', 'Time limitation'

AssignedRoleType - I'll do more analysis regarding this

HealthcareProviderRoleType - the terminology worksheet and PRS seem to be in alignment except PRS also has 'PCY', 'Pharmacy', as PRS is also concerned about organizational providers

x_BasicPersonNamePartQualifier - internally PRS has a preferred name flag; we'd like to indicate a preferred name among many names in these interactions: PRPM_IN306011CA, PRPM_IN306051CA, PRPM_IN301010CA, PRPM_IN303030CA. Not sure how this would impact existing implementations as this is new functionality

Hi Alan,

Thank you for your questions on the terminology value sets supporting HL7 v3 R02.04.03. Please find my answers in bold enclosed with your questions below. Based on your responses for TerritorialAuthorityRoleType, RestrictionToPracticeType, and AssignedRoleType value sets, I may create new threads for us to discuss each in more detail. I will create a new thread on your inquiry regarding add “preferred name” to x_BasicPersonNamePartQualifier value set, which would expand the Basic Person Name data type.

TerritorialAuthorityRoleType - lists no codes in Value Set? Currently, there are no values in the TerritorialAuthorityRoleType value set since there is no known implementation of this value set or the Provider Registry information model component which requires this value set to support the component to date. Are there implementations projects interested in using the value set and/or the information model component used to carry this information in the message? Using the clinical interoperability framework, the starting point is the requirements from the implementation projects confirmed with discussions and refinement, then the value sets would be consider to represent the requirements. Do you have any additional information from implementation projects?

RestrictionToPracticeType - lists no codes in Value Set? Similar to the TerritorialAuthorityRoleType, there is very little known about what the implementation projects have used. There is one jurisdictions who may have implemented this and I’ll reach out to see if there’s additional information. Do you have requirements from implementations projects which can serve as a basis to formulate the value set?

AssignedRoleType - may need to use code not in Value Set, is this possible? Based on the context, it is identify a functional role a health care provider plays inside an organization, I suggest using the ProviderRoleCode subset from the Primary Care Subsets found here: infocentral.infoway-inforoute.ca/2_Standards/1_pan-Canadian_Standards/Terminology/pan-Canadian_Subset_Library/Primary_Health_Care_(PHC)_Reference_Sets/PHC_Reference_Sets_Current_Release_(Individual). Again, the business requirements should be confirmed to ensure the subset meets the requirements.

HealthcareProviderRoleType - may need to use code not in Value Set, is this possible? What kind of concepts are we talking about? Is it used only within one jurisdiction or between jurisdictions? If they are to be shared between jurisdictions, it needs to be added to the value set, so that everyone has access to the “master” value set.

x_BasicPersonNamePartQualifier - would like to use a code representing "preferred", is this possible? x_BasicPersonnamePartQualifier is used to support the Basic Person Name data type (technical name: PN.BASIC). The design of the Basic Person Name data type was intended to only support Initial as a given name and Last Name. To add “preferred”, this means we would need to expand the data elements supported in Basic Person Name data type and would be impact to existing implementations using the existing data type. Which messages are you considering where this would be used? As you are aware, the “preferred name” concept is listed in the x_FullPersonNamePartQualifier value set, the concept is called “call me” with a description: A callme name is (usually a given name) that is preferred when a person is directly addressed. Hence, such concept already exist however need to understand the new business requirements and impact to existing implementations to move forward.

I encourage those using or looking to use the specified value sets and data types to participating in this discussion. Looking forward to further discussions.

Best regards,
Wendy Huang
Standards Subject Matter Expert
Canada Health Infoway Inc.

We're implementing with the R02.04.03 standard and the terminology worksheet "SC-3004-EN - Terminology Worksheet - R02.04.02_Release - 20100326.xls" accompanying that standard is causing some issues:

TerritorialAuthorityRoleType - lists no codes in Value Set?
RestrictionToPracticeType - lists no codes in Value Set?
AssignedRoleType - may need to use code not in Value Set, is this possible?
HealthcareProviderRoleType - may need to use code not in Value Set, is this possible?
x_BasicPersonNamePartQualifier - would like to use a code representing "preferred", is this possible?