Snis 645 Better -

| Criterion | % of Final Grade | |-----------|------------------| | Problem relevance & clarity | 10 % | | Technical depth (standards, architecture) | 20 % | | Prototype functionality & code quality | 25 % | | Evaluation methodology & results | 20 % | | Writing quality & visual communication | 15 % | | Oral defense & Q&A handling | 10 % | | Question | Quick Answer | |----------|--------------| | Do I need to know Java? | No. The course uses R (for analytics) and Python/JavaScript for API work. If you’re comfortable with one scripting language, you’ll be fine. | | Can I use a commercial FHIR server? | Yes, but the HAPI FHIR sandbox is free, lightweight, and fully compatible with the lab assignments. | | What if I’m not a programmer? | Focus on logic building (CDS rules, data mapping). The labs provide starter code; you’ll mainly edit JSON/YAML and write small functions. | | Is group work allowed for the capstone? | Most sections require individual projects to assess personal mastery, but you can collaborate on peer‑review and share resources. | | How much time should I allocate each week? | ~3 hrs of lecture + 2 hrs of reading + 3‑4 hrs of lab/work = 8‑9 hrs total. Adjust if you’re a non‑programmer (add 1‑2 hrs for coding practice). | 7️⃣ Quick‑Start Checklist (Print or Pin to Your Desk) | ☐ | Set up your dev environment (GitHub, VS Code, FHIR sandbox) | | ☐ | Download the syllabus and highlight all due dates . | | ☐ | Create a folder structure on your computer: SNIS645/Week01 , Week02 , … Capstone . | | ☐ | Add the core textbook to your reading list (e‑book or library copy). | | ☐ | Join the course Slack/Discord for rapid Q&A. | | ☐ | Schedule weekly office‑hour slots (at least 2 ×

| Tool | Use | Quick‑Start Link | |------|-----|------------------| | | Statistical modeling, Shiny apps | https://posit.cloud | | VS Code + Live Share | Code editing, pair programming | https://code.visualstudio.com | | Postman | Test REST APIs (FHIR) | https://www.postman.com | | GitHub Classroom | Version control, project submission | https://classroom.github.com | | FHIR‑Sandbox (HAPI) | Deploy a local FHIR server | https://hapifhir.io | | OpenCDS | Build rule‑based CDS modules | https://github.com/openCDS | 4️⃣ How to Master Each Component | Skill | Study Strategy | Practice Routine | |-------|----------------|------------------| | Reading | • Skim headings, abstract, conclusion first. • Highlight definition sentences (e.g., “FHIR is …”). • Write a 3‑sentence “elevator pitch” for each article. | 30 min daily. Use Zotero for citation management. | | Hands‑On Labs | • Follow the “copy‑paste‑run‑modify” pattern: copy starter code → run → change one parameter → observe outcome. • Keep a lab notebook (digital markdown) with screenshots. | Allocate 2 h each lab day. Commit changes to a private Git repo . | | Writing Assignments | • Start with a bullet‑point outline (intro, problem, method, results, discussion). • Use APA 7th citation style; set up a Word/LaTeX template early. | Draft first half by the midway point; peer‑review with a classmate. | | Presentations | • Follow the “3‑Slide Rule” : 1‑slide problem, 1‑slide solution, 1‑slide impact. • Practice in front of a mirror or record on Zoom → watch playback. | Rehearse 2× before the actual slot; time yourself. | | Exams | • Create one‑page cheat‑sheet (allowed for self‑study) summarizing formulas, standards, and acronyms. • Form a study group ; rotate “quiz master” each session. | Do one practice question per day from the reading guide. | 5️⃣ Capstone Project Blueprint A capstone is the hallmark of SNIS 645. Below is a step‑by‑step skeleton that you can plug any health‑IT problem into (e.g., “Improving vaccination alerts” or “Integrating wearable data into a chronic‑care dashboard”). snis 645

(Assuming “SNIS 645” is a graduate‑level course in S ystems N etworks, I nformation, and S tudies – e.g., “Advanced Topics in Health‑Information Systems”). | Criterion | % of Final Grade |

Below is a you can use whether you’re just enrolling, midway through the semester, or polishing up your final project. Feel free to adapt the timeline to your institution’s calendar, but keep the core milestones in place so you stay on track. 1️⃣ Course Overview | Element | What It Means for You | |---------|-----------------------| | Course Title | Advanced Topics in Health‑Information Systems (or equivalent) | | Credit Hours | 3 (typically 9 – 12 h/week of contact + independent work) | | Prerequisites | SNIS 500‑540 series, basic statistics, introductory programming (R/Python), and a fundamentals course in health informatics. | | Core Goal | Equip you to design, evaluate, and implement complex health‑information systems (HIS) that improve patient outcomes, data quality, and workflow efficiency. | | Key Competencies | • System architecture & integration • Data governance & security • Clinical decision support (CDS) design • Interoperability standards (HL7, FHIR, DICOM) • Evaluation methods (usability, implementation science) | | Typical Deliverables | 1. Weekly reading reflections 2. Hands‑on labs (FHIR sandbox, HL7 messaging) 3. Mid‑term case‑study analysis 4. Final capstone project + oral defense. | 2️⃣ Semester‑Long Timeline (12 Weeks) | Week | Theme | Core Activities | Deliverable | |------|-------|----------------|-------------| | 0 | Orientation | Syllabus deep‑dive, set up learning environment (GitHub, RStudio, VS Code, FHIR sandbox). | Course plan uploaded to LMS. | | 1 | Health‑Information System Landscape | Lecture + reading: Health Informatics: An Overview (Chapter 1). Lab: Map components of a hospital EMR. | 1‑page system map (submitted via Canvas). | | 2 | Interoperability Standards | HL7 v2/v3 vs FHIR deep dive. Lab: Build a simple FHIR resource (Patient). | FHIR‑JSON file + short reflection. | | 3 | Data Governance & Security | GDPR, HIPAA, data‑use agreements. Guest speaker (privacy officer). | Policy‑brief (max 800 words). | | 4 | Clinical Decision Support (CDS) | Knowledge‑based vs data‑driven CDS. Lab: Create a basic rule‑based alert in OpenCDS. | CDS rule prototype (Git repo). | | 5 | Usability & Human‑Centered Design | Nielsen heuristics, usability testing protocols. Lab: Conduct a 5‑minute think‑aloud test on a mock UI. | Usability report + video clip. | | 6 | Implementation Science | Frameworks (CFIR, RE-AIM). Reading: Implementation Research in Health IT . | Mini‑case analysis (2 pages). | | 7 | Mid‑Term Exam | Closed‑book, 60 min. Covers weeks 1‑6. | Exam (graded). | | 8 | Analytics & Machine Learning in HIS | Predictive modeling for readmission risk. Lab: Train a logistic regression model in R. | Model code + ROC curve. | | 9 | Integration & Middleware | ESB, API gateways, FHIR‑to‑HL7 adapters. Lab: Connect a mock EHR to a decision‑support service via REST. | Integration script + diagram. | | 10 | Emerging Tech | Blockchain for consent, IoT wearables, AI‑driven triage bots. | 1‑page “tech‑watch” note. | | 11 | Capstone Project Work‑in‑Progress | Peer‑review session, instructor office hours. | Draft of final report (30 %). | | 12 | Final Presentations & Submission | 12‑minute oral defense + Q&A. Submit final report + code repo. | Final grade (project 50 % + participation 30 % + exam 20 %). | Tip: Mark all due dates in a digital calendar (Google Calendar/Outlook) with 2‑day and 1‑day reminder alerts. This prevents “last‑minute” scrambling. 3️⃣ Core Readings & Resources | Category | Recommended Texts | Free/Open‑Source Alternatives | |----------|-------------------|------------------------------| | Foundations | Health Informatics: An Interprofessional Approach (M. Shortliffe & J. Bodenreider) | HIMSS whitepapers (downloadable PDF). | | Standards | FHIR Basics (B. Mandel) | HL7.org – FHIR specification (HTML, PDF). | | CDS | Clinical Decision Support: A Practical Guide (R. Kawamoto) | OpenCDS tutorials (GitHub). | | Implementation | Implementation Science in Health IT (E. Miller) | RE-AIM website (re-aim.org). | | Analytics | Practical Predictive Analytics and Decision Management (K. B. C. Miller) | UCI Machine Learning Repository for health datasets. | | Usability | Don’t Make Me Think (S. Krug) – UI basics | Nielsen Norman Group articles (free). | | | What if I’m not a programmer

| Phase | Objective | Deliverable | Suggested Timeline | |-------|-----------|-------------|--------------------| | | Identify a real‑world clinical workflow pain point. | Problem Statement (≤ 500 words). | Week 1‑2 | | B – Requirements & Architecture | List functional & non‑functional requirements; draw high‑level system diagram. | Requirements matrix + Architecture diagram (Visio/Draw.io). | Week 3‑4 | | C – Standards Mapping | Choose appropriate standards (FHIR, HL7 v2, DICOM). | Mapping table (clinical concepts ↔ FHIR resources). | Week 5 | | D – Prototype Development | Build a minimal viable product (MVP): API endpoints, UI mock‑up, CDS rule. | Working code repo (GitHub) + README. | Week 6‑8 | | E – Evaluation Plan | Define metrics (accuracy, usability SUS score, adoption rate). | Evaluation protocol (IRB‑ready if patient data used). | Week 9 | | F – Data Collection & Testing | Run usability tests, simulate data flows, collect metrics. | Raw data + analysis scripts. | Week 10‑11 | | G – Reporting & Dissemination | Write final report (10‑12 pages) & prepare 12‑min slide deck. | Final PDF + slide deck (PDF/PPT). | Week 11‑12 | | H – Defense | Present to faculty + peers, answer Q&A. | Recorded defense (optional for future portfolio). | Week 12 |