What You Will Build

You will be building a practitioner-facing app. A doctor or clinician would use it to look at information about their patients. The idea is to give a practitioner a single place to see everything they need about a patient, without chasing down information across multiple systems.

The challenge is split into two weeks. This way, you have something specific to work on each week.

Week 1: Patient management

In week one, you will build the patient management side of the app. Here’s what it needs to do:

• List all patients on the FHIR server, showing name, gender, and date of birth
• Create new patients using a form with those same fields. All fields need to be validated, for example, date of birth cannot be in the future, gender needs to be selected from a fixed set of values, etc.
• Edit existing patients and save updates back to the FHIR server
• Search patients by name

Week 2: Patient details page

In week two, you go deeper. When a practitioner clicks on a patient, they should see the patient’s full medical history. At minimum, the page should include:

• Demographics: Name, gender, date of birth, at the top of the page
• Vital signs: blood pressure, heart rate, temperature, respiratory rate, oxygen saturation, height, weight, BMI
• Active conditions and diagnoses
• Active medications

How you display this information is up to you. The patient listing page will look similar across submissions, but the details page is where you can differentiate. We’ve had participants build it for clinical trials, personal injury law firms, and more. You can also apply your own context if you have one.

If you already know how to build this

The next lesson covers how to get access to your FHIR server, after that, use these requirements and start building. You only need to come back to the tutorials if you get stuck.

Good luck!