Implementations Using JPID Identifier Type

We have found 4 entries in the Canadian URI Registry that are using the type JPID.
Please see the details below and the type that we are suggesting be used instead for each.
Please review this information and let us know if you have any issue with the type being changed for these URIs.

Indigenous and Northern Affairs Canada number
- urn:oid:2.16.840.1.113883.4.635
- fhir.infoway-inforoute.ca/NamingSystem/ca-indigenous-northern-affairs-number

• Suggest changing type to: TN – Treaty Number

Canada Interim Federal Health Program identifier (by Immigration, Refugees and Citizenship Canada)
- urn:oid:2.16.840.1.113883.4.577
- fhir.infoway-inforoute.ca/NamingSystem/ca-interim-federal-ircc-health-id

• Suggest changing type to: JHN – Jurisdictional Health Number

Canada Permanent Resident Card Number
- fhir.infoway-inforoute.ca/NamingSystem/ca-permanent-resident-card-number

• Suggest changing type to: PRC – Permanent Resident Card

Canada, Social Insurance Number (SIN)
- urn:oid:2.16.840.1.113883.4.272
- fhir.infoway-inforoute.ca/NamingSystem/ca-social-insurance-number

• Suggest changing type to: SB – Social Beneficiary Identifier

We have yet to hear from anyone in the community that is actively using the JPID type concept - we're going to keep the thread open this week to allow any implementers who are using JPID to provide feedback - before we make the decision to remove the request from the UTG tickets. Particularly - we want to be sure we've heard from folks who represent the client/patient registry perspective and any vendors using identifier type to aid patient matching/record lookup.

We discussed the CA Baseline's removal of a slice representing JPID concept, on our Governance call last Friday. Our original intent was to use slicing to model the various identifiers and identifier types we saw being used in the Canadian URI Registry and where appropriate apply extensions and constraints that would support the use of the field.

We didn't have any users on the call that were actively using the JPID identifier type to facilitate any specific use cases. The group agreed in removal of the JPID (and PPN) slices but to maintain the slice on JHN identifier type since it is currently the mechanism in which we socialize the identifierversion extension that was built for jurisdictional health number version codes.We'll be making the change in the CA Baseline shortly and will be reaching out to implementers we believe may be impacted by this change to the CA Baseline Patient profile.

Concurrently, the community is requesting for a correction to the Canadian URI registry to correct the current naming systems using this type to prevent further confusion in the future. This is an activity that will need to be tackled separate from the CA Baseline and will be a request issued to the team in charge of the Canadian URI Registry product.

I am in support of pushing back to not have this new identifier needed, as Lloyd indicated I feel that this is already possible with the current structure.

Anibal, for the RAMQ identifier.system you can use fhir.infoway-inforoute.ca/NamingSystem/ca-qc-patient-healthcare-id
- its NamingSystem is defined at simplifier.net/CanadianURIRegistry/ca-qc-patient-healthcare-id/~json.

And as Lloyd has mentioned, identifier.type.coding.code will be "JHN".

Sure. Identifiers aren't distinguished by type, they're distinguished by system. So the combination of Identifer.value and Identifier.system must be unique. But it's fine for there to be may identifiers that share the same type. E.g. if type is MRN (medical record number), there could be repetitions with the medical record number of 3 or 4 organizations.

Is it possible to have more than one JHN in a resource and if so, how would they be differentiated?

I think the case in New Brunswick is that they have both a Health Card Number and a MyHealthNB number.