
Join the kickoff team meeting at North Valley Health System (NVHS). Meet the people you will work with throughout the course and see how the project, the roles and the agenda fit together.
Who this course is for, what you need to get started, and what you will build: a signed-off mapping specification and a delivery plan in Jira for a healthcare vendor onboarding case at NVHS.
Mo Kammoun, MS Electrical Engineering (Boston University), Scrum Master certified. 25+ years in telecom, pharma, healthcare: AT&T Labs, Bell Labs, Merck & Co, Verizon, CHOP, Elsevier.
A tour of the four modules and the NVHS case, and how the weeks line up: Module 1 (Weeks 1 and 2), Module 2 (Week 3), Module 3 (Weeks 4 and 5) and Module 4 (Weeks 6 to 13).
How the course is organized and how to work with the two tools you use throughout it: the mapping table (ten rows, P01 to P05 and E01 to E05) and Jira.
Team status update that closes the course introduction: what is in place, and what starts on Monday with Module 1.
Team meeting that sets the agenda for Weeks 1 and 2: onboarding the vendor, the project scope, the stakeholders and the requirements.
What the vendor onboarding project is, and what the business analyst does in it from the first week.
Identify the stakeholders and assign who is responsible, accountable, consulted and informed with a RACI chart.
Why the scope is small: the minimum necessary principle and how it limits the data NVHS shares with the vendor.
Prepare for and run requirements interviews with the stakeholders, and capture what they tell you.
Turn what you gathered into clear, testable written requirements the whole team can use.
Set up the Jira project that holds the requirements now and the user stories later in the course.
Team status update that closes Module 1: what was delivered in Weeks 1 and 2 and what comes next.
Team meeting that opens Week 3: where the project stands, what the team needs from you, and the plan for learning to read the data.
What an HL7 v2 ADT (admit, discharge, transfer) message is, and the events that trigger it.
Read an HL7 v2 message segment by segment and field by field, and locate the values that matter for the mapping.
What FHIR is in plain terms, and what the Patient and Encounter resources look like.
How patient and visit identifiers are carried in HL7 v2 and in FHIR: a system plus a value.
Why a code needs its code system, and which codes change as data moves through the gateway.
How data flows from NVHS through the gateway to the vendor, and what the vendor receives.
Team status update that closes Module 2: the documents produced in Week 3 and what comes next.
Team meeting that opens Week 4: where the project stands and why the talking now has to turn into a written mapping specification.
What a mapping specification is and what it contains, starting with a blank template: a header block and two sections.
Write the patient section of the mapping specification: rows P01 to P05, with exact rule text.
Write the encounter section: rows E01 to E05, including the translation of visit class and status.
Separate what comes from the HL7 v2 to FHIR guide from what NVHS decided itself, and record each decision with an owner and a reason in a gap and decision log.
Why unmapped data is documented, and how a change request form handles requests for more data.
Review the specification with a checklist, make sure every row has an owner, and record the approval of version 1.0.
Team sign-off review that closes Module 3: the signed specification, the four principles that carry over, and what starts in Week 6.
Team meeting that opens Module 4: how the signed specification becomes a Jira backlog, and the four sprints from Week 6 to Week 13.
Turn the rows of the mapping specification into user stories in Jira.
Write acceptance criteria that make each user story testable.
Order the backlog and plan a sprint around the stories.
Write test cases and connect them to the requirements with a traceability view.
Run user acceptance testing and manage the defects it finds.
Prepare go-live and hand the work over to the people who will run it.
Team sprint review that closes Module 4: what was delivered, what was learned, and the handoff.
A recap of the method from start to finish and the toolkit of documents you built along the way.
How to apply the method on your own projects at work, and where to go next.
Closing team meeting with the VP: what the team delivered, and what carries over to your own work.
This course contains the use of artificial intelligence.
Course description
When a hospital system connects a new vendor to its data, the business analyst is the person who holds the project together. This course puts you in that seat, inside a working Agile team.
You play the BA at North Valley Health System (NVHS), onboarding a specialty pharma vendor that will receive patient and visit data from the hospital's HL7 v2 messages as FHIR resources. You run the work from start to finish: you identify stakeholders, gather and write requirements, agree what data is shared and what is not, document the mapping, turn it into user stories in Jira, test it, and take it live.
You never work alone. Meet the project team: Hannah Park, the Scrum Master; Dr. Elena Rostova, the clinical pharmacist who is the business sponsor and Product Owner; Marcus Vance, the Lead Integration Architect who owns the gateway and its rules; Nina Okafor, the Test Analyst; Sarah Jenkins, the Privacy and Security Officer; and, on the vendor side, David Miller, the Project Manager, and Alex Chen, the Lead Developer.
Every module opens and closes the way real projects do. Each module starts with a realistic team meeting that sets the agenda, where the team talks through where the project stands and who does what. Each module ends with a status update in the style of a Sprint Review, where every team member gives their own perspective on what was delivered and what was learned. The course finishes with a final project meeting in which the NVHS Vice President of Clinical Operations congratulates the team. Between the meetings, the lessons are focused, step-by-step instruction in a single clear voice, so you can follow the method without the noise.
The course teaches the process, not one company's mapping. Every organization maps its own fields, so you work through a small example of 10 mapping rows covering patient identity and the visit. You learn how to build such a table, check it against the HL7 standard, question it, and get it signed off. You can apply the same method to your own fields.
Privacy shapes the whole course. You learn why only the minimum data is shared, how to justify each field, and how to say no to the rest.
The course is for working professionals. You leave with a method and a set of documents you can adapt at work: a RACI, a requirements list, a mapping specification, user stories with acceptance criteria, a traceability view, a UAT log and a go-live checklist, plus a clear picture of how a business analyst works with each role on an Agile team.
What you will learn
Explain the BA's role in a healthcare vendor onboarding and run the project with a clear stakeholder map and RACI.
Work inside an Agile team: take part in sprint kickoffs, status reviews and retrospectives, and know which role owns which decision.
Apply the HIPAA minimum necessary rule to decide what data a vendor receives and what it does not.
Gather and write clear, testable requirements by interviewing the vendor, the source-system team and privacy.
Set up a Jira project for an interface onboarding, with epics, issue types and a workflow.
Read an HL7 v2 ADT message and identify the patient and visit values in it.
Describe FHIR Patient and Encounter resources, identifiers, and code systems in plain terms.
Build and review a mapping specification from source field to FHIR target, and separate the standard from your own business rules.
Write user stories and acceptance criteria from mapping rows, plan a sprint, and link requirements to stories and tests.
Run UAT, log and triage defects, and prepare a go-live checklist and handoff.
Who this course is for
Business analysts and systems analysts who work, or will work, on healthcare integrations.
Project managers and Scrum Masters who run or support interface and vendor onboarding projects.
Product owners and QA analysts who write or test requirements for healthcare data exchange.
IT and clinical informatics staff who join onboarding projects and need the BA process.
This course is not for people who want to learn to build interface engines or write code. It teaches the analysis, documentation and delivery side.
Requirements
No HL7 or FHIR experience is needed; Module 2 teaches what you need.
Basic knowledge of business analysis terms such as requirements and stakeholders helps but is not required.
Access to Jira. A free account is enough for the exercises.
A spreadsheet or document tool for the templates.