HSA4192: Health Informatics

Course Description

HSA4192 Health Informatics is the study of how health information is captured, coded, stored, exchanged and used — the systems that run modern health care, and the legal, ethical and practical problems they create.

The course is offered at approximately four Florida institutions, including Florida International University, Pensacola State College, St. Petersburg College and the University of West Florida.

The University of West Florida titles it Current Topics in Health Informatics, places it in the College of Health, Department of Health Sciences and Administration at 3 semester hours, and describes "an overview of the multifaceted, interdisciplinary nature of health (medical) informatics," covering "fundamentals of computer applications in medicine, health data classification and coding, and legal and ethical issues (including documentation)" in the health record.

⚠⚠ Florida International University runs a materially different course under this number. FIU carries it as Healthcare Quality Management at 3 credits: "development and evaluation of healthcare quality management techniques including work systems, job analysis, space utilization, inventory control, and operations management." That is operations and quality improvement, not informatics. The statewide title is Health Informatics, which matches UWF — so FIU is the outlier here. Details and transfer consequences are in Special Information.

Why health informatics is its own field rather than "IT for hospitals." Health data is unlike other business data in several ways that shape everything about how it is handled. It is legally protected under HIPAA and state law, with specific access, disclosure and breach obligations. It is clinically consequential — a coding error or a badly designed alert can produce patient harm. It is financially load-bearing, because coded diagnoses and procedures drive reimbursement. And it is fragmented across systems that were never designed to talk to each other, which is why interoperability is a permanent problem rather than a solved one.

Classification and coding is the part students least expect and most need. ICD-10-CM/PCS for diagnoses and inpatient procedures, CPT for outpatient procedures, SNOMED CT for clinical terminology, LOINC for laboratory observations and RxNorm for medications. ⚠ These are not filing conveniences: the code determines what the encounter is recorded as having been, what is billed, what appears in the patient's history and what the data says when someone analyses it later. A great deal of what looks like clinical variation in health data is coding variation.

The electronic health record is the course's central object, and the honest treatment includes its failures. Adoption was driven substantially by federal incentive programmes, and the result has been real gains — legibility, availability, decision support, e-prescribing — alongside well-documented costs: documentation burden and its contribution to clinician burnout, alert fatigue, copy-forward errors, and interfaces that optimise for billing capture rather than for clinical work. ⚠ A course that presents the EHR only as progress is teaching badly, and so is one that presents it only as a failure.

Interoperability is the field's defining unsolved problem. HL7 v2 remains widely deployed and is showing its age; FHIR is the modern standard and is genuinely changing what is possible, particularly through APIs; and information blocking rules under the 21st Century Cures Act have made patient access to their own records a legal requirement rather than a courtesy.

⚠ Privacy and security are treated as legal obligations, not as best practice. HIPAA's Privacy and Security Rules, the HITECH breach notification requirements, minimum necessary access, business associate agreements — these carry civil and in some cases criminal penalties, and a health informatics graduate is expected to know them as a working matter.

Florida context. The state's large health systems — AdventHealth, Orlando Health, BayCare, Baptist Health, Tampa General, Jackson Health and the academic centres — run some of the largest EHR deployments in the country, and Florida's health information exchange infrastructure plus the Agency for Health Care Administration's public data reporting make the state a substantial employer in this area.

Learning Outcomes

Required Outcomes

• Define health informatics and distinguish it from health information management, clinical informatics and health information technology.
• Describe the structure and content of the health record and the purposes it serves — clinical, legal, financial, research.
• Explain electronic health record systems — components, workflow, clinical decision support, order entry, and documented benefits and harms.
• Explain health data classification and coding — ICD-10-CM/PCS, CPT, SNOMED CT, LOINC, RxNorm — and what each is for.
• Explain the relationship between coding, documentation and reimbursement, including DRGs and the concept of medical necessity.
• Explain data quality dimensions — accuracy, completeness, timeliness, consistency — and the common sources of error in clinical data.
• Explain interoperability and the principal standards — HL7 v2, FHIR, DICOM, CCD — and why exchange remains difficult.
• Explain health information exchange and patient matching.
• Apply the HIPAA Privacy Rule — protected health information, permitted uses and disclosures, minimum necessary, patient rights of access and amendment.
• Apply the HIPAA Security Rule — administrative, physical and technical safeguards; risk analysis.
• Explain breach notification obligations under HITECH and applicable state law.
• Explain information blocking and patient access requirements under the 21st Century Cures Act.
• Explain legal and ethical issues in documentation — authorship, amendment, copy-forward, the legal health record, and record integrity.
• Explain clinical decision support and evaluate alert design, including alert fatigue.
• Explain terminology and vocabulary standards and the role of mapping between them.
• Explain secondary use of health data — quality measurement, research, public health reporting, registries — and the governance it requires.
• Explain de-identification and re-identification risk.
• Explain system selection and implementation at an introductory level, including workflow analysis, training and change management.
• Explain usability and human factors in clinical systems and their relationship to patient safety.

