The following workflow issues were identified:

<workgroup name="cbcc">
<resource name="Consent">
<issue severity="Warning" pattern="Event" path="Event.code" issue="Different element names">The element Consent.category has a name that differs from the workflow element it maps to: code. 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.</issue>
<issue severity="Warning" pattern="Event" path="Event.code" issue="Element min cardinality has increased">The element Consent.category 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 'workflow-warning-ignore' file.</issue>
<issue severity="Warning" pattern="Event" path="Event.code" issue="Element max cardinality made repeating">The element Consent.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.</issue>
<issue severity="Error" pattern="Event" path="Event.code" issue="Element w5 mapping doesn't agree with pattern">The element Consent.category has a w5 mapping of 'class' which disagrees with the Event 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.</issue>
<issue severity="Warning" pattern="Event" path="Event.context" issue="Resource has no element mapped to pattern element">The resource Consent does not have an element with a mapping to the Event pattern element Event.context, 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</issue>
<issue severity="Warning" pattern="Event" path="Event.location" issue="Resource has no element mapped to pattern element">The resource Consent does not have an element with a mapping to the Event pattern element Event.location, 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</issue>
<issue severity="Warning" pattern="Event" path="Event.note" issue="Resource has no element mapped to pattern element">The resource Consent does not have an element with a mapping to the Event pattern element Event.note, 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</issue>
<issue severity="Warning" pattern="Event" path="Event.occurrence[x]" issue="Element missing types found in pattern">The element Consent.dateTime excludes the following type(s) that are part of the pattern: Period, Timing. If the pattern types fall within the 80% for the resource, then add them, otherwise add this warning to the 'workflow-warning-ignore' file.</issue>
<issue severity="Error" pattern="Event" path="Event.occurrence[x]" issue="Element w5 mapping doesn't agree with pattern">The element Consent.dateTime has a w5 mapping of 'when.recorded' which disagrees with the Event pattern mapping of 'when.done'. 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.</issue>
<issue severity="Warning" pattern="Event" path="Event.partOf" issue="Resource has no element mapped to pattern element">The resource Consent 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. 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</issue>
<issue severity="Warning" pattern="Event" path="Event.performer" issue="Multiple elements map to one pattern">The resource Consent has multiple elements that map to pattern element Event.performer: . If this is because different elements are used for different types or because the resource embeds the concept of multiple Events, then add to the ignore list. Otherwise, determine which element should actually be mapped.</issue>
<issue severity="Warning" pattern="Event" path="Event.performer" issue="Different element names">The element Consent.consentingParty has a name that differs from the workflow element it maps to: performer. 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.</issue>
<issue severity="Warning" pattern="Event" path="Event.performer" issue="Element missing types found in pattern">The element Consent.consentingParty excludes the following type(s) that are part of the pattern: Element. If the pattern types fall within the 80% for the resource, then add them, otherwise add this warning to the 'workflow-warning-ignore' file.</issue>
<issue severity="Warning" pattern="Event" path="Event.performer" issue="Element includes types not found in pattern">The element Consent.consentingParty includes the following type(s) that are not part of the pattern: Reference(Organization), Reference(Patient), Reference(Practitioner), Reference(RelatedPerson). If the types should be considered for addition to the pattern, contact the FHIR Workflow project. Otherwise, add this warning to the 'workflow-warning-ignore' file.</issue>
<issue severity="Warning" pattern="Event" path="Event.performer" issue="Different element names">The element Consent.organization has a name that differs from the workflow element it maps to: performer. 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.</issue>
<issue severity="Warning" pattern="Event" path="Event.performer" issue="Element missing types found in pattern">The element Consent.organization excludes the following type(s) that are part of the pattern: Element. If the pattern types fall within the 80% for the resource, then add them, otherwise add this warning to the 'workflow-warning-ignore' file.</issue>
<issue severity="Warning" pattern="Event" path="Event.performer" issue="Element includes types not found in pattern">The element Consent.organization includes the following type(s) that are not part of the pattern: Reference(Organization). If the types should be considered for addition to the pattern, contact the FHIR Workflow project. Otherwise, add this warning to the 'workflow-warning-ignore' file.</issue>
<issue severity="Warning" pattern="Event" path="Event.performer.actor" issue="Resource has no element mapped to pattern element">The resource Consent does not have an element with a mapping to the Event pattern element Event.performer.actor, 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</issue>
<issue severity="Warning" pattern="Event" path="Event.performer.function" issue="Resource has no element mapped to pattern element">The resource Consent does not have an element with a mapping to the Event pattern element Event.performer.function, 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</issue>
<issue severity="Warning" pattern="Event" path="Event.reasonCode" issue="Resource has no element mapped to pattern element">The resource Consent does not have an element with a mapping to the Event pattern element Event.reasonCode, 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</issue>
<issue severity="Warning" pattern="Event" path="Event.reasonReference" issue="Resource has no element mapped to pattern element">The resource Consent does not have an element with a mapping to the Event pattern element Event.reasonReference, 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</issue>
<issue severity="Warning" pattern="Event" path="Event.status" issue="Element draws from different code system">The element Consent.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/consent-state-codes. 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.)</issue>
<issue severity="Warning" pattern="Event" path="Event.statusReason" issue="Resource has no element mapped to pattern element">The resource Consent 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</issue>
<issue severity="Warning" pattern="Event" path="Event.subject" issue="Different element names">The element Consent.patient has a name that differs from the workflow element it maps to: subject. 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.</issue>
<issue severity="Warning" pattern="Event" path="Event.subject" issue="Element missing types found in pattern">The element Consent.patient excludes the following type(s) that are part of the pattern: Reference(Group). If the pattern types fall within the 80% for the resource, then add them, otherwise add this warning to the 'workflow-warning-ignore' file.</issue>
</resource>
</workgroup>