HIM 650 Topic 4 conversion crosswalk decision record example

Health Care Data Management Grand Canyon University Free custom sample in 24 to 48h

This HIM 650 Topic 4 sample paper is a conversion crosswalk decision record for a 62-clinician multispecialty group moving fifteen years of data into its acquiring network's EHR. It belongs to GCU HIM 650, Health Care Data Management, the course listed as HIM-650 in the Grand Canyon University MS in Health Informatics. Of 214 source fields, 208 map and are summarized; six do not. Free-text allergies are coded only on exact matches, a glucose code covering fasting and random tests maps without guessing fasting status, and inexact problem maps keep their relationship. Telehealth visits, smoking comments and untyped scanned records each get a decision, a stated loss and a visible conversion label for clinicians.

CourseHIM 650 Health Care Data Management
TopicTopic 4
Paper typeConversion crosswalk decision record
LengthAbout 970 words, 3 pages
FormatAPA 7 student paper
SchoolGrand Canyon University (GCU)
ProgramMS in Health Informatics
UpdatedSeptember 2026

Free sample paper for HIM 650 Topic 4

1

Six Fields That Would Not Map: A Conversion Crosswalk Decision Record for Rincon Valley Multispecialty Group's Move Into the Arroyo Seco EHR

[Author Name]

College of Nursing and Health Care Professions, Grand Canyon University

HIM-650: Health Care Data Management

Topic 4 Assignment

[Instructor Name]

[Date]

The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.

What this page is doingThe title puts the unmapped rows first, since the mapped ones need only a line and the decisions sit in the failures. The group, systems and counts are composites; the sources are real.
2

Six Fields That Would Not Map: A Conversion Crosswalk Decision Record for Rincon Valley Multispecialty Group's Move Into the Arroyo Seco EHR

Scope and the Rows That Mapped

Rincon Valley Multispecialty Group, 62 clinicians acquired by Arroyo Seco Health last year, is converting fifteen years of data from its legacy ambulatory system into the network's enterprise electronic health record. The crosswalk covers 214 source fields. Of these, 191 map directly to a target field with the same meaning, and 17 map after simple transformations such as date formats or unit conversions. Those 208 rows are summarized in an appendix. The six below do not map cleanly, and each carries a decision that changes what a clinician will see. This record states, for each, the options considered, the one chosen, what is lost and how the loss is shown in the chart.

A conversion that reports a mapping rate and stops, 97% in this case, implies that every mapped row kept its meaning. The six rows below show why that implication is dangerous.

Allergies Typed as Free Text

The legacy system stored allergies as free text: "PCN rash," "sulfa," "shellfish/iodine," "codeine makes her sick." There are 14,200 entries for about 9,800 patients. Drug allergies are common in any large record; in one health system's data, 35.5% of patients had at least one recorded drug allergy (Zhou et al., 2016). The target requires a coded allergen and a coded reaction, because only coded allergies trigger drug interaction checking. Goss et al. (2013) found that no single terminology covers every kind of allergen well, with RxNorm strongest for drugs and other terminologies stronger for foods and environmental substances.

Options: code everything automatically with text matching; code exact matches and convert the rest as flagged text; or leave allergies in the archive. Automated coding of all entries was rejected because it is the option most likely to put a wrong allergen in front of a prescriber: "sulfa" could mean sulfonamide antibiotics or be misread as sulfites. The decision: 9,900 entries that match an RxNorm ingredient or class exactly are coded, with the original text kept in the comment; the other 4,300 convert as uncoded entries labeled "legacy allergy, not yet coded." What is lost: interaction checking does not fire on uncoded entries until a clinician reconciles them. To compensate, the chart shows a banner when a patient has uncoded legacy allergies, and pharmacists review them before the first medication order.

One Laboratory Code for Two Tests

The legacy system used a single local code, GLU, for both fasting and random glucose. The target has separate codes. Cimino (1998) listed concept orientation, one concept per code, as a basic requirement of a controlled vocabulary, and this local code violated it. One proposed fix was to infer fasting status from the time of the draw, treating morning results as fasting. That was rejected because it manufactures a fact the source never held; many morning draws are not fasting. The decision: map all GLU results to the target's glucose code that makes no claim about fasting, with a note stating that fasting status was not recorded. What is lost: trend views of fasting glucose will not include legacy results, and clinicians must read the note.

Problem Entries With Inexact Maps

The legacy problem list used local codes that map to target concepts that are broader, narrower or roughly equivalent, rarely exact. "DM2 uncontrolled" maps to a broader concept of type 2 diabetes; "back pain, mechanical" maps to back pain. The decision: convert each entry to its closest target concept, keep the source text visible beside it and record the map relationship, broader, narrower or equivalent, in the conversion table. Without the relationship, the next reader cannot tell whether a converted entry means exactly what the old one did. Broader maps also lose detail that matters for care: "uncontrolled" does not survive the move to a general diabetes concept, so the source text is the only place a clinician will see it.

Visits Without a Setting, Smoking in a Comment, Documents Without a Type

Visit records did not distinguish telehealth from in-person care. For visits since 2020, billing records carry telehealth modifiers, a fact the source did record; those visits are marked accordingly. Earlier visits convert with the setting marked unspecified rather than assumed in person.

Smoking history sat in a free-text comment field. Converting it to a structured status with text matching would assign current, former or never to comments such as "quit, restarted, cutting down." The decision: convert comments as a dated text note, leave the structured status blank and prompt staff to record it at the next visit.

About 38,000 scanned outside records carry no document type. Classifying them all by hand would take an estimated 1,900 staff hours. The decision: convert all with the generic type "outside record," indexed by date and source where recorded, and have HIM staff classify the documents of patients seen in the past two years, about 11,000, before go-live. The rest are classified on request.

