HCIS 318 Week 1 Medical Terminology for Information Technology Example

What the Cardiology Clinic Actually Asked For: Translating a Request to Capture Ejection Fraction Into Technical Requirements Using Medical Terminology and Standard Vocabularies

[Student Name]

University of Phoenix

HCIS/318: Health Care Industry Terms for IT Professionals

Week 1 Assignment

[Instructor Name]

[Date]

The clinic, the request and the build are composites written for a model paper; vocabulary standards come from the sources listed.

The request arrived in the IT ticket system as one line from the cardiology clinic manager: "Need EF captured discretely for HFrEF registry reporting." The analyst assigned to it built a free-text field labeled "EF" on the nursing intake form. A week later the clinic's cardiologist explained that the field was useless. This paper shows what the request meant, why the first build failed and how medical terminology and standard vocabularies turned it into correct technical requirements.

Unpacking the Request

Four terms carried the meaning. EF stands for ejection fraction. Discretely means as a separate data element that a computer can read and count, not as words inside a paragraph. HFrEF stands for heart failure with reduced ejection fraction. Registry reporting means sending data to an external database that tracks the care of patients with a condition. The analyst understood none of these clearly, which is common for IT staff without clinical training and exactly why this course exists.

The Clinical Terms Behind the Request

An echocardiogram is an ultrasound picture of the heart: the prefix echo- means sound, cardi- points to the heart, and -gram marks a recorded image (Ehrlich et al., 2021). From it, a cardiologist measures how well the left ventricle, the heart's main pumping chamber, empties with each beat. Ejection fraction is the percentage of the blood in the left ventricle that is pushed out per beat. A normal value is roughly 50% to 70%. Heart failure with reduced ejection fraction generally means a value of 40% or lower, and patients in this group receive specific medications that improve survival, which is why the clinic tracks them.

Why the First Build Failed

A free-text field on a nursing form failed in three ways. Nurses do not measure ejection fraction; cardiologists read it from the echocardiogram, so the field was in the wrong place. Free text allowed entries such as "EF 35," "35 percent" or "reduced," which a report cannot count reliably. And the field had no date, although ejection fraction changes over time and the registry needs the most recent value with its date.

Why Structured Data Matter

Structured data are stored as defined elements with set formats, units and codes. A structured ejection fraction is a number between 0 and 100, with a unit of percent, a date and a source, such as the echocardiogram report. With structure, the system can find every patient with a value of 40% or lower, remind clinicians about recommended medications and send the value to the registry automatically.

Mapping to Standard Vocabularies

For data to mean the same thing across systems, they must be coded with standard vocabularies. LOINC provides universal identifiers for laboratory tests and clinical measurements, so an ejection fraction measured by echocardiogram carries a code that any receiving system recognizes (Regenstrief Institute, n.d.). SNOMED CT, which the National Library of Medicine distributes in the United States, is a comprehensive clinical terminology used to record findings and conditions in the health record, such as the concept of heart failure with reduced ejection fraction (National Library of Medicine, n.d.). ICD-10-CM codes classify diagnoses for billing and statistics; heart failure codes specify the type, such as systolic heart failure, and whether it is acute or chronic.

Using the right vocabulary for each element is what lets the registry, the billing system and another hospital's record all read the same value the same way, without a person retyping or interpreting it.

The Requirements, Written Twice

The analyst rewrote the requirements in two columns, clinical and technical. Clinically: capture the most recent left ventricular ejection fraction from each echocardiogram, with its date and the reading cardiologist. Technically: create a numeric observation field, 0 to 100, unit percent, populated from the structured echocardiogram report through the cardiology system interface, coded with the appropriate LOINC measurement code, stored with the result date. Clinically: find every patient whose heart failure involves a reduced ejection fraction. Technically: flag patients whose problem list includes a SNOMED CT heart failure concept and whose latest ejection fraction is 40 or lower. Clinically: send quarterly data to the registry. Technically: build an extract in the registry's required format.

Abbreviations as a Hazard

The ticket's abbreviations were not unusual. Clinical staff use hundreds of them, and many have more than one meaning: MS can mean multiple sclerosis or morphine sulfate, and PT can mean physical therapy, patient or prothrombin time. IT staff who guess at an abbreviation can build a field, report or alert around the wrong concept. The team's rule is now simple: every abbreviation in a request is spelled out and confirmed with the requester before design begins, and screens shown to users avoid ambiguous abbreviations altogether.

Units, Ranges and Validation

Numbers in health care carry units and plausible ranges. An ejection fraction of 350 is an error, and so is one entered as 0.35 when the field expects a percentage. The rebuilt field rejects values outside 0 to 100 and displays the unit beside the box. Validation rules like these are a technical task, but writing them requires knowing what the clinical value means.

Checking With the Clinic

Before building again, the analyst reviewed the two-column requirements with the cardiologist and the clinic manager, who corrected one detail: the value should come from the most recent echocardiogram, not the most recent cardiology visit.

A Glossary Habit

The IT team now keeps a shared glossary. Every unfamiliar clinical term in a ticket gets an entry with its word parts, a plain definition, an example value and the code system it maps to, reviewed by a clinical informatics nurse. After a year the glossary holds several hundred terms and new analysts read it during orientation.

What the Case Teaches IT Professionals

Clinicians write requests in their own language, full of abbreviations. An IT professional who can decode the terms, ask what the data will be used for and map each element to a standard vocabulary builds the right thing the first time.

Conclusion

One line of clinical shorthand hid a clear requirement. Medical terminology revealed what the clinic needed, structured data made it usable and standard vocabularies made it shareable. The failed first build cost a week; the terminology lesson will save many more.

References

Ehrlich, A., Schroeder, C. L., Ehrlich, L., & Schroeder, K. A. (2021). Medical terminology for health professions (9th ed.). Cengage Learning.

National Library of Medicine. (n.d.). SNOMED CT. U.S. National Library of Medicine. https://www.nlm.nih.gov/healthit/snomedct/index.html

Regenstrief Institute. (n.d.). About LOINC. https://loinc.org/about/