RESUMEN
As newborn screening programs transition from paper-based data exchange toward automated, electronic methods, significant data exchange challenges must be overcome. This article outlines a data model that maps newborn screening data elements associated with patient demographic information, birthing facilities, laboratories, result reporting, and follow-up care to the LOINC, SNOMED CT, ICD-10-CM, and HL7 healthcare standards. The described framework lays the foundation for the implementation of standardized electronic data exchange across newborn screening programs, leading to greater data interoperability. The use of this model can accelerate the implementation of electronic data exchange between healthcare providers and newborn screening programs, which would ultimately improve health outcomes for all newborns and standardize data exchange across programs.
RESUMEN
BACKGROUND: U.S. poison control centers pose a special case for patient identity matching because they collect only minimal patient identifying information. METHODS: In early 2017, the Utah Poison Control Center (Utah PCC) initiated participation in regional health information exchange by sending Health Level Seven Consolidated Clinical Document Architecture (C-CDA) documents to the Utah Health Information Network and Intermountain Healthcare. To increase the documentation of patient identifiers by the Utah PCC, we (1) adapted documentation practices to enable more complete and consistent documentation, and (2) implemented staff training to improve collection of identifiers. RESULTS: Compared with the same time period in 2016, the Utah PCC showed an increase of 27% (p < 0.001) in collection of birth date for cases referred to a health care facility, while improvements in the collection of other identifiers ranged from 0 to 8%. Automated patient identity matching was successful for 77% (100 of 130) of the C-CDAs. CONCLUSION: Historical processes and procedures for matching patient identities require adaptation or added functionality to adequately support the PCC use case.