Stream: workflow
Topic: Report Errors?
Michelle (Moseman) Miller (Mar 02 2018 at 00:24):
@Lloyd McKenzie I believe all of the following are report errors (really, 2 groups of errors: 1-4, and 5-6)
First group -- extensions exist
1-The resource CommunicationRequest does not have an element with a mapping to the Request pattern element Request.instantiates, nor is it listed as a context in the corresponding extesnsion.
2-The resource CommunicationRequest does not have an element with a mapping to the Request pattern element Request.relevantHistory, nor is it listed as a context in the corresponding extesnsion.
3-The resource ClinicalImpression does not have an element with a mapping to the Event pattern element Event.partOf, nor is it listed as a context in the corresponding extesnsion.
4-The resource Condition does not have an element with a mapping to the Event pattern element Event.partOf, nor is it listed as a context in the corresponding extesnsion.
Second group - pattern doesn't actually require performer.actor since performer is 0..*
5-The element ClinicalImpression.assessor has decreased the minimum cardinality from 1 to 0.
6-The element Condition.asserter has decreased the minimum cardinality from 1 to 0.
Michelle (Moseman) Miller (Mar 05 2018 at 15:07):
@Lloyd McKenzie the latest workflow report seems to have resolved the earlier issues, but I'm seeing 2 more that are likely bugs in the report.
1) The element Procedure.performer includes the following type(s) that are not part of the pattern: BackboneElement. 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.
2) The element CommunicationRequest.payload.content[x] has increased the minimum cardinality from 0 to 1. Verify that it's reasonable to make this element mandatory for all possible use-cases. If so, add this warning to the 'suppressed-workflow-warnings' file.
Why?
1) Event.performer is a backbone element
2) content is only 1..1 in context of payload, which is 0..* -- thus, the content element is not actually mandatory
Let me know if you will update the report or if I should treat them like exemptions
Michelle (Moseman) Miller (Mar 05 2018 at 15:14):
Additionally, @Lloyd McKenzie, some of the Patient Care issues that were previously reported (and not resolved yet) are missing from the report now. Examples include: 1, 4, 5, 6, and 12 from https://chat.fhir.org/#narrow/stream/workflow/topic/Patient.20Care.20Exemption.20Requests
Michelle (Moseman) Miller (Mar 05 2018 at 15:24):
A few more that are missing in the latest report (that were outstanding issues I was previously tracking):
- The element CommunicationRequest.category 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.
- The element CommunicationRequest.category has a w5 mapping of 'class' which disagrees with the Request pattern mapping of 'what'. Either the element has the wrong workflow mapping, the element has the wrong w5 mapping or there's a problem with the pattern's w5 mapping. If you're not sure what to fix, please discuss with the Workflow project.
- The resource CommunicationRequest does not have an element with a mapping to the Request pattern element Request.doNotPerform, nor is it listed as a context in the corresponding extesnsion. Possibilities: mapping was missed; element is in the 80% and should be added and mapped; element is outside the 80% but should be supported by the standard pattern extension; element is not relevant and this warning should be added to the 'workflow-warning-ignore' file
- The resource CommunicationRequest has multiple elements that map to pattern element Request.performer: . If this is because different elements are used for different types or because the resource embeds the concept of multiple Requests, then add to the ignore list. Otherwise, determine which element should actually be mapped.
- The element CommunicationRequest.recipient has a w5 mapping of 'who.focus' which disagrees with the Request pattern mapping of 'who.actor'. Either the element has the wrong workflow mapping, the element has the wrong w5 mapping or there's a problem with the pattern's w5 mapping. If you're not sure what to fix, please discuss with the Workflow project.
- The resource CommunicationRequest does not have an element with a mapping to the Request pattern element Request.statusReason, nor is it listed as a context in the corresponding extesnsion. Possibilities: mapping was missed; element is in the 80% and should be added and mapped; element is outside the 80% but should be supported by the standard pattern extension; element is not relevant and this warning should be added to the 'workflow-warning-ignore' file
- The resource CommunicationRequest has multiple elements that map to pattern element Request.supportingInfo: . If this is because different elements are used for different types or because the resource embeds the concept of multiple Requests, then add to the ignore list. Otherwise, determine which element should actually be mapped.
- The element ClinicalImpression.assessor has a name that differs from the workflow element it maps to: actor. Confirm that this inconsistency is intentional and is believed to better help domain implementers understand the purpose of the element in context. If so, add this warning to the 'workflow-warning-ignore' file.
- The element ClinicalImpression.assessor has a w5 mapping of 'who.author' which disagrees with the Event pattern mapping of 'who.actor'. Either the element has the wrong workflow mapping, the element has the wrong w5 mapping or there's a problem with the pattern's w5 mapping. If you're not sure what to fix, please discuss with the Workflow project.
- The element ClinicalImpression.status has a fixed binding to code system(s) http://hl7.org/fhir/event-status while the element uses the code system(s) http://hl7.org/fhir/clinical-impression-status. Confirm this is necessary and, if so, discuss with the workflow project. (We're trying to use a consistent code system across all of FHIR when we can.)
- The resource ClinicalImpression does not have an element with a mapping to the Event pattern element Event.statusReason, nor is it listed as a context in the corresponding extesnsion. Possibilities: mapping was missed; element is in the 80% and should be added and mapped; element is outside the 80% but should be supported by the standard pattern extension; element is not relevant and this warning should be added to the 'workflow-warning-ignore' file
Lloyd McKenzie (Mar 05 2018 at 17:32):
#1 and #2 are expected. There's a limit to how smart the comparison can be. I will see what's happening with the missing issues
Last updated: Apr 12 2022 at 19:14 UTC
