Profile Comparison between http://hl7.org/fhir/StructureDefinition/patient-contactPriority vs http://hl7.org/fhir/StructureDefinition/patient-contactPriority

Left:Patient Contact Priority (http://hl7.org/fhir/StructureDefinition/patient-contactPriority)
Right:Contact Priority (http://hl7.org/fhir/StructureDefinition/patient-contactPriority)

Messages

InformationStructureDefinition.titleValues for title differ: 'Patient Contact Priority' vs 'Contact Priority'
InformationStructureDefinition.statusValues for status differ: 'draft' vs 'active'
InformationStructureDefinition.shortValues for short differ: 'Order in which contacts should be used' vs 'Order in which contacts would be used for the purpose of the contact'
InformationStructureDefinition.definitionValues for definition differ: 'The order in which contacts for a patient should be used. For example, if a patient has multiple people listed as an emergency contact, which of those should be called first in an emergency.' vs 'The order in which contacts would be used for the purpose of the contact. For example, if a patient has multiple people listed as an emergency contact, which of those should be called first in an emergency. Or an Organization might have multiple contacts, one for press inquiries and two for patient inquires (one for scheduling, and one for billing questions). All three of those contacts may have a rank=1, since they all have different purposes.'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Extension
      .copyright
        .descriptionThe order in which contacts for a patient should be used. For example, if a patient has multiple people listed as an emergency contact, which of those should be called first in an emergency.The order in which contacts would be used for the purpose of the contact. For example, if a patient has multiple people listed as an emergency contact, which of those should be called first in an emergency. Or an Organization might have multiple contacts, one for press inquiries and two for patient inquires (one for scheduling, and one for billing questions). All three of those contacts may have a rank=1, since they all have different purposes.
        • Values Differ
        .experimentalfalse
          .fhirVersion5.0.0
            .jurisdiction
              ..jurisdiction[0]http://unstats.un.org/unsd/methods/m49/m49.htm#001
                .kindcomplex-type
                  .namePatContactPriority
                    .publisherHL7 International / Patient Administration
                      .purpose
                        .statusdraftactive
                        • Values Differ
                        .titlePatient Contact PriorityContact Priority
                        • Values Differ
                        .typeExtension
                          .urlhttp://hl7.org/fhir/StructureDefinition/patient-contactPriority

                            Structure

                            NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
                            .. Extension 0..1ExtensionOrder in which contacts should be used
                            0..1ExtensionOrder in which contacts would be used for the purpose of the contact
                              ... id 0..1idUnique id for inter-element referencing0..1idUnique id for inter-element referencing
                                ... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                Slice: Unordered, Open by value:url
                                0..*ExtensionAdditional content defined by implementations
                                Slice: Unordered, Open by value:url
                                  ... url 1..1uri"http://hl7.org/fhir/StructureDefinition/patient-contactPriority"1..1uri"http://hl7.org/fhir/StructureDefinition/patient-contactPriority"

                                    doco Documentation for this format