| 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 |
| 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”). | Phase | Objective | Deliverable | Suggested
