Learn StructureDefinition and CapabilityStatement from JSON Schema and OpenAPI
summary
Shows how to generate CapabilityStatement-driven OpenAPI by extracting supported resources and search parameters from FHIR and using StructureDefinition for data shapes, while keeping StructureDefinition as the source of truth. Demonstrates tooling choices: converting 20 existing models, authoring specs in FISH, generating OpenAPI but hitting JSON Schema/OpenAPI divergence (3.0 vs 3.1) and infinite-recursion in FHIR extensions, and building fast docs with React/Gatsby at beta.developer.redoxengine.com. Explains why value set binding, slicing/profiling, and format-agnostic validation favor FHIR native resources.
AI-written summary · about
chapters (31)
- 0:00Introduction
- 1:32Audience
- 2:08Spice
- 3:26OpenAPI
- 4:28Cloud Hosting
- 5:15Open API
- 6:03Fire
- 6:24Can you replace it all with OpenAPI
- 7:07Challenges with Fire
- 8:43Capability Layer
- 10:53Instances
- 12:00Capability Statement
- 15:02OpenAPI out of Fire
- 16:38JSON Schema and OpenAPI
- 18:05Write down your questions
- 18:43OpenAPI vs JSON Schema
- 21:12Resource to Value Set
- 22:57JSON vs XML
- 25:33Webhook Support
- 26:23Fire Documentation
- 26:58OpenAPI Documentation
- 27:50Fire Extensions
- 29:05What we learned
- 31:35Summary
- 32:28Contact Info
- 32:47Fire Questions
- 34:08Federal Government
- 36:30Enterprise Data Catalog
- 37:45Pub Talks
- 40:53Nicks Question
- 42:30Firespank
