| Course | HIM 370 Health Care Information Systems |
|---|---|
| Topic | Topic 5 |
| Paper type | Discussion post |
| Length | About 430 words, 2 pages |
| Format | Discussion post, APA 7 citations |
| School | Grand Canyon University (GCU) |
| Program | BS in Health Information Management |
| Updated | September 2026 |
Free sample paper for HIM 370 Topic 5
Topic 5 DQ 1: Initial Post
Configuration Can Change What Gets Stored Tomorrow, Not What Was Stored Yesterday: A Problem List Report Request
Initial Post
My position: configuration changes what an EHR stores going forward. It cannot change what the system has already stored, and a request that depends on old data must be answered with a different tool or a different start date.
The request: Bajada Community Hospital's quality team wants a report of every active patient's problem list entries by condition, to find patients with heart failure, diabetes and chronic kidney disease for outreach. The difficulty is that for eight years the EHR allowed problem list entries as free text, and about 60% of current entries are typed phrases such as "CHF EF 35%," "sugar problems" and "kidneys stage 3?" rather than coded concepts.
What configuration can do: our analysts can switch the problem list to require selection of a coded concept from the terminology, with free text allowed only as an annotation. They can add a prompt at the end of each visit to review the list. They can build a report that counts coded entries by condition. All of this is ordinary configuration, and from the day it goes live, new entries will be reportable. Wright et al. (2015), studying problem list completeness at ten organizations, found wide variation, from about 60% to over 99% of patients with diabetes having it on their problem list, and identified factors such as shared responsibility, gap reporting and links to billing codes at the best-performing sites, which suggests configuration and workflow together can improve new data substantially.
What configuration cannot do: nothing in the configuration screens will turn eight years of typed phrases into coded concepts reliably. "Sugar problems" might mean diabetes, prediabetes or hypoglycemia. Converting old entries requires a project, not a setting: manual review by clinicians or coders, or natural language processing with validation. Kreimeyer et al. (2017), reviewing natural language processing systems for standardizing unstructured clinical information, found them promising but varied in performance and dependent on the task and the text, which is why any automated conversion would need a sample checked by a person before the quality team relies on it.
My recommendation to the team: configure coded entry now, run the report on coded entries from a stated start date, and supplement it for the three target conditions with diagnosis codes from claims, which are coded, while deciding whether a conversion project is worth funding.
Question for the group: has anyone seen a conversion of free-text problem lists that was validated? What share did a person have to fix?
References
Kreimeyer, K., Foster, M., Pandey, A., Arya, N., Halford, G., Jones, S. F., Forshee, R., Walderhaug, M., & Botsis, T. (2017). Natural language processing systems for capturing and standardizing unstructured clinical information: A systematic review. Journal of Biomedical Informatics, 73, 14-29. https://doi.org/10.1016/j.jbi.2017.07.012
Wright, A., McCoy, A. B., Hickman, T.-T. T., Hilaire, D. S., Borbolla, D., Bowes, W. A., III, Dixon, W. G., Dorr, D. A., Krall, M., Malholtra, S., Bates, D. W., & Sittig, D. F. (2015). Problem list completeness in electronic health records: A multi-site study and assessment of success factors. International Journal of Medical Informatics, 84(10), 784-790. https://doi.org/10.1016/j.ijmedinf.2015.06.011
HIM 370 Topic 5 instructions, in plain terms
The Topic 5 discussion in HIM-370 asks students to explain the limits of what an information system can do through configuration. Strong initial posts commit to one claim about what settings can and cannot do, then try it against a request a real department might send. Strong posts distinguish configuration, meaning settings, templates and report tools, from projects that require new data work, and show which parts of a request each can meet. Students should explain why stored free text cannot simply be converted by a setting, describe options such as manual abstraction or validated language processing, offer a practical way to answer the request and end with a question classmates can answer from experience.
How the HIM-370 Topic 5 example is put together
A single discussion post carries a position, a composite request and a question for classmates. The request comes from a composite quality team that wants problem list entries reported by condition, in a hospital whose EHR has stored those entries largely as free text. The post argues that configuration can add a coded field going forward, change the entry screen and build a report on whatever is coded, while nothing configurable can turn years of stored free text into coded data. It then names a middle path, a customization or a mapping project, with its cost in maintenance at every upgrade. The response closes by asking classmates for a request from their own setting that looked like configuration and turned out to need something larger.
Reading the HIM 370 Topic 5 rubric
GCU faculty grading this discussion reward a limit stated precisely and an answer offered anyway. Excellent posts show exactly what configuration changes going forward and why it cannot reach historical free text. Credit goes to supporting the argument with research on problem list completeness and on language processing performance. The rubric values a practical recommendation, such as a start date and supplementary coded sources, instead of stopping at the limit. The highest level invites classmates to share evidence from validated conversions, which moves the discussion from opinion to experience.
HIM 370 Topic 5 help: mistakes that cost marks
Posts that answer with a list of features the system lacks miss the question, which is about the boundary and why it sits where it does. Treating every limit as a configuration problem promises the quality team something the stored data cannot deliver. The opposite answer, that nothing new is possible without replacement, ignores how much a well-configured product can change going forward. Several responses call customization the solution and never mention the maintenance it creates at each upgrade, which is the reason many organizations avoid it. Examples framed in the abstract, with no composite request, give classmates nothing to test the argument against. A reply that closes on a summary instead of a question leaves the discussion with no invitation to continue, and in many sections the follow-up replies are where participation is judged.
Get an HIM-370 Topic 5 example written to your instructions
Send the HIM-370 Topic 5 discussion question as it appears in your classroom, together with the participation rubric and any source requirement your instructor set. We write a custom example to those criteria, with the position stated first, a composite request sorted into configuration, customization and replacement, and a closing question, in 24 to 48 hours. The first one is free.
More HIM 370 papers and BS in Health Information Management samples
- HIM 370 Topic 1: System Type Inventory
- HIM 370 Topic 2: Data Element Trace
- HIM 370 Topic 3: Interface Failure Analysis
- HIM 370 Topic 4: Duplicate Record Impact Analysis
- HIM 370 Topic 6: Weighted Requirements Matrix
- HIM 370 Topic 7: Data Migration Plan
- HIM 370 Topic 8: Installed System Evaluation
- HIM 355 Topic 5: Separate Reportability Discussion
- HIM 350 Topic 5: Physician Query Discussion
- HIM 310 Topic 5: Granularity Trade Off Discussion
- HIM 200 Topic 5: Defensible Entry Discussion
HIM 370 Topic 5 questions, answered
What counts as configuration rather than customization?
Configuration uses the settings, rules, templates and report tools the vendor supports, and it survives upgrades because the vendor tests against it. Customization changes or extends the product beyond those tools, through custom code, local database changes or bespoke interfaces, and the organization then owns the work of retesting it with every release. The line varies by product, which is why the post defines both terms before sorting the composite request.
Can old free-text data ever be converted?
Partly, through a mapping or abstraction project that reads the stored text and assigns codes, either by people or with software assistance followed by human review. It is a project with its own cost and its own error rate, not a setting that can be switched on. The post names it as the middle path so the quality team can weigh it, rather than implying the system could do it on request.
Does the post need a source?
Where a source is required, the assigned readings on system architecture and implementation are the natural place to start, cited for the distinction between configuring and customizing a product. A vendor's marketing material is a weak source for what a system cannot do. Name the source for the claim it supports, and keep the composite request clearly marked as an illustration rather than a real organization.
Where can I find a free HIM 370 Topic 5 sample paper?
This page has the complete post, with the position, the request, what configuration can and cannot do, the recommendation and the question to classmates. Ask for a free model post built on your own system request.
Why can't configuration fix old entries in HIM 370 Topic 5?
Typed phrases like sugar problems could mean several conditions, so turning them into codes requires someone, or a validated language processing tool, to interpret each one. No setting can do that reliably.