The Goals of the Clinicians on FHIR activities are to:

  1.  Test FHIR Resources for
    1. Accuracy (clinical knowledge and clinical practices)
    2. Validity (designed correctly for the purpose of clinical practice and clinical use)
    3. Usability (useful and usable for the clinical story tested against)
  2. Identify any interoperability issues arising from clinical use of FHIR resources tested
  3. Provide recommendations to enhance/improve FHIR
  4. Improve FHIR development methodology and processes to involve clinicians from inception


  1.  Clinicians on FHIR Leadership to establish "tracks" for each Event.  (An event is a designated testing period such as a WGM Friday)
  2.  Participants submit a proposal of a use case or scenario they want to test at the event (link to proposal submission directions here)
  3.  Accepted proposals are assigned to a track by the Clinicians on FHIR Leadership
  4. Participants complete the Testing Preparation tool (link to spreadsheet tool, and completed example here)
  5.  Training is provided to the submitters on using the "ConMan" Tool
    1.  Via recorded webinars
    2.  In person at the WGM (Friday morning or previous day?)
      1. Proposed approximately 1.5 hour training time
      2. Refresher by David at the Wednesday Lunch - 45 min
  6. Users perform scenario testing and submit comments via the "ConMan" tool and submit gForge tickets as needed, log the tracker number in the ConMan comment section.  
  7. Comments are reviewed by the Clinicians on FHIR Leadership
    1. Accepted suggested comments = gForge ticket created if they have not been already
    2. Provide education re: suggested changes not accepted
  8. Retest the scenario once changes to Resource made
  9. Add successfully completed scenarios to Library of Successfully Complete Clinical Scenarios

Temporary Link to ConMan




The overall process to do this is as follows:

  1. Build the model using the clinFHIR Logical Modeler. Generally, you’d base the model on a core type and amend as desired.
  2. Add the model to the scenario
  3. Build the scenario

Lets look at each of these steps.

1. Build the model

2. Add the model to the scenario

  • No labels