{'fraction_non_alphanumeric': 0.01627906976744186, 'fraction_numerical': 0.0, 'mean_word_length': 5.194244604316546, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
What mapping and modeling means to the HIM professional.

The processes of data mapping and concept modeling are required to help meet the goal of interoperability for an electronic health record (EHR). Interoperability, as defined by the Institute of Electrical and Electronics Engineers, is “the ability of two or more systems or components to exchange information and to use the information that has been exchanged.” This paper explains how these processes contribute to the exchange of information between multiple health information systems. In it, I will discuss the differences and similarities between data mapping and coding for reimbursement. The effect upon HIM professionals will be profound as their job functions either shift to performing data mapping and concept modeling, or as they see the results of these processes upon their current roles.