Profiling for Clinicians
summary
Hands-on profiling using ClinFHIR's ClinFHIR logical modeler demonstrates making a Condition profile for oncology: changing patient identifier cardinality to 1.., forcing clinicalStatus, adding a string extension for treatment protocol, and nesting a constrained Observation for TNM staging observation using LOINC panels and SNOMED code sets. The model exports as a computable StructureDefinition posted to Happy server*, is discoverable by ClinFHIR, and validates structure; example-instance validation is still limited but the end-to-end profile publishing and retrieval workflow works.
AI-written summary · about
chapters (23)
- 0:00Start
- 1:01Viet Nguyen, MD
- 1:51The need for Profiles
- 4:59Profiling a resource
- 7:10Structured & published
- 7:51Using profiles
- 10:10Conformance Resources are Resources
- 12:20Must support?
- 13:13Extending a name
- 13:46Constraining cardinality
- 15:01Limit value domains
- 15:34Contextualize narrative
- 15:45Profiling bindings
- 16:29CodeSystem vs. ValueSet
- 18:03Add formal constraints
- 19:03Profile-less FHIR
- 19:33Simultaneous profiles
- 19:58Declaring profiles
- 20:43Forge
- 21:18Trifolia
- 22:41How to get system capabilities
- 24:13Create a New Logical Model
- 29:2175620-5 TNM clinical staging before treatment panel
related talks
46mIntroduction to Profiling
39mFirely tooling for putting FHIR in production
47mSNOMED overview
45mLearn to FSH: a friendly introduction to FHIR Shorthand
39mContent Management as Critical Success Factor for Personalized Medicine
50mIntroduction to FHIR
33mImplementation Guides
19mExtreme Makeover: Drupal.org Profile Edition