Stream: implementers
Topic: Medicaid Identifier Type
Kimberly Kenna (Feb 17 2021 at 14:52):
Is there a precedent set for what the type should be set to for a Practitioner / Provider Organization Medicaid Identifier?
Lloyd McKenzie (Feb 17 2021 at 14:54):
@Eric Haas @Brett Marquard
Eric Haas (Feb 17 2021 at 16:03):
US Core is silent on Patient.identifier.type. It requires both a value and a system.
Eric Haas (Feb 17 2021 at 16:04):
The system for SSN is ...
Eric Haas (Feb 17 2021 at 16:10):
http://hl7.org/fhir/sid/us-ssn
Eric Haas (Feb 17 2021 at 16:12):
I am curious what is the value that type adds to the resource. You know from the system that the identifier is a SSN. ?
Eric Haas (Feb 17 2021 at 16:19):
There have been separate discussions on the United States stream about type.
Eric Haas (Feb 17 2021 at 16:32):
Btw we have added this guidance to the us core patient resource. ...
*The Patient’s Social Security Numbers SHOULD NOT be used as a patient identifier in Patient.identifier.value. There is increasing concern over the use of Social Security Numbers in healthcare due to the risk of identity theft and related issues. Many payers and providers have actively purged them from their systems and filter them out of incoming data.
Lloyd McKenzie (Feb 17 2021 at 21:13):
Type is useful in two contexts:
- if system is omitted, type gives at least some clue what's going on and type.label can be a fully descriptive name. E.g. type.code says "provider license number" and type.text says "Michigan state physician license number". Not useful for computational matching, but super useful for displaying something to a human
- if system is present, having the human label is still useful. Seeing system="urn:oid:2.16.840.1.113883.4.3.2" is sufficient for computable matching, but having type.text that says "Alaska Driver's License" is super important for displaying the identifier in the user interface
Richard Townley-O'Neill (Feb 18 2021 at 04:54):
More than one identifier could use the same system, maybe car license and boat license.
Lloyd McKenzie (Feb 18 2021 at 05:01):
The same licensing authority could indeed issue license of different types from the same pool of numbers. The system tells you the namespace. That's not always guaranteed to be enough to tell you the associated credential (if any).
Last updated: Apr 12 2022 at 19:14 UTC