Optional Outcomes

• Explain telehealth systems, and the licensure and reimbursement questions attached to them.
• Explain population health analytics and risk stratification.
• Explain clinical research informatics and electronic data capture.
• Explain public health informatics and reportable-condition surveillance.
• Explain imaging informatics — PACS, DICOM.
• Explain consumer health informatics — patient portals, wearables, patient-generated data.
• Explain precision medicine and genomic data in the record.
• Explain cybersecurity in health care, including ransomware and its clinical consequences.
• Explain project management for informatics implementations.
• Explain AI and machine learning in clinical settings and their regulatory status.

Major Topics

Required Topics

• The field defined — informatics, HIM, clinical informatics, health IT.
• The health record — content, purposes, the legal health record.
• Electronic health records — architecture, workflow, adoption history, benefits and harms.
• Classification and coding systems.
• Coding, documentation and reimbursement.
• Data quality and integrity.
• Standards and interoperability — HL7, FHIR, DICOM.
• Health information exchange.
• HIPAA Privacy Rule.
• HIPAA Security Rule and risk management.
• Breach notification and enforcement.
• Information blocking and patient access.
• Ethical and legal issues in documentation.
• Clinical decision support and alerting.
• Secondary use, de-identification and governance.
• System selection, implementation and workflow.
• Usability, human factors and safety.

Optional Topics

• Telehealth.
• Population health analytics.
• Clinical research and public health informatics.
• Imaging informatics.
• Consumer informatics and patient-generated data.
• Genomics in the record.
• Healthcare cybersecurity and ransomware.
• Implementation project management.
• AI and machine learning in clinical care.

Resources & Tools

• Standard textbooks: Hoyt and Hersh, Health Informatics: Practical Guide — widely adopted, frequently updated and available inexpensively; Nelson and Staggers, Health Informatics: An Interprofessional Approach; Wager, Lee and Glaser, Health Care Information Systems; Oachs and Watters, Health Information Management (AHIMA) for the HIM side.
• Free authoritative sources — this field's primary documents are all public: the Office of the National Coordinator for Health IT (ONC), now part of ASTP, for certification criteria, interoperability rules and information blocking guidance; the HHS Office for Civil Rights for HIPAA guidance and the breach portal, which lists reported breaches and is genuinely instructive reading; CMS for coding, quality programmes and reimbursement; and HL7 International, whose FHIR specification is free and readable.
• Terminology resources: the UMLS and SNOMED CT browser (free with registration), LOINC, and the CDC's ICD-10-CM files. ⚠ Actually browsing SNOMED or LOINC for an afternoon teaches more about clinical terminology than any chapter.
• Professional bodies and certification: AHIMA (American Health Information Management Association) — the RHIA and RHIT credentials, and ⚠ RHIA eligibility requires graduation from a CAHIIM-accredited programme, which is a programme-level matter, not a course-level one; HIMSS — the CAHIMS credential is designed for students and early-career entrants and is a realistic first certification; and AMIA for the academic and clinical informatics side.
• Florida context and data: the Agency for Health Care Administration (AHCA) publishes hospital utilisation and financial data and operates FloridaHealthFinder; the Florida Health Information Exchange; and the Florida Department of Health for reportable-condition electronic reporting.
• Journals: JAMIA (Journal of the American Medical Informatics Association), Applied Clinical Informatics, Journal of AHIMA.
• ⚠ Hands-on EHR access varies by programme. Some institutions license an academic EHR environment; where yours does, use it — employers ask about system familiarity, and Epic and Cerner/Oracle Health experience is specifically valued.

Career Pathways

