Stream: workflow
Topic: EpisodeOfCare workflow mappings
Cooper Thompson (Feb 27 2018 at 19:44):
I'm working through the WorkflowIssues warnings for EpisodeOfCare. One of the warnings is about EpisodeOfCare.diagnosis.condition including a Reference(Condition) which is not a type in the pattern in Event.reasonReference.
But it is... Event.reasonReference does include Condition.
<issue severity="Warning" pattern="Event" path="Event.reasonReference" issue="Element includes types not found in pattern">The element EpisodeOfCare.diagnosis.condition includes the following type(s) that are not part of the pattern: Reference(Condition). If the types should be considered for addition to the pattern, contact the FHIR Workflow project. Otherwise, add this warning to the 'suppressed-workflow-warnings' file.</issue>
Is that an error in the report, or am I missing something?
Lloyd McKenzie (Feb 27 2018 at 19:48):
Error in the report. I'll try to get a fix out next week.
Cooper Thompson (Feb 27 2018 at 19:51):
Also, since EpisodeOfCare can involve several actors, having a 1..* for our mapping to Event.performer.actor seems reasonable, correct?
<issue severity="Warning" pattern="Event" path="Event.performer.actor" issue="Element max cardinality made repeating">The element EpisodeOfCare.team has increased the maximum cardinality from 1 to *. Is it in the 80% for this element to repeat? Is there a need to change the workflow pattern? Please discuss with the workflow project.</issue>
Lloyd McKenzie (Feb 27 2018 at 20:06):
I would map to Event.performer rather than Event.performer.actor - the actors and roles would be inside the team
Lloyd McKenzie (Feb 27 2018 at 20:15):
But yes, no cardinality issues - though I'm not clear on why you'd need multiple teams given that eam has 0..* within it. (And not sure how you'd interpret multiple people with the same role from different teams)
Last updated: Apr 12 2022 at 19:14 UTC