What this page is doingEach decision refuses to invent a fact the source did not hold, and each says what is lost as a result.
3

How Losses Are Shown to Clinicians

A decision record that documents losses only for the project team hides them from the people who inherit them. Every converted item in the new chart carries a label stating that it was converted from the legacy system and the conversion date, and a link shows the original source text. Uncoded allergies carry the banner described above. A one-page guide to what converted data does and does not mean is part of go-live training for every Rincon Valley clinician and for Arroyo Seco clinicians who will see Rincon Valley patients. The legacy system will remain available read-only for six months after go-live, and any clinician who finds a converted item misleading can report it through a dedicated queue that the conversion team reviews weekly.

References

Cimino, J. J. (1998). Desiderata for controlled medical vocabularies in the twenty-first century. Methods of Information in Medicine, 37(4-5), 394-403. https://doi.org/10.1055/s-0038-1634558

Goss, F. R., Zhou, L., Plasek, J. M., Broverman, C., Robinson, G., Middleton, B., & Rocha, R. A. (2013). Evaluating standard terminologies for encoding allergy information. Journal of the American Medical Informatics Association, 20(5), 969-979. https://doi.org/10.1136/amiajnl-2012-000816

Zhou, L., Dhopeshwarkar, N., Blumenthal, K. G., Goss, F., Topaz, M., Slight, S. P., & Bates, D. W. (2016). Drug allergies documented in electronic health records of a large healthcare system. Allergy, 71(9), 1305-1313. https://doi.org/10.1111/all.12881

HIM 650 Topic 4 instructions, in plain terms

The Topic 4 instructions in HIM-650 ask students to document decisions made when data is converted between systems. Weak submissions report a mapping rate. The assignment rewards records that summarize the rows that map cleanly and focus on those that do not, stating for each the options considered, the option chosen and what a clinician loses. Students should avoid inventing facts the source never held, record map relationships such as broader or narrower, weigh the safety risk of automated coding for clinical data like allergies and describe how converted data will be labeled for the clinicians who inherit it.

Inside the HIM 650 Topic 4 example

The finished record is a crosswalk with a decision under every row that failed to map. A composite multispecialty group is converting its legacy ambulatory system into the enterprise EHR of its acquiring hospital system. Most fields map cleanly and are summarized in a line. Six are not. Allergies were typed as free text, while the target wants a coded allergen and reaction. One local laboratory code held both fasting and random glucose results. Problem entries carry local codes that map to broader or narrower concepts, rarely exact ones. Visit records do not distinguish telehealth from in-person care. Smoking history sits in a comment field, and scanned outside records carry no document type. For each, the record names the options, the one chosen, what a clinician loses and where the conversion note appears in the chart.

Where the marks sit in the HIM 650 Topic 4 rubric

Faculty grading the crosswalk record reward decisions that refuse to invent. Excellent records reject inferring fasting status from draw time and code allergies automatically only where the match is exact. Credit goes to recording map relationships and keeping source text visible where detail is lost. The rubric values compensating controls, such as a banner for uncoded allergies and pharmacist review before the first order. The highest level shows clinicians how converted data is labeled and gives them a way to report misleading items. Records that stop at a mapping percentage usually land in a middle band.

HIM 650 Topic 4 help: mistakes that cost marks

The weakest records report a mapping rate and nothing else, as if every mapped row kept its meaning. Automated coding of free-text allergies is often proposed, and it is the option most likely to put a wrong allergen in front of a prescriber. Papers that drop unmappable content to keep the new chart clean lose history nobody can recover once the legacy system is retired. Some examples resolve the glucose problem by guessing fasting status from the time of the draw, which manufactures a fact the source never held. Map relationships left unstated leave the next reader unable to tell a broader concept from an exact one. A record that never says how converted data is shown to clinicians has documented its losses for the project team and hidden them from the people who inherit them.

Get an HIM-650 Topic 4 example written to your instructions

Send the HIM-650 Topic 4 instructions and the rubric from your classroom, with any source and target structures or mapping tables provided. We write a custom example to those criteria, with every unclean map documented, the choice between losing and inventing detail argued row by row and converted data made visible to clinicians, in 24 to 48 hours. The first one is free.

More HIM 650 papers and MS in Health Informatics samples

HIM 650 Topic 4 questions, answered

Why not let the conversion tool code free-text allergies?

Because a wrong code is worse than an honest note. Matching allergy text to a coded allergen by string or language model may get most entries right and some confidently wrong, and a coded entry looks verified to the prescriber who reads it. Carrying the text across as unverified, with reconciliation at the next visit, keeps the information and its uncertainty together. Exact matches can still be coded if flagged.

What is a map relationship?

A label stating how closely a source code matches its target. Terminology mapping work, including HL7 FHIR's ConceptMap resource, distinguishes maps that are equivalent from those where the target is broader, narrower or only loosely related. Recording the relationship tells a later reader whether a converted problem entry means exactly what the clinician originally recorded or something close to it, which matters for decision support and reporting.

Should everything in the legacy system be migrated?

Not necessarily. Many migrations bring forward active and recent clinical data in discrete form and leave older history in an archive that stays readable for the retention period. The decision record covers what is converted; a later topic in many sections handles what stays behind. The assignment may fix that scope, and the record should state it at the top so each row's decision is read against it.

Where can I find a free HIM 650 Topic 4 sample paper?

This page gives the complete record: scope and mapped rows, free-text allergies, one lab code for two tests, inexact problem maps, visits, smoking and documents, and how losses are shown. Send your conversion for a free worked record.

Why not code every allergy automatically in HIM 650 Topic 4?

Text matching could put a wrong allergen in front of a prescriber, such as reading sulfa as sulfites, so only exact matches are coded and the rest are flagged for clinician review.