Profile Comparison between http://hl7.org/fhir/us/ecr/StructureDefinition/rr-communication vs http://hl7.org/fhir/us/ecr/StructureDefinition/rr-communication

Left:Reportability Response Communication (http://hl7.org/fhir/us/ecr/StructureDefinition/rr-communication)
Right:Reportability Response Communication (http://hl7.org/fhir/us/ecr/StructureDefinition/rr-communication)

Messages

ErrorStructureDefinition.versionValues for version differ: '1.0.0' vs '1.1.0'
InformationStructureDefinition.dateValues for date differ: '2020-01-29T20:30:08+00:00' vs '2020-12-16T19:27:50+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 Public Health Work Group' vs 'HL7 Public Health Work Group (http://www.hl7.org/Special/committees/pher/index.cfm)'
InformationStructureDefinition.jurisdictionAdded the item 'urn:iso:std:iso:3166#US'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Communication
      .copyright
        .date2020-01-29T20:30:08+00:002020-12-16T19:27:50+00:00
        • Values Differ
        .descriptionThis Communication profile represents the Reportability Response that will be created in response to an electronic Initial Case Report Composition. The sharing of the Reportability Response with clinical care will serve several functions, including to: * Communicate the reportability status, for the responsible PHA(s) of each condition included in the electronic Initial Case Report (eICR) * Identify who (a PHA or an intermediary) prepared the Reportability Response * Indicate whether the eICR has been sent to one or more PHA(s) * Identify which PHA(s) has/have been sent the eICR * Provide contact information for the responsible PHA(s) * Provide suggested or required clinical follow-up activities from the responsible PHA(s), including any additional reporting needs or infection control activities * Provide access to clinical support resources suggested by the responsible PHA(s) for identified reportable conditions * Confirm eICR receipt and processing A Reportability Response will also, when requested, be shared with the responsible PHAs (when they have not constructed it) for their internal use, so they understand what has been shared with clinical care and, and to monitor/audit decision support algorithm effectivesness and implementation. When a condition is considered reportable to more than one PHA, the Reportability Response can be helpful in communicating reporting that has been done to other PHAs. The Reportability Response Communication is also structured to allow: * Notification, alerting, routing and queueing in work or message management systems for healthcare personnel * Dynamic and static URIs for supplemental data collection and the provision of information resourcesThis Communication profile represents the Reportability Response that will be created in response to an electronic Initial Case Report Composition.
        • Values Differ
        .experimentalfalse
          .fhirVersion4.0.1
            .jurisdiction
              ..jurisdiction[0]urn:iso:std:iso:3166#US
              • Added the item 'urn:iso:std:iso:3166#US'
              .kindresource
                .nameRR_Communication
                  .publisherHL7 Public Health Work GroupHL7 Public Health Work Group (http://www.hl7.org/Special/committees/pher/index.cfm)
                  • Values Differ
                  .purpose
                    .statusactive
                      .titleReportability Response Communication
                        .typeCommunication
                          .urlhttp://hl7.org/fhir/us/ecr/StructureDefinition/rr-communication
                            .version1.0.01.1.0
                            • Values Differ

                            Structure

                            NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                            .. Communication SS
                              ... id ΣΣ
                                ... meta ΣΣ
                                  ... implicitRules ?!Σ?!Σ
                                    ... language
                                      ... text SS
                                        ... contained
                                          ... extension ExtensionExtension
                                            ... modifierExtension ?!?!
                                              ... identifier SΣSΣ
                                                ... instantiatesCanonical ΣΣ
                                                  ... instantiatesUri ΣΣ
                                                    ... basedOn ΣΣ
                                                      ... partOf ΣΣ
                                                        ... inResponseTo
                                                          ... status ?!Σ?!Σ
                                                            ... statusReason ΣΣ
                                                              ... category SS
                                                                ... priority ΣΣ
                                                                  ... medium
                                                                    ... subject SΣSΣ
                                                                      ... topic SS
                                                                        .... id
                                                                          .... extension ExtensionExtension
                                                                            .... coding ΣΣ
                                                                              .... text SΣSΣ
                                                                                ... about
                                                                                  ... encounter SΣSΣ
                                                                                    ... sent
                                                                                      ... received
                                                                                        ... recipient SS
                                                                                          ... sender SS
                                                                                            ... reasonCode ΣΣ
                                                                                              ... reasonReference ΣΣ
                                                                                                ... payload (Slice Definition)(Slice Definition)
                                                                                                  .... id
                                                                                                    .... extension ExtensionExtension
                                                                                                      .... modifierExtension ?!Σ?!Σ
                                                                                                        .... content[x]
                                                                                                          ... note

                                                                                                            doco Documentation for this format