Course 1
From Clinical Need to Tested Tool
Follow a clinical workaround through explicit behavior, structured data, testing, and deployment.
intermediate 51 min 5 lessons
What you will learn
- Recognize when a private workaround has become shared infrastructure.
- Translate spreadsheet logic into inspectable program behavior.
- Write boundary tests for a clinical calculator.
- Explain how JSON, FHIR, and APIs move clinical data.
- Define the minimum checks required before deployment.
Prerequisites
- Basic familiarity with Git and GitHub.
- Ability to read a simple JSON object.
- 01 When the Workaround Becomes Infrastructure Recognize when a private clinical repair acquires shared responsibility. 7 min
- 02 Move Clinical Logic Out of the Spreadsheet Determine when spreadsheet logic needs version control, tests, and a clearer execution boundary. 8 min
- 03 Make Expected Behavior Executable Write tests that protect units, thresholds, missing values, and boundary behavior from silent drift. 8 min
- 04 Retrieve Clinical Data with FHIR Connect structured clinical data, authenticated APIs, and the application that consumes them. 14 min
- 05 Deploy and Verify the Tool Move a tested application from a local machine to reachable infrastructure and verify the live system. 14 min