Firely tooling for putting FHIR in production
summary
Firely provides a practical toolchain: Forge (Windows) builds profiles and custom extensions (example: change Patient.birthDate cardinality to 1), the Firely .NET API (cross‑platform) creates and posts resources to a server, and Simplifier publishes profiles and assembles implementation guides. A Vonk server loads structureDefinitions and enforces strict validation so a patient without meta.profile or the required birthDate is rejected; the demo shows uploading, failing, adding meta.profile, then succeeding.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:26Overview
- 1:47Firely API
- 7:21FHIR API
- 7:54simplifier
- 9:53commandline tool
- 12:13One Floater
- 12:43Wind Tunnel Performance
- 13:12Demo
- 14:01API
- 15:57Upload
- 17:03Local Server
- 18:39Create new profile
- 19:44Profile example
- 21:18Administration restful API
- 22:04Profile creation
- 23:44App settings
- 24:26Enable allowed profiles
- 25:49Claiming conformance
- 27:59Optional fields
- 29:09Fire Profiles
- 30:08Publishing Profiles
- 33:08Publishing Implementation Guide
- 34:58New Guide
- 37:16Capability Statement
related talks
13mFHIR on the Command Line with Firely Terminal
47mLet's Build a FHIR Spec: Profiling with Forge
46mUsing clinFHIR to learn and develop FHIR solutions
40mFHIR Profiling: Overview & Introduction
45mA General Intro to FHIR
47mIntroduction to profiling
46mDevelopment and Testing Strategies
31mPublishing a FHIR specification