Skip to end of metadata
Go to start of metadata


  • Approve (minutes from previous meeting)


  • Lloyd McKenzie (chair/scribe)
  • Emma Jones
  • Judy Williamson
  • Ricardo Quintano
  • Vadim Peretokin
  • Craig Newman
  • Jose Costa Teixeira

joined late

  • John Hatem
  • Ana Kostadinovska
  • Stephen Chu

Minutes Approval


Emma had questions around whether CareTeam was considered a "workflow" resource and how to manage the requirements documented in  FHIR-25267 - Getting issue details... STATUS .

Recommendation was that CareTeam is not a workflow resource - i.e. it is not a Definition, Request or Event.  However, it (and any other resource) can have "requests" for change made against it and those requests might be accepted, refused, etc.  The general mechanism for making requests for change (to CareTeam or anything else) would generally be Task.  It may make sense to have a status on CareTeam.participant if most systems that manage care teams commonly maintain non-active participants along with active participants in the list.  However, if this is done, the state should simply reflect the passive state of participation (planned, active, suspended, etc.), not the request for change (requested, accepted, refused, etc.)

Better workflow guidance

Jose proposes that we create an implementation guide on workflow.  Discussion about whether a separate IG was necessary.  Agreed to pursue the creation of more examples and worry about whether to split them into a separate IG later.

Tracker Items

  • FHIR-22931 - Getting issue details... STATUS  - Persuasive
  • FHIR-23040 - Getting issue details... STATUS  - Shouldn't be workflow.  Lloyd to update so it doesn't refer to the pattern
  • FHIR-25199 - Getting issue details... STATUS  - Waiting for input from Grahame

Use of ExampleScenario

Provided an overview on the purpose of ExampleScenario for Ricardo


2:50 Eastern