Type | Standard / Implementation Specification | Standards Process Maturity | Implementation Maturity | Adoption Level | Federally required | Cost | Test Tool Availability |
---|---|---|---|---|---|---|---|
Operating Rules
|
Final
|
Feedback requested
|
Feedback Requested |
No
|
Free
|
No
|
|
Standard
|
Final
|
Pilot
|
![]() |
No
|
Free
|
No
|
Limitations, Dependencies, and Preconditions for Consideration | Applicable Value Set(s) and Starter Set(s) |
---|---|
|
|
Comment
Submitted by Amanda Rodriguez on
AHIMA Patient Naming Policy
I support AHIMA's Patient Naming Policy to improve patient safety, reduce the risk of patient identity errors, efficiently share health data across systems, and reduce the costs associated with patient identity errors.
Submitted by mceraso on
Patient Naming Policy
I support AHIMA’s Patient Naming Policy to improve patient safety.
Submitted by Djordjevic on
Patient Naming Policy
I support AHIMA’s Patient Naming Policy to decrease the financial burden of duplicate tests that are ordered when patient records cannot be assimilated.
Submitted by tmulvenn1 on
Patient Name Requirements
I support adopting the AHIMA Recommended Data Elements for capturing the legal name to improve patient safety, reduce overlays, and ensure interoperability.
Submitted by CTurrietta on
Patient Naming Policy
I support AHIMA’s Patient Naming Policy in support of patient safety. Duplicates, overlaps, and overlays not only create a financial burden due to duplicate tests but can also lead to errors that jeopardize the health and safety of patients. The data elements recommended by AHIMA support consistency and quality data. A patient naming policy with these legal name requirements and quality principles protects everyone.
Submitted by Katherine Lusk on
Capture of Name
I support the adoption of the AHIMA Recommended data elements for capture of individuals names. Consistent use of the legal name and the AHIMA conventions will improve patient safety and interoperability.
Submitted by Katherine Lusk on
Capture of Patient Names
I support the adoption of the AHIMA recommended data elements for capture in the master patient index as a level playing field for all participants in the healthcare ecosystem. The AHIMA policy contains practical guidance for the community including capture of naming conventions for multiple births, in-vitro care diagnosing and care delivery and individuals with one name. The policy can support the capture of individual's names as a patient, insured individual, or clinician receiving a direct secure messaging. The type of standardization via a national policy has broad ranging positive impacts for patient safety and for efficiencies.
Submitted by Beth Juliano on
Patient Name Requirements
I support the adoption of the AHIMA Recommended Data Elements for Capture in the Master Patient Index, specifically use of legal name. Consistent use of legal name would improve patient safety and interoperability.
Submitted by Cole Downs on
Patient Name Requirements
I support AHIMA’s Patient Naming Policy to improve patient safety as well as decreasing the financial burden of duplicate tests that are ordered when patient records cannot be assimilated.