Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest vs http://hl7.org/fhir/us/physical-activity/StructureDefinition/pa-servicerequest

Left:US Core ServiceRequest Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest)
Right:PA Service Request (http://hl7.org/fhir/us/physical-activity/StructureDefinition/pa-servicerequest)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest' vs 'http://hl7.org/fhir/us/physical-activity/StructureDefinition/pa-servicerequest'
ErrorStructureDefinition.versionValues for version differ: '6.0.0-ballot' vs '1.0.0-ballot'
InformationStructureDefinition.nameValues for name differ: 'USCoreServiceRequestProfile' vs 'PAServiceRequest'
InformationStructureDefinition.titleValues for title differ: 'US Core ServiceRequest Profile' vs 'PA Service Request'
InformationStructureDefinition.dateValues for date differ: '2022-10-07' vs '2023-03-28T18:30:00+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - Cross-Group Projects' vs 'HL7 International - Patient Care WG'
WarningServiceRequestElements differ in definition: '\-' vs 'Represents orders and referrals for interventions that help to improve or maintain a patient's level of physical activity'
InformationServiceRequest.implicitRulesElement maximum cardinalities differ: '1' vs '0'
WarningServiceRequest.extensionElements differ in short: 'Additional content defined by implementations' vs 'Extension'
WarningServiceRequest.extensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'An Extension'
WarningServiceRequest.modifierExtensionElements differ in short: 'Extensions that cannot be ignored' vs 'Extension'
WarningServiceRequest.modifierExtensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'An Extension'
InformationServiceRequest.modifierExtensionElement maximum cardinalities differ: '2147483647' vs '0'
WarningServiceRequest.intentElements differ in short: 'proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option' vs 'original-order | order | filler-order'
WarningServiceRequest.intentElements differ in comments: 'This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.' vs 'This element is labeled as a modifier because the intent alters when and how the resource is actually applicable. Multiple codes are allowed to support situations where a Task might point to a filler order instead of an original. However, in almost all cases, the intent should be 'original-order' or just 'order'.'
WarningServiceRequest.categoryElements differ in definition for mustSupport: 'true' vs 'false'
InformationServiceRequest.categoryElement minimum cardinalities differ: '0' vs '2'
WarningServiceRequest.priorityElements differ in definition for mustSupport: 'false' vs 'true'
InformationServiceRequest.doNotPerformElement maximum cardinalities differ: '1' vs '0'
WarningServiceRequest.subjectElements differ in short: 'Individual or Entity the service is ordered for' vs 'A reference from one resource to another'
WarningServiceRequest.subjectElements differ in definition: 'On whom or what the service is to be performed. This is usually a human patient, but can also be requested on animals, groups of humans or animals, devices such as dialysis machines, or even locations (typically for environmental scans).' vs 'A reference from one resource to another.'
WarningServiceRequest.requesterElements differ in short: 'Who/what is requesting service' vs 'A reference from one resource to another'
WarningServiceRequest.requesterElements differ in definition: 'The individual who initiated the request and has responsibility for its activation.' vs 'A reference from one resource to another.'
WarningServiceRequest.requesterElements differ in comments: 'This not the dispatcher, but rather who is the authorizer. This element is not intended to handle delegation which would generally be managed through the Provenance resource.' vs 'References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.'
WarningServiceRequest.performerElements differ in short: 'Requested performer' vs 'A reference from one resource to another'
WarningServiceRequest.performerElements differ in definition: 'The desired performer for doing the requested service. For example, the surgeon, dermatopathologist, endoscopist, etc.' vs 'A reference from one resource to another.'
WarningServiceRequest.performerElements differ in comments: 'If multiple performers are present, it is interpreted as a list of *alternative* performers without any preference regardless of order. If order of preference is needed use the [request-performerOrder extension]. Use CareTeam to represent a group of performers (for example, Practitioner A *and* Practitioner B).' vs 'References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.'
WarningServiceRequest.performerElements differ in definition for mustSupport: 'false' vs 'true'
ErrorServiceRequest.performerType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Practitioner], CanonicalType[http://hl7.org/fhir/StructureDefinition/PractitionerRole], CanonicalType[http://hl7.org/fhir/StructureDefinition/Organization], CanonicalType[http://hl7.org/fhir/StructureDefinition/CareTeam], CanonicalType[http://hl7.org/fhir/StructureDefinition/HealthcareService], CanonicalType[http://hl7.org/fhir/StructureDefinition/Patient], CanonicalType[http://hl7.org/fhir/StructureDefinition/Device], CanonicalType[http://hl7.org/fhir/StructureDefinition/RelatedPerson]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/physical-activity/StructureDefinition/reference-rest-or-logical]])([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization], CanonicalType[http://hl7.org/fhir/us/physical-activity/StructureDefinition/pa-relatedperson]])
WarningServiceRequest.reasonCodeElements differ in definition for mustSupport: 'false' vs 'true'
WarningServiceRequest.reasonCode.textElements differ in definition for mustSupport: 'false' vs 'true'
WarningServiceRequest.supportingInfoElements differ in short: 'Additional clinical information' vs 'A reference from one resource to another'
WarningServiceRequest.supportingInfoElements differ in definition: 'Additional clinical information about the patient or specimen that may influence the services or their interpretations. This information includes diagnosis, clinical findings and other observations. In laboratory ordering these are typically referred to as 'ask at order entry questions (AOEs)'. This includes observations explicitly requested by the producer (filler) to provide context or supporting information needed to complete the order. For example, reporting the amount of inspired oxygen for blood gas measurements.' vs 'A reference from one resource to another.'
WarningServiceRequest.supportingInfoElements differ in comments: 'To represent information about how the services are to be delivered use the `instructions` element.' vs 'References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. A variety of resources might provide support for asserting this condition, however at minimum, systems must support the Physical Activity Vital Sign observations.'
InformationServiceRequest.specimenElement maximum cardinalities differ: '2147483647' vs '0'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/ServiceRequest
      .copyrightUsed by permission of HL7 International, all rights reserved Creative Commons License
      • Removed the item 'Used by permission of HL7 International, all rights reserved Creative Commons License'
      .date2022-10-072023-03-28T18:30:00+00:00
      • Values Differ
      .descriptionThis profile sets minimum expectations for recording, searching, and fetching the ServiceRequest resource to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource when using this profile. It provides the floor for standards development for specific use cases.fhirVersion: 4.0.1Represents orders and referrals for interventions that help to improve or maintain a patient's level of physical activity
      • Values Differ
      .experimental
        .fhirVersion4.0.1
          .jurisdiction
            ..jurisdiction[0]urn:iso:std:iso:3166#US
              .kindresource
                .nameUSCoreServiceRequestProfilePAServiceRequest
                • Values Differ
                .publisherHL7 International - Cross-Group ProjectsHL7 International - Patient Care WG
                • Values Differ
                .purpose
                  .statusactive
                    .titleUS Core ServiceRequest ProfilePA Service Request
                    • Values Differ
                    .typeServiceRequest
                      .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequesthttp://hl7.org/fhir/us/physical-activity/StructureDefinition/pa-servicerequest
                      • Values Differ
                      .version6.0.0-ballot1.0.0-ballot
                      • Values Differ

                      Structure

                      NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                      .. ServiceRequest C0..*ServiceRequestA request for a service to be performed
                      C0..*ServiceRequestA request for a service to be performed
                      • Elements differ in definition: '\-' vs 'Represents orders and referrals for interventions that help to improve or maintain a patient's level of physical activity'
                      ... id Σ0..1idLogical id of this artifactΣ0..1idLogical id of this artifact
                        ... meta Σ0..1MetaMetadata about the resourceΣ0..1MetaMetadata about the resource
                          ... implicitRules ?!Σ0..1uriA set of rules under which this content was created?!Σ0..0
                          • Element maximum cardinalities differ: '1' vs '0'
                          ... language 0..1codeLanguage of the resource content
                          Binding: ?? (preferred): A human language.

                          Additional BindingsPurpose
                          ??Max Binding
                          0..1codeLanguage of the resource content
                          Binding: ?? (preferred): A human language.

                          Additional BindingsPurpose
                          ??Max Binding
                            ... text 0..1NarrativeText summary of the resource, for human interpretation0..1NarrativeText summary of the resource, for human interpretation
                              ... contained 0..*ResourceContained, inline Resources
                              0..*ResourceContained, inline Resources
                                ... extension 0..*ExtensionAdditional content defined by implementations
                                0..*ExtensionExtension
                                Slice: Unordered, Open by value:url
                                • Elements differ in short: 'Additional content defined by implementations' vs 'Extension'
                                • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'An Extension'
                                ... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
                                ?!0..0
                                • Elements differ in short: 'Extensions that cannot be ignored' vs 'Extension'
                                • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'An Extension'
                                • Element maximum cardinalities differ: '2147483647' vs '0'
                                ... identifier Σ0..*IdentifierIdentifiers assigned to this order
                                Σ0..*IdentifierIdentifiers assigned to this order
                                  ... instantiatesCanonical Σ0..*canonical(ActivityDefinition | PlanDefinition)Instantiates FHIR protocol or definition
                                  Σ0..*canonical(ActivityDefinition | PlanDefinition)Instantiates FHIR protocol or definition
                                    ... instantiatesUri Σ0..*uriInstantiates external protocol or definition
                                    Σ0..*uriInstantiates external protocol or definition
                                      ... basedOn Σ0..*Reference(CarePlan | ServiceRequest | MedicationRequest)What request fulfills
                                      Σ0..*Reference(CarePlan | ServiceRequest | MedicationRequest)What request fulfills
                                        ... replaces Σ0..*Reference(ServiceRequest)What request replaces
                                        Σ0..*Reference(ServiceRequest)What request replaces
                                          ... requisition Σ0..1IdentifierComposite Request IDΣ0..1IdentifierComposite Request ID
                                            ... status ?!SΣ1..1codedraft | active | on-hold | revoked | completed | entered-in-error | unknown
                                            Binding: ?? (required): The status of a service order.

                                            ?!SΣ1..1codedraft | active | on-hold | revoked | completed | entered-in-error | unknown
                                            Binding: ?? (required): The status of a service order.

                                              ... intent ?!SΣ1..1codeproposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option
                                              Binding: ?? (required): The kind of service request.

                                              ?!SΣ1..1codeoriginal-order | order | filler-order
                                              Binding: ?? (required)
                                              • Elements differ in short: 'proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option' vs 'original-order | order | filler-order'
                                              • Elements differ in comments: 'This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.' vs 'This element is labeled as a modifier because the intent alters when and how the resource is actually applicable. Multiple codes are allowed to support situations where a Task might point to a filler order instead of an original. However, in almost all cases, the intent should be 'original-order' or just 'order'.'
                                              ... Slices for category SΣ0..*CodeableConceptClassification of service
                                              Slice: Unordered, Open by pattern:$this
                                              Binding: ?? (example): Classification of the requested service.


                                              Σ2..*CodeableConceptClassification of service
                                              Slice: Unordered, Open by pattern:$this
                                              Binding: ?? (example): Classification of the requested service.


                                              • Elements differ in definition for mustSupport: 'true' vs 'false'
                                              • Element minimum cardinalities differ: '0' vs '2'
                                              ... priority Σ0..1coderoutine | urgent | asap | stat
                                              Binding: ?? (required): Identifies the level of importance to be assigned to actioning the request.

                                              SΣ0..1coderoutine | urgent | asap | stat
                                              Binding: ?? (required): Identifies the level of importance to be assigned to actioning the request.

                                              • Elements differ in definition for mustSupport: 'false' vs 'true'
                                              ... doNotPerform ?!Σ0..1booleanTrue if service/procedure should not be performed?!Σ0..0
                                              • Element maximum cardinalities differ: '1' vs '0'
                                              ... code SΣ1..1CodeableConceptWhat is being requested/ordered
                                              Binding: ?? (extensible)
                                              SΣ1..1CodeableConceptWhat is being requested/ordered
                                              Binding: ?? (extensible)
                                                ... orderDetail ΣC0..*CodeableConceptAdditional order information
                                                Binding: ?? (example): Codified order entry details which are based on order context.


                                                ΣC0..*CodeableConceptAdditional order information
                                                Binding: ?? (example): Codified order entry details which are based on order context.


                                                  ... quantity[x] Σ0..1Quantity, Ratio, RangeService amountΣ0..1Quantity, Ratio, RangeService amount
                                                    ... subject SΣ1..1Reference(US Core Patient Profile)Individual or Entity the service is ordered forSΣ1..1Reference(US Core Patient Profile)A reference from one resource to another
                                                    • Elements differ in short: 'Individual or Entity the service is ordered for' vs 'A reference from one resource to another'
                                                    • Elements differ in definition: 'On whom or what the service is to be performed. This is usually a human patient, but can also be requested on animals, groups of humans or animals, devices such as dialysis machines, or even locations (typically for environmental scans).' vs 'A reference from one resource to another.'
                                                    ... encounter Σ0..1Reference(Encounter)Encounter in which the request was createdΣ0..1Reference(Encounter)Encounter in which the request was created
                                                      ... occurrence[x] SΣ0..1Period S, dateTime, TimingWhen service should occurSΣ0..1dateTime, Period S, TimingWhen service should occur
                                                      Slice: Unordered, Open by type:$this
                                                        ... asNeeded[x] Σ0..1boolean, CodeableConceptPreconditions for service
                                                        Binding: ?? (example): A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc.

                                                        Σ0..1boolean, CodeableConceptPreconditions for service
                                                        Binding: ?? (example): A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc.

                                                          ... authoredOn SΣ0..1dateTimeDate request signedSΣ0..1dateTimeDate request signed
                                                            ... requester SΣ0..1Reference(US Core Practitioner Profile S | US Core Organization Profile | US Core Patient Profile | PractitionerRole | US Core RelatedPerson Profile | Device)Who/what is requesting serviceSΣ0..1Reference(US Core Practitioner Profile | US Core PractitionerRole Profile)A reference from one resource to another
                                                            • Elements differ in short: 'Who/what is requesting service' vs 'A reference from one resource to another'
                                                            • Elements differ in definition: 'The individual who initiated the request and has responsibility for its activation.' vs 'A reference from one resource to another.'
                                                            • Elements differ in comments: 'This not the dispatcher, but rather who is the authorizer. This element is not intended to handle delegation which would generally be managed through the Provenance resource.' vs 'References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.'
                                                            ... performerType Σ0..1CodeableConceptPerformer role
                                                            Binding: ?? (example): Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.

                                                            Σ0..1CodeableConceptPerformer role
                                                            Binding: ?? (example): Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.

                                                              ... performer Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson)Requested performer
                                                              SΣ0..*Reference(US Core Patient Profile S | US Core Practitioner Profile S | US Core PractitionerRole Profile S | US Core Organization Profile S | PA Related Person)A reference from one resource to another
                                                              • Elements differ in short: 'Requested performer' vs 'A reference from one resource to another'
                                                              • Elements differ in definition: 'The desired performer for doing the requested service. For example, the surgeon, dermatopathologist, endoscopist, etc.' vs 'A reference from one resource to another.'
                                                              • Elements differ in comments: 'If multiple performers are present, it is interpreted as a list of *alternative* performers without any preference regardless of order. If order of preference is needed use the [request-performerOrder extension]. Use CareTeam to represent a group of performers (for example, Practitioner A *and* Practitioner B).' vs 'References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.'
                                                              • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                              • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Practitioner], CanonicalType[http://hl7.org/fhir/StructureDefinition/PractitionerRole], CanonicalType[http://hl7.org/fhir/StructureDefinition/Organization], CanonicalType[http://hl7.org/fhir/StructureDefinition/CareTeam], CanonicalType[http://hl7.org/fhir/StructureDefinition/HealthcareService], CanonicalType[http://hl7.org/fhir/StructureDefinition/Patient], CanonicalType[http://hl7.org/fhir/StructureDefinition/Device], CanonicalType[http://hl7.org/fhir/StructureDefinition/RelatedPerson]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/physical-activity/StructureDefinition/reference-rest-or-logical]])([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization], CanonicalType[http://hl7.org/fhir/us/physical-activity/StructureDefinition/pa-relatedperson]])
                                                              ... locationCode Σ0..*CodeableConceptRequested location
                                                              Binding: ?? (example): A location type where services are delivered.


                                                              Σ0..*CodeableConceptRequested location
                                                              Binding: ?? (example): A location type where services are delivered.


                                                                ... locationReference Σ0..*Reference(Location)Requested location
                                                                Σ0..*Reference(Location)Requested location
                                                                  ... reasonCode Σ0..*CodeableConceptExplanation/Justification for procedure or service
                                                                  Binding: ?? (extensible)
                                                                  SΣ0..*CodeableConceptExplanation/Justification for procedure or service
                                                                  Binding: ?? (extensible)
                                                                  • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                  .... id 0..1stringUnique id for inter-element referencing0..1stringUnique 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
                                                                      .... coding Σ0..*CodingCode defined by a terminology system
                                                                      Σ0..*CodingCode defined by a terminology system
                                                                        .... text Σ0..1stringPlain text representation of the conceptSΣ0..1stringPlain text representation of the concept
                                                                        • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                        ... reasonReference Σ0..*Reference(US Core Condition Encounter Diagnosis Profile | US Core Condition Problems and Health Concerns Profile | US Core DiagnosticReport Profile for Report and Note exchange | US Core DiagnosticReport Profile for Laboratory Results Reporting | US Core DocumentReference Profile | US Core Laboratory Result Observation Profile | US Core Observation Pregnancy Status Profile | US Core Observation Pregnancy Intent Profile | US Core Observation Occupation Profile | US Core Respiratory Rate Profile | US Core Simple Observation Profile | US Core Heart Rate Profile | US Core Smoking Status Observation Profile | US Core Observation Screening Assessment Profile | US Core Observation Clinical Result Profile | US Core Vital Signs Profile)Explanation/Justification for service or service
                                                                        Σ0..*Reference(Condition | Observation | DiagnosticReport | DocumentReference)Explanation/Justification for service or service
                                                                        Slice: Unordered, Open by profile:resolve()
                                                                          ... insurance 0..*Reference(Coverage | ClaimResponse)Associated insurance coverage
                                                                          0..*Reference(Coverage | ClaimResponse)Associated insurance coverage
                                                                            ... supportingInfo 0..*Reference(Resource)Additional clinical information
                                                                            0..*Reference(Resource)A reference from one resource to another
                                                                            Slice: Unordered, Open by profile:resolve()
                                                                            • Elements differ in short: 'Additional clinical information' vs 'A reference from one resource to another'
                                                                            • Elements differ in definition: 'Additional clinical information about the patient or specimen that may influence the services or their interpretations. This information includes diagnosis, clinical findings and other observations. In laboratory ordering these are typically referred to as "ask at order entry questions (AOEs)". This includes observations explicitly requested by the producer (filler) to provide context or supporting information needed to complete the order. For example, reporting the amount of inspired oxygen for blood gas measurements.' vs 'A reference from one resource to another.'
                                                                            • Elements differ in comments: 'To represent information about how the services are to be delivered use the `instructions` element.' vs 'References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. A variety of resources might provide support for asserting this condition, however at minimum, systems must support the Physical Activity Vital Sign observations.'
                                                                            ... specimen Σ0..*Reference(Specimen)Procedure Samples
                                                                            Σ0..0
                                                                            • Element maximum cardinalities differ: '2147483647' vs '0'
                                                                            ... bodySite Σ0..*CodeableConceptLocation on Body
                                                                            Binding: ?? (example): Codes describing anatomical locations. May include laterality.


                                                                            Σ0..*CodeableConceptLocation on Body
                                                                            Binding: ?? (example): Codes describing anatomical locations. May include laterality.


                                                                              ... note 0..*AnnotationComments
                                                                              0..*AnnotationComments
                                                                                ... patientInstruction Σ0..1stringPatient or consumer-oriented instructionsΣ0..1stringPatient or consumer-oriented instructions
                                                                                  ... relevantHistory 0..*Reference(Provenance)Request provenance
                                                                                  0..*Reference(Provenance)Request provenance

                                                                                    doco Documentation for this format