HSA4191: Health Information Systems

Course Description

HSA4191, Health Information Systems, is the health informatics course of the health services administration major. It covers how clinical and administrative data are captured, stored, moved, protected and turned into something a manager or clinician can act on — and why health care has found that so much harder than other industries.

The University of West Florida, which teaches it out of the Department of Public Health, describes "an overview of the functions of health information systems, including basic concepts, methods, and tools of data collection, use, analysis, and visualization," using case studies "drawn from the healthcare and public health sectors" to demonstrate "why evidence-based approaches are an essential part of professional practice," with students completing "case study projects using relevant job-related software, such as Excel workbooks, Access databases, and commercial electronic health record system interfaces." Florida Gulf Coast University, which titles it Health Care Info Systems, describes an "introduction to health care information systems" emphasising "advances in information technology, the general applications and management of information, databases and database management systems, microcomputer, internet, and medical informatics concepts and applications."

UWF's description is worth reading carefully, because it names the thing that makes this course employable rather than theoretical: students work in the actual tools — spreadsheets, relational databases and electronic health record interfaces — rather than reading about them. A graduate who can build a working Access database and pull a clean report out of an EHR has a demonstrable skill; one who can define "interoperability" does not.

HSA4191 is offered at approximately 10 Florida institutions and carries 3 credits with roughly 45 contact hours. It is a 4000-level course taken in the senior year of a health services administration or health informatics programme.

Title variation: Health Information Systems (the statewide title and UWF's) and Health Care Info Systems (FGCU). Same course.

Learning Outcomes

Required Outcomes

• Describe the role of information systems in health care delivery, administration and public health, and explain why health care adopted them later and less successfully than most industries.
• Distinguish data, information, knowledge and evidence, and explain the chain from a clinical event to an actionable report.
• Describe the principal categories of health information system: the electronic health record, computerised provider order entry, clinical decision support, laboratory and radiology systems, pharmacy systems, practice management and billing systems, and enterprise resource planning.
• Explain the structure and content of the legal health record and the distinction between the EHR, the EMR and the personal health record.
• Explain the standards and vocabularies that make health data exchangeable: ICD-10-CM/PCS, CPT/HCPCS, SNOMED CT, LOINC, RxNorm, and the HL7 family including FHIR.
• Explain interoperability — syntactic and semantic — describe why it remains incomplete, and describe the policy responses including the 21st Century Cures Act information-blocking provisions and TEFCA.
• Apply relational database concepts: tables, keys, relationships, normalisation, and querying; build and query a small database.
• Manipulate, clean and analyse health data in a spreadsheet, including formulas, lookups, pivot tables and charts.
• Produce clear data visualisations appropriate to a health care audience, and identify visualisations that mislead.
• Explain data quality dimensions — completeness, accuracy, timeliness, consistency — and identify the ways health data routinely fails each.
• Apply HIPAA Privacy and Security Rules to a scenario, including the minimum necessary standard, permitted uses and disclosures, business associate agreements, the de-identification standards, and breach notification.
• Describe health care cybersecurity threats — ransomware, phishing, insider misuse — and the administrative, physical and technical safeguards required.
• Explain the system life cycle in a health care setting: needs assessment, selection and vendor evaluation, implementation, training, go-live, optimisation and replacement.
• Explain why health IT implementations fail, including workflow mismatch, insufficient training, inadequate governance and clinician resistance, and describe change management approaches.
• Describe clinician documentation burden and alert fatigue as measurable consequences of system design.
• Use health data to support an administrative or clinical decision, and present the analysis in a professional deliverable.

Optional Outcomes

• Apply population health analytics, risk stratification and registry management.
• Describe telehealth platforms, remote patient monitoring and connected devices, and their data and regulatory implications.
• Explain public health informatics: syndromic surveillance, immunisation registries, notifiable disease reporting and Florida's systems.
• Apply project management methods to a health IT implementation.
• Analyse the revenue cycle's information systems and the technical basis of claims and denials.
• Use a business intelligence or visualisation platform such as Tableau or Power BI.
• Explain machine learning applications in clinical prediction and operations, and evaluate their validation.
• Analyse patient-facing technology: portals, apps, patient-generated data and digital access disparities.
• Prepare for a health information credential such as CAHIMS or CPHIMS.

Major Topics

Required Topics

• Introduction to health informatics: definitions, the field's scope, and why health care is a hard information environment
• History and policy drivers: HITECH and meaningful use, the 21st Century Cures Act, information blocking, TEFCA and the current federal framework
• The electronic health record: components, the legal health record, EHR versus EMR versus PHR, and the dominant vendors
• Clinical systems: computerised provider order entry, clinical decision support, e-prescribing, laboratory and imaging systems, PACS
• Administrative and financial systems: practice management, scheduling, registration, coding, billing and claims, enterprise resource planning
• Terminologies and code sets: ICD-10-CM and PCS, CPT and HCPCS, SNOMED CT, LOINC, RxNorm, and what each is for
• Data exchange standards: HL7 v2, CDA, and FHIR; APIs in health care; health information exchanges
• Interoperability: syntactic and semantic, the barriers, and the policy responses
• Database fundamentals: relational model, tables and keys, relationships, normalisation, queries and reports; building a database in Access or equivalent
• Spreadsheet analysis of health data: cleaning, formulas, lookups, pivot tables, charting
• Data visualisation for health audiences; dashboards; visualisation that misleads
• Data quality and data governance: dimensions of quality, stewardship, master patient index and patient matching
• Privacy and security: HIPAA Privacy and Security Rules, minimum necessary, authorisation, de-identification (Safe Harbor and expert determination), business associates, breach notification, and 42 CFR Part 2 for substance use records
• Cybersecurity in health care: the threat landscape, ransomware and its clinical consequences, safeguards, and incident response
• System selection and implementation: needs assessment, requests for proposal, vendor evaluation, contracting, implementation approaches, training, go-live support, optimisation
• Why implementations fail: workflow mismatch, governance, clinician engagement, unintended consequences
• Usability, documentation burden, alert fatigue and clinician burnout as system-design outcomes
• Using data for decisions: reporting, quality measurement, regulatory reporting, and the case study projects

Optional Topics

• Population health analytics, risk stratification and registries
• Telehealth, remote monitoring and connected devices
• Public health informatics and surveillance systems
• Health IT project management
• Revenue cycle systems and denials analytics
• Business intelligence tools (Tableau, Power BI)
• Machine learning in clinical prediction and operations
• Patient portals, patient-generated health data and the digital divide
• Precision medicine and genomic data systems
• Credential preparation (CAHIMS, CPHIMS)

Resources & Tools

• Health Informatics: An Interprofessional Approach (Nelson & Staggers, Elsevier) and Health Care Information Systems: A Practical Approach for Health Care Management (Wager, Lee & Glaser, Jossey-Bass) are the two most widely adopted texts; Wager is the standard for health administration programmes specifically.
• Introduction to Information Systems for Health Information Technology (Sayles, AHIMA) and Health Information Management Technology (AHIMA) are used where the course leans toward HIM practice.
• Biomedical Informatics (Shortliffe & Cimino) is the field's reference work, used in extract at undergraduate level.
• Software students actually use, and the reason to take this course seriously: Microsoft Excel (formulas, lookups, pivot tables — the single most transferable skill in the course), Microsoft Access or an equivalent relational database, and EHR training environments — academic versions of Epic, Cerner or purpose-built teaching systems such as EHR Go, SimChart or Practice Fusion. Tableau Public and Power BI (both free for students) appear where visualisation is emphasised.
• Standards and reference: HL7 International and the FHIR specification, which is free and readable; SNOMED International; LOINC (Regenstrief); CMS for code sets and reporting requirements.
• Policy and regulation: the Office of the National Coordinator for Health IT (ONC), now within the Assistant Secretary for Technology Policy, for certification and interoperability rules; the HHS Office for Civil Rights for HIPAA guidance and its published breach portal — the "wall of shame" is a genuinely useful teaching resource; and HealthIT.gov.
• Professional bodies and credentials: HIMSS (Healthcare Information and Management Systems Society), offering CAHIMS for early-career and CPHIMS for experienced professionals — CAHIMS is attainable by a student or recent graduate and is a real differentiator; AHIMA, offering RHIA and RHIT through accredited programmes; and AMIA for the academic informatics community.
• Florida-specific: the Agency for Health Care Administration (AHCA), which operates FloridaHealthFinder.gov and collects facility-level data; the Florida Department of Health systems including Florida SHOTS (immunisation registry), EDEN and the E-FORCSE prescription drug monitoring programme; Florida HIE and its Event Notification Service; and the Florida HIMSS chapter, which runs student events and is a practical networking route.

Career Pathways

• Health Information Systems Analyst / Clinical Applications Analyst — SOC 15-1211 (Computer Systems Analysts). The most direct destination and a genuinely accessible bachelor's-level role. Health systems employ analysts in volume to configure, support and optimise EHR modules, and vendor certification — Epic or Cerner credentialing, obtained after hire — is the career accelerator.
• Health Data Analyst and Clinical Data Analyst — SOC 15-2051 and 29-2072. Excel plus SQL plus health domain knowledge is a marketable combination immediately on graduation.
• Health Information Manager — SOC 11-9111 and 29-2072. Note that the RHIA credential requires a CAHIIM-accredited health information management programme, which is a different degree from health services administration; this course supports but does not substitute for it.
• Clinical Informatics Specialist — SOC 15-1211 and 29-1141 for nurse informaticists. Frequently filled by clinicians who move into IT, which is worth knowing for nursing students taking this course.
• EHR Implementation Consultant and Trainer — SOC 15-1211 and 13-1151.
• Privacy Officer and HIPAA Compliance Specialist — SOC 13-1041. Every covered entity must designate a privacy officer; the compliance function is large and growing.
• Health Care Cybersecurity Analyst — SOC 15-1212. Health care is among the most targeted sectors for ransomware, and the shortage is acute.
• Revenue Cycle Systems Analyst — SOC 15-1211 and 11-9111; see also HSA3170.
• Public Health Informatics Specialist — SOC 15-1211 and 19-1041, at the Florida Department of Health and county health departments.
• Project Manager, Health IT — SOC 11-3021 and 15-1299; the PMP credential applies.
• Florida employers of note: the large health systems and their IT organisations — AdventHealth (which runs one of the largest Epic installations in the country), Orlando Health, BayCare, Baptist Health, Tampa General, HCA Florida Healthcare, Memorial Healthcare System, Lee Health, UF Health, Nemours Children's Health, Moffitt Cancer Center and Mayo Clinic Florida; the health plans Florida Blue, Humana, Centene/Sunshine Health and Molina; the Agency for Health Care Administration and the Florida Department of Health; the Veterans Health Administration facilities, which run a distinct national system; and health IT consultancies with Florida operations.

Special Information

Position in the curriculum

HSA4191 is a senior-level course in health services administration, health informatics and health sciences programmes. It follows the health systems survey (HSA3111) and usually health care finance (HSA3170), and it sits alongside or before the capstone and internship. It is often the last technical course in the degree and, for students who take it seriously, the one that most directly produces an employable skill.

Prerequisites narrative

Neither UWF nor FGCU lists a course prerequisite for HSA4191 in its catalog entry. In practice, senior standing and completion of the health systems foundation are expected, and departments frequently restrict enrolment to majors. No programming background is required — the tools are spreadsheets, a desktop database and vendor interfaces rather than a language — but students with no prior spreadsheet competence will find the first weeks harder than the syllabus implies, and it is worth arriving with working Excel skills rather than acquiring them under deadline.

Course format and workload

Three credits, approximately 45 contact hours, no separate laboratory — though UWF's description makes clear that hands-on software work is embedded in the course. Online and hybrid delivery is very common in Florida health administration programmes. Assessment is project-based: case study deliverables built in Excel and Access, an EHR exercise, a system selection or implementation analysis, and often a HIPAA scenario analysis. Expect the workload to be front-loaded with tool learning and back-loaded with the project.

The practical advice for this course: keep the deliverables. A working Access database, a cleaned dataset with a pivot-table analysis, and a dashboard are portfolio artefacts that can be shown in an interview, and health IT hiring responds to demonstrated tool competence far more than to a transcript line.

Certification alignment worth planning around

This course maps onto CAHIMS (Certified Associate in Healthcare Information and Management Systems), the HIMSS entry-level credential, which is attainable by a student or recent graduate without years of experience. Many students do not know it exists. Sitting it near graduation is a low-cost, high-signal differentiator for analyst roles. CPHIMS follows with experience. Note the distinction from the AHIMA credentials: RHIA and RHIT require graduation from a CAHIIM-accredited HIM programme, so a health services administration graduate cannot sit them on the strength of this course.

Florida context

Several features make this course land differently in Florida. The state's health systems run very large EHR installations — AdventHealth's Epic deployment is among the largest nationally — which means a substantial local employer base for analysts and a real internal job market. Florida's age structure makes Medicare quality and regulatory reporting a larger share of health IT work here than the national average. AHCA publishes facility-level data through FloridaHealthFinder.gov, which makes real data available for course projects in a way most states do not permit. And Florida operates several distinctive state systems students should know by name — Florida SHOTS for immunisations and E-FORCSE, the prescription drug monitoring programme, whose use is mandated for controlled substance prescribers under Florida law.

Transfer and articulation

HSA4191 is a 4000-level SCNS course: the number is recognised statewide, but upper-division credit is not covered by the A.A. transfer guarantee and applicability inside a major is the receiving department's decision. It is generally not available before transfer from a Florida College System A.A., except at the Florida colleges offering bachelor's degrees in health services administration or health informatics — several of which do teach it. Because the software and tool component varies by institution, a receiving programme may ask what tools were actually used; carry a syllabus if the course was taken as a survey rather than as a hands-on class.

Course-code variations across Florida

Within the HSA prefix: HSA3111 (US health care systems), HSA3170 (health care finance), HSA4191 (this course), HSA4222 (long-term care administration), HSA4700-range research methods, and HSA4922-range capstones. Related content appears under HIM (health information management, in CAHIIM-accredited programmes — a different degree path), HSC (health sciences), PHC (public health, including public health informatics), and CGS, CIS and ISM prefixes for general information systems in the business or computing schools. Note that a general ISM information systems course is not a substitute for HSA4191 in a health administration major — the health-specific standards, privacy law and clinical workflow content is the point.

AI Integration

Health informatics is a field where AI has moved from prospect to deployment quickly, which makes this course one of the more important places to build judgement about it. It is also a field where the consequences of getting it wrong are clinical.

AI as subject matter — and this belongs in the course, not as an aside. Machine learning is now embedded in health information systems in production: sepsis and deterioration prediction models running inside EHRs, imaging triage tools with FDA clearance, ambient clinical documentation that drafts notes from the consultation audio, coding and revenue-cycle automation, no-show and capacity prediction, and large language models surfacing summaries inside clinician workflow. Students entering health IT roles will be configuring, validating and supporting these systems.

The critical competency is evaluation, not enthusiasm. Several documented failures make the point and are standard teaching cases: widely deployed sepsis prediction models that performed far worse in external validation than their vendor's claims; a population health algorithm that used historical cost as a proxy for health need and consequently under-referred Black patients at equal illness severity; and imaging models that degrade when applied to scanners or populations unlike their training data. The questions this course teaches — what was the validation population, what are the error rates and for whom, what happens to the workflow when the alert fires — are exactly the right ones.

Where AI helps a student in this course. Language models are effective at explaining a standard or a regulation, writing and debugging Excel formulas and SQL queries, explaining a database design decision, and drafting the narrative sections of a system selection report.

Where AI fails. Models state regulatory requirements incorrectly — HIPAA provisions, the Cures Act information-blocking exceptions and CMS reporting rules are frequently rendered wrong or out of date, and these are areas where being wrong has legal consequences. They fabricate code values: a plausible-looking ICD-10 or CPT code that does not exist, or exists and means something else. They produce SQL that runs and returns the wrong rows, which in a health context means a report that silently misstates a quality measure or a patient count. Every regulatory statement must be checked against HHS, ONC or CMS; every code against the actual code set; every query against a known-answer test case.

⚠ The absolute rule in this field: never put protected health information into a public AI service. Entering PHI into a consumer chatbot is a HIPAA disclosure to a party with no business associate agreement — a reportable breach, not a grey area. This applies to real clinical data in course projects as well as in practice. Use synthetic or de-identified data for anything involving a tool outside the institution's covered systems, and understand that de-identification has a defined legal meaning under the Privacy Rule (Safe Harbor's eighteen identifiers, or expert determination) — removing the name is not sufficient. This is the single most important professional habit this course can install.

Academic integrity. Policies vary; a common arrangement in this course permits AI for code and explanation while requiring that analysis, design decisions and recommendations be the student's own. Read the syllabus, and note that the deliverables here are portfolio artefacts — work you cannot explain in an interview has no value to you regardless of what it earned.