| Course | HIM 370 Health Care Information Systems |
|---|---|
| Topic | Topic 2 |
| Paper type | Data element trace |
| Length | About 1,000 words, 3 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | BS in Health Information Management |
| Updated | September 2026 |
Free sample paper for HIM 370 Topic 2
One Potassium Value, Four Systems, Five Handoffs: A Data Element Trace From Order Entry to a Monthly Quality Report
[Author Name]
College of Nursing and Health Care Professions, Grand Canyon University
HIM-370: Health Care Information Systems
Topic 2 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.
One Potassium Value, Four Systems, Five Handoffs: A Data Element Trace From Order Entry to a Monthly Quality Report
Why Trace One Value
Bajada Community Hospital's quality committee reports each month the share of patients receiving intravenous potassium replacement whose serum potassium was rechecked within six hours. Last spring the figure dropped from 91% to 74% in one month with no change in practice, and the committee asked health information management to find out why. The answer lay in how a potassium value travels. This trace follows one composite result for one patient from the moment it was ordered to the moment it was counted, recording at each handoff the identifier used, the timestamps carried and anything that could alter the value's meaning.
The Trace
Table 1
Handoffs of One Potassium Result
| Step | System | Identifier for the test | What is carried | Where meaning can change |
|---|---|---|---|---|
| 1. Order | EHR order entry | Local orderable: basic metabolic panel | Order time, ordering provider, patient and encounter | Panel ordered, not potassium alone |
| 2. Order message | Interface engine to laboratory system | Local order code mapped to laboratory test code | Order message with patient identity and encounter | Wrong encounter if the patient was transferred between messages |
| 3. Result | Laboratory information system | Laboratory test code; LOINC code for serum or plasma potassium | Value 3.1, units mmol/L, reference range 3.5-5.1, flag low, collection time 06:12, result time 06:58 | Hemolysis comment attached as a separate note |
| 4. Result message | Interface engine to EHR | Observation identifier carries local and LOINC codes | Value, units, range, flag and status in their message fields; comment in a note segment | Note segment not displayed with the value in some views |
| 5. Warehouse load | Data warehouse | Mapped to a warehouse concept, potassium | Value, result time, status | Collection time and comments not loaded |
Identifiers at Each Handoff
The test changes names four times. The clinician orders a local panel, the laboratory runs a test with its own internal code, the result message carries both the laboratory's code and a LOINC code in its observation identifier field, and the warehouse maps the result to its own concept. LOINC exists to make the third of these universal, giving each laboratory observation a code that specifies what was measured, in what specimen, by what property and scale (McDonald et al., 2003). The serum or plasma potassium code identifies exactly the test run on this patient. Universal codes help only if systems use them consistently, however. Lin et al. (2012), comparing LOINC use at three large institutions, found that many code pairings were used interoperably but that some pairings carried contradictory knowledge, meaning that the same apparent test was coded differently or different tests were coded the same way.
Where the Meaning Changed
The trace located the quality report's drop in two places. First, the warehouse loaded the result time, 06:58, not the collection time, 06:12. The quality measure asks whether potassium was rechecked within six hours of the replacement dose, and the clinically meaningful time is when the blood was drawn. Using the result time made rechecks look later than they were, by the laboratory's turnaround time, and when a new analyzer lengthened turnaround in the spring, recheck compliance appeared to fall.
Second, the warehouse mapped two LOINC codes to its single potassium concept: the serum or plasma test from the main laboratory and the whole blood potassium measured on the intensive care unit's blood gas analyzer. The two are clinically related but not the same measurement, and the blood gas values arrived with a different result time pattern. When the intensive care unit began using its analyzer for more potassium checks that spring, the mix shifted. The hemolysis comment, which marks a falsely high potassium, was never loaded at all, so the warehouse could not exclude unreliable values.
None of these changes altered the value 3.1. Each altered what the value was taken to mean in the report.
The Handoffs Nobody Owned
The trace also showed why the problem had gone unnoticed. Each handoff belonged to a different team. The laboratory owned the result and its comment and had recorded both correctly. The interface team owned the message and had passed every field through. The EHR team owned the display, where the comment appeared in the full result view but not in the flowsheet most nurses use. The analytics team owned the warehouse load, which had been built years earlier from a specification that listed the fields a potassium report then needed. When the laboratory added the intensive care analyzer and the new main analyzer, no one told analytics, because no one thought of the warehouse as downstream of a laboratory purchase.
Each team could show that its own step was correct, and each was. The error existed only in the chain. That is the reason health information management was the right department to run the trace: its responsibility for the integrity of the record gave it a reason to follow the value across boundaries no single system owner crosses. The department now asks to review any change to laboratory analyzers, codes or interfaces for its effect on warehouse measures.
What the Department Changed
Three fixes followed. The warehouse now loads the collection time and uses it for time-based measures, with the result time kept as a separate field. The warehouse concept for potassium was split into serum or plasma and whole blood, each mapped from its own LOINC code, so that reports state which they use. And result comments are loaded and flagged, so hemolyzed specimens can be excluded from measures where a false value would mislead. With the collection time restored, the recheck rate for the spring month recalculated to 89%.
The broader lesson is that a data element carries its meaning in more than its value: in its identifier, its timestamps, its specimen and its comments. Sittig and Singh (2010) included measurement and monitoring among the dimensions of their sociotechnical model for health information technology, and this trace shows why. A quality measure is a system too, and it inherits every decision made about the data before it.
References
Lin, M.-C., Vreeman, D. J., McDonald, C. J., & Huff, S. M. (2012). Auditing consistency and usefulness of LOINC use among three large institutions: Using version spaces for grouping LOINC codes. Journal of Biomedical Informatics, 45(4), 658-666. https://doi.org/10.1016/j.jbi.2012.01.008
McDonald, C. J., Huff, S. M., Suico, J. G., Hill, G., Leavelle, D., Aller, R., Forrey, A., Mercer, K., DeMoor, G., Hook, J., Williams, W., Case, J., & Maloney, P. (2003). LOINC, a universal standard for identifying laboratory observations: A 5-year update. Clinical Chemistry, 49(4), 624-633. https://doi.org/10.1373/49.4.624
Sittig, D. F., & Singh, H. (2010). A new sociotechnical model for studying health information technology in complex adaptive healthcare systems. Quality and Safety in Health Care, 19(Suppl. 3), i68-i74. https://doi.org/10.1136/qshc.2010.042085
The HIM-370 Topic 2 assignment instructions
The Topic 2 instructions in HIM-370 ask students to trace a data element through the information systems that create, transmit and use it. Weak traces describe systems in general or draw a simple flow diagram. The assignment rewards traces that follow one concrete value from its origin to its final use, recording at each handoff the identifier used, the timestamps carried and anything that could change the value's meaning, such as units, specimen type or attached comments. Students should explain the role of standard codes such as LOINC, identify where meaning actually changed and describe the fixes and who owns each handoff.
Inside the HIM 370 Topic 2 example
The finished trace follows a composite potassium result from end to end. It starts at order entry, where the test is requested with a local order code, moves into the laboratory information system, where the specimen is received, run and resulted, and then returns to the EHR as a result message carrying the value, its units and a reference range. From there it is picked up by a data warehouse feed that builds a monthly quality report. At every handoff the trace records which system sends, which system receives, what identifier travels with the value and whether the code is local or standard. The break is found at the warehouse step: the result arrived coded locally, the report expected LOINC, and the values were excluded from the count without any error being raised.
Where the marks sit in the HIM 370 Topic 2 rubric
Faculty grading the data element trace reward precision at each handoff. Excellent traces record identifiers, timestamps, units and comments as the value moves, and show where standard codes are and are not used consistently. Credit goes to finding a real change in meaning, such as a timestamp substitution or merged specimen types, rather than asserting that errors are possible. The rubric values connecting the trace to a measurable consequence and to fixes assigned by owner. The highest level explains why errors that exist only between systems go unnoticed and names who should watch the chain.
HIM 370 Topic 2 help before you submit
Traces drawn as a single arrow from one system to another lose the most, since the topic is about the handoffs and an arrow hides every one of them. A diagram of the whole hospital's data flow can look thorough and still never follow one value far enough to find a problem. Drafts often stop when the result reaches the clinician's screen, which misses the downstream uses where coding and mapping matter most. Papers that record the value but not the identifier traveling with it cannot show whether the result stayed attached to the right patient. Some examples find a break and blame the users, when the element degraded because of a mapping no user ever saw. A trace that names the break without naming the system that owns the fix leaves the finding with nowhere to go.
Get an HIM-370 Topic 2 example written to your instructions
Send the HIM-370 Topic 2 instructions, the rubric posted in your classroom and any data element or scenario your instructor assigned. We write a custom example to those criteria, with the element followed hop by hop, the identifier and coding recorded at each boundary and the point of degradation assigned to a system, in 24 to 48 hours. The first one costs nothing.
More HIM 370 papers and BS in Health Information Management samples
- HIM 370 Topic 1: System Type Inventory
- HIM 370 Topic 3: Interface Failure Analysis
- HIM 370 Topic 4: Duplicate Record Impact Analysis
- HIM 370 Topic 5: System Limits Dq Post
- HIM 370 Topic 6: Weighted Requirements Matrix
- HIM 370 Topic 7: Data Migration Plan
- HIM 370 Topic 8: Installed System Evaluation
- HIM 355 Topic 2: Operative Report Abstraction
- HIM 350 Topic 2: Index to Tabular Verification
- HIM 310 Topic 2: Diagnosis Hierarchy Analysis
- HIM 200 Topic 2: Legal Record Boundary Memo
HIM 370 Topic 2 questions, answered
Which data element makes the best trace?
One that crosses several systems and is used for different purposes in each. A laboratory result, an allergy or a discharge disposition all work, because each is created in one place and consumed in others. A field that lives entirely inside one system, such as a nursing note, shows little. The trace picks the element first and the systems second, so the path is dictated by the data rather than chosen for convenience.
What does LOINC have to do with this?
LOINC provides standard identifiers for laboratory tests and observations, so two systems can agree that a result means the same test. Many laboratories still use local codes internally and map them to LOINC for exchange or reporting. Where that mapping is missing or wrong, a result can display correctly on screen yet remain unseen by any report expecting the standard code, which is the break this composite trace finds.
Is a data flow diagram required as well?
Many classrooms request one as well, and it can sit beside the trace as an overview. The diagram shows which systems connect; the trace shows what happens to one value on each connection. Where both are required, the diagram belongs near the start and the hop-by-hop record carries the analysis. A diagram alone rarely locates a failure, because it draws the connections without testing what crosses them.
Where can I find a free HIM 370 Topic 2 sample paper?
The complete trace is on this page, with why trace one value, the handoff table, identifiers at each step, where the meaning changed, the handoffs nobody owned and what the department changed. Request a free worked trace for your data element.
Why did the recheck rate fall in HIM 370 Topic 2?
The warehouse timed rechecks from result time rather than collection time, so a slower new analyzer made rechecks look late. With collection time restored, the month recalculated from 74 to 89 percent.