Submitted by nedragarrett_CDC on
CDC's Comment for draft USCDI v5
CDC supports the inclusion of this data element in USCDI v5 as it is an element that may be necessary for calculation of our digital quality metrics from FHIR data.
Data used to categorize individuals for identification, records matching, and other purposes.
Data Element |
||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Medical Record Number
Description
The unique identifier assigned by the provider to reference a single patient |
||||||||||||||||||||||||||||||||||||||||||||||||||
|
Submitted by nedragarrett_CDC on
CDC supports the inclusion of this data element in USCDI v5 as it is an element that may be necessary for calculation of our digital quality metrics from FHIR data.
Submitted by nedragarrett_CDC on
Support - LHDs will also be able to use this to attribute encounter level information to a person-level, which is what is used for prevention analysis and program creation.
Having this element and the "identifier" element is going to be confusing for LHDs who will receive this data. There needs to be clarification made between the two and what their use cases are. Right now, they are not very clear in their submissions.
Submitted by nedragarrett_CDC on
Submitted by nedragarrett_CDC on
CSTE agrees with CDC's recommendation for this data element.
Submitted by nedragarrett_CDC on
CDC continues to recommend inclusion of this high priority data element in USCDI v4
Submitted by nedragarrett_CDC on
Medical record number (Level 2); CSTE strongly recommends that medical record number be moved into USCDI v3. This element is critical to include in eCR and ELR and is used heavily for person matching and deduplication as well as when requesting additional clinical information on a case of reportable disease.
Submitted by nedragarrett_CDC on
Submitted by maria.michaels… on
MedMorph supports the addition of Medical Record Number, but is concerned with having a general Identifier element (level 2) as well as Medicare Patient Identifier (level 2), and Patient Social Security Number (level 1). What is the intention of Identifier - is it a placeholder for a national identifier of some sort for a patient? We recommend that USCDI either take a general approach with Identifier Type, Identifier System, and Identifier Value OR be specific with Medical Record Number, Medicare Patient Identifier and Social Security Number elements (and remove the Identifier element).
Submitted by nedragarrett_CDC on
We've reviewed and submitted comments in regards to the submission for Patient Medical Record Number and stand to see that we have slightly differing data element submissions, though this was the previous submission marked as it's duplicate. We recommend re-visiting our submission and comparing it to the above submission seen here.
Submitted by BLampkins_CSTE on
CSTE Comment - v5
CSTE requests the inclusion of medical record number, which is a very important data element for public health, in USCDI v5 in one of two ways. The preference would be to include it in the Patient Identifier data element, with the associated metadata elements required - which would be Type of patient identifier AND Assigning authority for patient identifier. Transmission of this information to public health in both case and laboratory reports is important for the following reasons:
1. It is incredibly helpful for person deduplication which currently requires a huge amount of manual effort at STLT public health agencies to manage the many potential duplicates (even with the best algorithms and automation for patient deduplication, often health department staff spend countless hours deduplicating partially matched patient records).
2. It is critical for identifying patients for follow-up - as in when medical information is sought as part of a case investigation or when additional demographics or contact information are needed in order to quickly reach a patient, or when lab results are needed from a hospital.
3. For any type of automated or semi-automated query of an HIE or another clinical repository (as will hopefully be possible through TEFCA), MR number will be invaluable in narrowing the query and ensuring the returned results pertain to the correct individual - this will save an enormous amount of time and frustration
4. For any bidirectional data exchange it would be invaluable to the receiving health care org to be able to use medical record to route the data to the correct medical record.
CSTE also recommends adding the two additional variables mentioned above to go with the identifier data element - one is the assigning authority (e.g., for a medical record it would be the name of the health care facility using the medical record system) and the other is the type of identifier (e.g., medical record, laboratory patient identifier, SSN, etc.)