• Health information technologists and medical registrars (SOC 29-2072) — the direct destination.
• Medical records specialists (SOC 29-2072) — coding, documentation integrity, release of information.
• Health informatics specialists and clinical analysts (SOC 15-1211, 15-1299) — ⚠ EHR build and support analyst roles are a large and accessible entry point at Florida's major health systems, and vendor certification (Epic in particular) is typically employer-sponsored after hiring.
• Medical and health services managers (SOC 11-9111) — informatics and HIM management.
• Clinical documentation improvement specialists (SOC 29-2072) — ⚠ frequently requires clinical background, and well compensated.
• Health data analysts (SOC 15-2051, 15-1211) — quality measurement, population health, operations.
• Privacy and compliance officers (SOC 13-1041) — ⚠ HIPAA compliance is a statutory obligation for every covered entity, which makes this a structurally durable role.
• Healthcare cybersecurity (SOC 15-1212) — a growth area, and ransomware against health systems has made it a patient-safety function rather than only an IT one.
• Health IT project managers and implementation consultants (SOC 15-1299, 13-1082).
• Vendor roles — Epic, Oracle Health (Cerner), MEDITECH and others hire analysts and implementation staff directly from health informatics programmes.
• Public health informatics (SOC 15-1211) — state and county health departments.
• Graduate study — MS in health informatics, MHA, MPH, or the clinical informatics subspecialty for clinicians.

Special Information

⚠⚠⚠ FIU teaches a different subject under this number

	Statewide / UWF	FIU
Title	Health Informatics / Current Topics in Health Informatics	Healthcare Quality Management
Subject	medical informatics; computer applications in medicine; health data classification and coding; legal and ethical issues in documentation	quality management techniques; work systems, job analysis, space utilisation, inventory control, operations management
Field	health information systems and data	healthcare operations and quality improvement

These are different subjects. Health informatics is about data, systems and their governance; healthcare quality management is about operations, process improvement and industrial-engineering methods applied to care delivery. They are both legitimate health administration courses and neither prepares a student for the other's follow-on work.

⚠ The statewide title is Health Informatics, which matches UWF — so on this number UWF holds the majority reading and FIU is the outlier. That is worth noting because it is the reverse of the pattern this repository has documented repeatedly, where UWF diverges from the statewide title.

Practical consequences:

• The credit articulates on the number, so a transfer evaluator will record whichever you took as satisfying the other. ⚠ That is the risk rather than the reassurance.
• If your programme requires informatics — for a CAHIIM-accredited HIM curriculum, or as preparation for an informatics concentration — the quality management version does not supply it, and the coding, HIPAA and interoperability material is not covered anywhere else in a typical curriculum.
• If your programme requires quality management, the reverse applies.
• Keep your syllabus, and raise it with the department rather than the registrar.

⚠ Programmatic accreditation — CAHIIM

Health information management is another field where accreditation operates at the programme level and outranks individual course credit.

• CAHIIM (Commission on Accreditation for Health Informatics and Information Management Education) accredits HIM and health informatics programmes.
• ⚠ AHIMA's RHIA credential requires graduation from a CAHIIM-accredited programme. Transferred credits do not substitute for programme completion.
• An accredited programme may require its own version of this course to document curricular coverage, regardless of how your credit articulates.
• If the RHIA is your goal, confirm accreditation status directly with CAHIIM before choosing where to complete the degree.

This is the seventh profession this repository has documented where programmatic accreditation outranks course credit — after nursing, medical laboratory science, social work (CSWE), financial planning (CFP Board), chemistry (ACS) and public health (CEPH).

Prerequisites and position in the curriculum

UWF lists no course prerequisite, though the 4000-level number normally implies upper-division standing or admission to the major.

⚠ "No prerequisite" is not "no useful preparation." Three things help materially:

• Medical terminology — ⚠ the most useful single preparation. The coding and documentation material assumes you can read clinical language, and a student who cannot is translating while learning.
• An introduction to the US health system — how care is organised, paid for and regulated, which the reimbursement material builds on.
• Basic database and spreadsheet competence. Not programming, but understanding what a table, a key and a query are makes the data material far more tractable.

The course sits in the junior or senior year of health services administration, health informatics or health sciences programmes, and is a common elective for nursing, public health and information technology students.

Course format and workload

3 credits, 45 contact hours — lecture, three hours per week. Frequently offered online; health administration programmes serve many working students.

Expect 6–8 hours per week outside class. Assessment typically includes examinations, case analyses, and often a system evaluation, workflow analysis or HIPAA compliance project.

⚠ The volume of acronyms is the most-reported difficulty. HIPAA, HITECH, ONC, HL7, FHIR, ICD, CPT, SNOMED, LOINC, DRG, CDS, CPOE, PACS, HIE, PHI, EHR, EMR. Build a glossary in week one; the concepts are not hard but the vocabulary is dense and cumulative.

⚠ Currency — this course dates faster than most

Health IT regulation changes frequently and substantively:

• ONC certification criteria and interoperability rules are revised on a regular cycle, and the information blocking framework is comparatively recent.
• HIPAA guidance and enforcement priorities shift, and proposed Security Rule updates have been under consideration.
• Coding systems are updated annually — ICD-10-CM and CPT both change every year.
• Telehealth rules and reimbursement changed dramatically during and after the pandemic and have continued to move.

Treat any specific regulatory statement — in a textbook, a lecture, or this guide — as needing verification against ONC, OCR and CMS. ⚠ Nothing here is legal advice; compliance questions in practice go to counsel and to the institution's privacy officer.

⚠ Confidentiality — a professional habit to form now

This field handles protected health information, and the standards are legal rather than aspirational:

• Never use real patient data in coursework unless it has been properly de-identified and your institution has authorised it. Use synthetic data — ⚠ Synthea generates realistic synthetic patient records free, and several teaching EHR environments ship with sample populations.
• If you work in health care while taking this course, your employer's policies govern what you may discuss, and a case drawn from your own workplace can be a HIPAA disclosure. Generalise, or ask.
• Minimum necessary access applies to you as a student and as an employee, and access logs are audited. Looking up a record you have no work reason to see is a terminable and reportable act, and it happens to students on clinical placements every year.

Articulation and transfer

HSA4192 is a 4000-level upper-division course. ⚠ Note that two Florida College System institutions appear among those offering it (Pensacola State and St. Petersburg College), which is possible because both offer baccalaureate programmes — so it may be available before transfer, with the standard caution about upper-division residency requirements at the receiving university.

The number is used consistently, so SCNS articulation is clean — subject to the subject divergence above, which is the real issue.

⚠ Prefix note. HSA is health services administration; HIM health information management at some institutions; HSC health sciences; PHC public health; CGS/CIS computing. ⚠ Health informatics courses are distributed across HSA, HIM and occasionally CIS depending on where the programme sits, so search by subject rather than prefix when looking for an equivalent.

AI Integration

⚠ Health care is among the most active areas of AI deployment and among the most heavily regulated, which makes this section substantive rather than speculative.

Where it is genuinely in use:

• Ambient clinical documentation — systems that listen to the encounter and draft the note. ⚠ This is the fastest-moving application in health IT right now, and it targets the documentation burden the course identifies as a driver of clinician burnout. It also raises immediate questions about accuracy, attestation and who is responsible for what the note says.
• Computer-assisted coding — suggesting codes from documentation, with human review. This directly affects the coding workforce and changes the job rather than eliminating it.
• Diagnostic imaging support — ⚠ a substantial and growing number of AI-enabled devices have received FDA clearance, most heavily in radiology.
• Clinical decision support and risk prediction — sepsis alerts, deterioration scores, readmission risk.
• Patient-facing tools — triage chatbots, portal message drafting.
• Revenue cycle and prior authorisation automation on both the payer and provider side.

⚠⚠ The regulatory and safety picture belongs in this course specifically, because it is a health informatics problem rather than a general AI problem:

• Clinical decision support software can be a regulated medical device. The FDA has a framework for this, and whether a tool falls inside it depends on what it claims and whether a clinician can independently review its basis.
• Models trained on one population degrade on another, and health systems differ enough that a model validated elsewhere may not perform locally. Local validation is a governance obligation, not a nicety.
• Bias in health algorithms is documented and consequential. ⚠ The widely cited case of an algorithm using healthcare spending as a proxy for need — which under-identified Black patients because less had historically been spent on them at equal illness — is a health informatics failure precisely because it was a data choice.
• Alert fatigue applies to AI alerts too, and adding a poorly tuned model to a system clinicians already override is a safety problem.
• Documentation integrity. An AI-drafted note that the clinician signs is the clinician's note, legally and professionally. Attestation does not transfer to the tool.

Using AI tools for coursework. Models are useful for explaining a standard or a regulation, for summarising how a technical standard works, and for generating practice scenarios.

⚠⚠ Two rules here that are not negotiable:

1. Never put protected health information into an AI service. Not a patient's data, not a de-identified-looking excerpt you have not verified, not a case from your workplace. In practice this is an impermissible disclosure and potentially a reportable breach, and public AI services are not covered entities or business associates. This is the single most important professional habit in this course.
2. Never rely on a model for a regulatory or clinical answer. HIPAA requirements, coding rules and certification criteria change and are jurisdiction-specific. Use OCR, CMS and ONC.

Models also fabricate code numbers, standard version details, regulatory citations and statistics — all of which are checkable and will be checked.

Academic integrity. Read the syllabus; policies vary. Submitting generated work as your own violates every Florida institution's policy. ⚠ The professional stakes are higher than the academic ones here: health information roles involve background screening, HIPAA sanctions are individual as well as institutional, and documentation integrity is the core professional value of the field.