ImagingStudy does not have a clean Workflow report

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Imaging Integration
    • ImagingStudy
    • Hide

      Warning: The element ImagingStudy.basedOn excludes the following type(s) that are part of the pattern: Reference(Appointment), Reference(AppointmentResponse), Reference(Claim), Reference(CommunicationRequest), Reference(Contract), Reference(DeviceRequest), Reference(EligibilityRequest), Reference(EnrollmentRequest), Reference(ImmunizationRecommendation), Reference(MedicationRequest), Reference(NutritionOrder), Reference(ProcessRequest), Reference(Task), Reference(SupplyRequest), Reference(VisionPrescription). If the pattern types fall within the 80% for the resource, then add them, otherwise add this warning to the 'workflow-warning-ignore' file.

        • Add to basedOn: Appointment, AppointmentResponse, Task
        • Add exceptions for remainders.

      Warning: The element ImagingStudy.procedureCode 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.

        • Add exception

      Warning: The element ImagingStudy.procedureCode 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.

        • Change procedureCode to 0..; procedureReference to 0..1, and add an exception.
        • Add procedureCode DICOM mapping of (008,0032)
        • Add basedOn DICOM mapping of (0032,1064)

      Warning: The resource ImagingStudy has multiple elements that map to pattern element Event.identifier: . 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.

          • remove uid, add constraints on "identifier" to require a mapping of oid to value, has "official" and specify the system to be limited to the RFC (to be tabled separately, does DICOM need its own RFC/scheme value - because its an OID, and because 64 character max) - to be covered in tracker 15123
          • update the description to read "DICOM Study Instance UID"
          • In the mappings, the Workflow mapping, the "accession" mapping to Identifier should be changed to event.basedOn.
          • change series UID and instance UID to mirror study uid, and update the comment field accordingly ("DICOM Series UID", "DICOM Instance UID")
          • the DICOM mappings will also need to be updated to reflect this
          • change sopClass to use Coding and map to DICOM mapping for sop class
          • search parameters will also need to be updated

      Warning: The element ImagingStudy.uid has a name that differs from the workflow element it maps to: identifier. 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.

          • this goes away with above fix

      Warning: The element ImagingStudy.uid excludes the following type(s) that are part of the pattern: Identifier. If the pattern types fall within the 80% for the resource, then add them, otherwise add this warning to the 'workflow-warning-ignore' file.

          • this goes away with above fix

      Warning: The element ImagingStudy.uid includes the following type(s) that are not part of the pattern: oid. 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.

          • this goes away with above fix

      Warning: The element ImagingStudy.uid 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.

          • this goes away with above fix

      Warning: The element ImagingStudy.accession has a name that differs from the workflow element it maps to: identifier. 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.

          • this should be ignored

      Warning: The element ImagingStudy.series.uid has a name that differs from the workflow element it maps to: identifier. 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.

          • this goes away with above fix

      Warning: The element ImagingStudy.series.uid excludes the following type(s) that are part of the pattern: Identifier. If the pattern types fall within the 80% for the resource, then add them, otherwise add this warning to the 'workflow-warning-ignore' file.

          • this goes away with above fix

      Warning: The element ImagingStudy.series.uid includes the following type(s) that are not part of the pattern: oid. 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.

          • this goes away with above fix

      Warning: The element ImagingStudy.series.uid 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.

          • The new identifier is mandatory, so this will be ignored

      Warning: The element ImagingStudy.series.instance.uid has a name that differs from the workflow element it maps to: identifier. 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.

          • this goes away with above fix

      Warning: The element ImagingStudy.series.instance.uid excludes the following type(s) that are part of the pattern: Identifier. If the pattern types fall within the 80% for the resource, then add them, otherwise add this warning to the 'workflow-warning-ignore' file.

          • this goes away with above fix

      Warning: The element ImagingStudy.series.instance.uid includes the following type(s) that are not part of the pattern: oid. 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.

          • this goes away with above fix

      Warning: The element ImagingStudy.series.instance.uid 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.

          • The new Identifier is mandatory, so minimum cardinality is 1, This should be ignored.

      Warning: The resource ImagingStudy 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

          • Add location as per the specification. Tie this to DICOM mapping (performed location 0008,1040; or maybe 0040,0243)

      Warning: The resource ImagingStudy 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

          • add note, and map to (0040,0280)

      Warning: The resource ImagingStudy has multiple elements that map to pattern element Event.occurrence[x]: . 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.

        • remove the mapping at series level

      Warning: The element ImagingStudy.started 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.

          • there's an override

      Error: The element ImagingStudy.started has a w5 mapping of 'when.init' 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.

          • needs to "be discussed with the workflow project"

      Warning: The element ImagingStudy.series.started 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.

        • safe to ignore

      Warning: The element ImagingStudy.procedureReference has a name that differs from the workflow element it maps to: partOf. 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.

        • override

      Warning: The element ImagingStudy.procedureReference excludes the following type(s) that are part of the pattern: Reference(ChargeItem), Reference(ClaimResponse), Reference(ClinicalImpression), Reference(Communication), Reference(Composition), Reference(Condition), Reference(Consent), Reference(Coverage), Reference(DeviceUseStatement), Reference(DiagnosticReport), Reference(DocumentManifest), Reference(DocumentReference), Reference(EligibilityResponse), Reference(Encounter), Reference(EnrollmentResponse), Reference(EpisodeOfCare), Reference(ExplanationOfBenefit), Reference(FamilyMemberHistory), Reference(GuidanceResponse), Reference(ImagingStudy), Reference(Immunization), Reference(MeasureReport), Reference(Media), Reference(MedicationAdministration), Reference(MedicationDispense), Reference(MedicationStatement), Reference(Observation), Reference(PaymentNotice), Reference(PaymentReconciliation), Reference(ProcessResponse), Reference(QuestionnaireResponse), Reference(RiskAssessment), Reference(SupplyDelivery), Reference(Task). If the pattern types fall within the 80% for the resource, then add them, otherwise add this warning to the 'workflow-warning-ignore' file.

        • ignore all of these

      Warning: The resource ImagingStudy does not have an element with a mapping to the Event pattern element Event.performer, 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

        • adopt the "performer" set as defined in Event and then fix the mapping, and create a value set for function

      Warning: The resource ImagingStudy 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

        • addressed with above fix (fix the mapping)

      Warning: The resource ImagingStudy 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

        • addressed with above fix (fix the mapping)

      Warning: The element ImagingStudy.reason has a name that differs from the workflow element it maps to: reasonCode. 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.

        • update reason to reasonCode
      Show
      Warning: The element ImagingStudy.basedOn excludes the following type(s) that are part of the pattern: Reference(Appointment), Reference(AppointmentResponse), Reference(Claim), Reference(CommunicationRequest), Reference(Contract), Reference(DeviceRequest), Reference(EligibilityRequest), Reference(EnrollmentRequest), Reference(ImmunizationRecommendation), Reference(MedicationRequest), Reference(NutritionOrder), Reference(ProcessRequest), Reference(Task), Reference(SupplyRequest), Reference(VisionPrescription). If the pattern types fall within the 80% for the resource, then add them, otherwise add this warning to the 'workflow-warning-ignore' file. Add to basedOn: Appointment, AppointmentResponse, Task Add exceptions for remainders. Warning: The element ImagingStudy.procedureCode 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. Add exception Warning: The element ImagingStudy.procedureCode 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. Change procedureCode to 0.. ; procedureReference to 0..1 , and add an exception. Add procedureCode DICOM mapping of (008,0032) Add basedOn DICOM mapping of (0032,1064) Warning: The resource ImagingStudy has multiple elements that map to pattern element Event.identifier: . 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. remove uid, add constraints on "identifier" to require a mapping of oid to value, has "official" and specify the system to be limited to the RFC (to be tabled separately, does DICOM need its own RFC/scheme value - because its an OID, and because 64 character max) - to be covered in tracker 15123 update the description to read "DICOM Study Instance UID" In the mappings, the Workflow mapping, the "accession" mapping to Identifier should be changed to event.basedOn. change series UID and instance UID to mirror study uid, and update the comment field accordingly ("DICOM Series UID", "DICOM Instance UID") the DICOM mappings will also need to be updated to reflect this change sopClass to use Coding and map to DICOM mapping for sop class search parameters will also need to be updated Warning: The element ImagingStudy.uid has a name that differs from the workflow element it maps to: identifier. 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. this goes away with above fix Warning: The element ImagingStudy.uid excludes the following type(s) that are part of the pattern: Identifier. If the pattern types fall within the 80% for the resource, then add them, otherwise add this warning to the 'workflow-warning-ignore' file. this goes away with above fix Warning: The element ImagingStudy.uid includes the following type(s) that are not part of the pattern: oid. 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. this goes away with above fix Warning: The element ImagingStudy.uid 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. this goes away with above fix Warning: The element ImagingStudy.accession has a name that differs from the workflow element it maps to: identifier. 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. this should be ignored Warning: The element ImagingStudy.series.uid has a name that differs from the workflow element it maps to: identifier. 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. this goes away with above fix Warning: The element ImagingStudy.series.uid excludes the following type(s) that are part of the pattern: Identifier. If the pattern types fall within the 80% for the resource, then add them, otherwise add this warning to the 'workflow-warning-ignore' file. this goes away with above fix Warning: The element ImagingStudy.series.uid includes the following type(s) that are not part of the pattern: oid. 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. this goes away with above fix Warning: The element ImagingStudy.series.uid 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. The new identifier is mandatory, so this will be ignored Warning: The element ImagingStudy.series.instance.uid has a name that differs from the workflow element it maps to: identifier. 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. this goes away with above fix Warning: The element ImagingStudy.series.instance.uid excludes the following type(s) that are part of the pattern: Identifier. If the pattern types fall within the 80% for the resource, then add them, otherwise add this warning to the 'workflow-warning-ignore' file. this goes away with above fix Warning: The element ImagingStudy.series.instance.uid includes the following type(s) that are not part of the pattern: oid. 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. this goes away with above fix Warning: The element ImagingStudy.series.instance.uid 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. The new Identifier is mandatory, so minimum cardinality is 1, This should be ignored. Warning: The resource ImagingStudy 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 Add location as per the specification. Tie this to DICOM mapping (performed location 0008,1040; or maybe 0040,0243) Warning: The resource ImagingStudy 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 add note, and map to (0040,0280) Warning: The resource ImagingStudy has multiple elements that map to pattern element Event.occurrence [x] : . 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. remove the mapping at series level Warning: The element ImagingStudy.started 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. there's an override Error: The element ImagingStudy.started has a w5 mapping of 'when.init' 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. needs to "be discussed with the workflow project" Warning: The element ImagingStudy.series.started 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. safe to ignore Warning: The element ImagingStudy.procedureReference has a name that differs from the workflow element it maps to: partOf. 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. override Warning: The element ImagingStudy.procedureReference excludes the following type(s) that are part of the pattern: Reference(ChargeItem), Reference(ClaimResponse), Reference(ClinicalImpression), Reference(Communication), Reference(Composition), Reference(Condition), Reference(Consent), Reference(Coverage), Reference(DeviceUseStatement), Reference(DiagnosticReport), Reference(DocumentManifest), Reference(DocumentReference), Reference(EligibilityResponse), Reference(Encounter), Reference(EnrollmentResponse), Reference(EpisodeOfCare), Reference(ExplanationOfBenefit), Reference(FamilyMemberHistory), Reference(GuidanceResponse), Reference(ImagingStudy), Reference(Immunization), Reference(MeasureReport), Reference(Media), Reference(MedicationAdministration), Reference(MedicationDispense), Reference(MedicationStatement), Reference(Observation), Reference(PaymentNotice), Reference(PaymentReconciliation), Reference(ProcessResponse), Reference(QuestionnaireResponse), Reference(RiskAssessment), Reference(SupplyDelivery), Reference(Task). If the pattern types fall within the 80% for the resource, then add them, otherwise add this warning to the 'workflow-warning-ignore' file. ignore all of these Warning: The resource ImagingStudy does not have an element with a mapping to the Event pattern element Event.performer, 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 adopt the "performer" set as defined in Event and then fix the mapping, and create a value set for function Warning: The resource ImagingStudy 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 addressed with above fix (fix the mapping) Warning: The resource ImagingStudy 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 addressed with above fix (fix the mapping) Warning: The element ImagingStudy.reason has a name that differs from the workflow element it maps to: reasonCode. 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. update reason to reasonCode
    • Chris Carr/Kevin O'Donnell: 8-0-0
    • Enhancement
    • Non-compatible
    • STU3

      The workflow project has put together a report identifying places where resources don't align with patterns, as well as a mechanism for work groups to mark as "ignored" if they don't feel alignment is appropriate/necessary. ImagingStudy is still showing up on the report - meaning that an alignment review has not been completed (or there are issues with the suppression process - in which case please let me know). Alignment is most critical for normative resources, but should be completed for all resources that are FMM3 or higher (and should be considered for resources with lower FMM levels)

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: