request - FHIR v5.0.0

This page is part of the FHIR Specification (v5.0.0: R5 - STU ). This is the current published version in it's permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B

12.3.2 12.4.2 Pattern request - Analysis

FHIR Infrastructure icon

Maturity Level : 1

Informative

Detailed Cross Analysis for the request.

12.3.2.1 12.4.2.1 Mappings

~~Contract Contract.status : code [0..1] Minimum Cardinality Violation (pattern = 1, resource = 0) Cardinality Problem.~~ ~~CarePlan.activity.detail.doNotPerform~~ ~~Appointment.serviceType~~ ~~Contract Contract.issued : dateTime [0..1] Contract.term.issued : dateTime [0..1] Names are different.~~ ~~Contract Contract.signer.party : Reference [1..1] Names are different.~~ Request.reasonCode Request.reasonCode : CodeableConcept [0..*] Resource Matches Issues Tasks Status Notes Appointment Appointment.reasonCode : CodeableConcept [0..*] CarePlan CarePlan.activity.detail.reasonCode : CodeableConcept [0..*] ~~DeviceRequest DeviceRequest.reasonCode : CodeableConcept [0..*] MedicationRequest MedicationRequest.reasonCode : CodeableConcept [0..*]~~ ~~RequestGroup.reasonCode : CodeableConcept [0..*]~~ ~~ServiceRequest~~ ~~ServiceRequest.reasonCode~~ ~~SupplyRequest SupplyRequest.reasonCode : CodeableConcept [0..*]~~

Request.identifier

Request.identifier : Identifier [0..*]

Resource

Matches

Issues

Tasks

Status

Notes

Appointment

Appointment.identifier : Identifier [0..*]

identifier does not contain the recommended logical text for short (Pattern: Business Identifier for appointment; ; Resource: External Ids for this item) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this appointment by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: This records identifiers associated with this appointment concern that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation).) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: The identifier.type element is used to distinguish between the identifiers assigned by the requester/placer and the performer/filler. Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: ) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the appointment as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: ) - no reason provided

AppointmentResponse

AppointmentResponse.identifier : Identifier [0..*]

identifier does not contain the recommended logical text for short (Pattern: Business Identifier for appointment response; ; Resource: External Ids for this item) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this appointment response by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: This records identifiers associated with this appointment response concern that are defined by business processes and/ or used to refer to it when a direct URL reference to the resource itself is not appropriate.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: The identifier.type element is used to distinguish between the identifiers assigned by the requester/placer and the performer/filler. Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: ) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the appointment response as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: ) - no reason provided

CarePlan

CarePlan.identifier : Identifier [0..*]

identifier does not contain the recommended logical text for short (Pattern: Business Identifier for care plan; ; Resource: External Ids for this plan) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this care plan by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: Business identifiers assigned to this care plan by the performer or other systems which remain constant as the resource is updated and propagates from server to server.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: The identifier.type element is used to distinguish between the identifiers assigned by the requester/placer and the performer/filler. Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.) - no reason provided

Claim

Claim.identifier : Identifier [0..*]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this claim by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: A unique identifier assigned to this claim.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: The identifier.type element is used to distinguish between the identifiers assigned by the requester/placer and the performer/filler. Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: ) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the claim as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: Allows claims to be distinguished and referenced.) - no reason provided

Claim.insurance.identifier : Identifier [0..1]

Maximum Cardinality differs (Pattern: *; ; Resource: 1) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided identifier does not contain the recommended logical text for short (Pattern: Business Identifier for claim; ; Resource: Pre-assigned Claim number) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this claim by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: The business identifier to be used when the claim is sent for adjudication against this insurance policy.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: The identifier.type element is used to distinguish between the identifiers assigned by the requester/placer and the performer/filler. Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: Only required in jurisdictions where insurers, rather than the provider, are required to send claims to insurers that appear after them in the list. This element is not required when 'subrogation=true'.) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the claim as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: This will be the claim number should it be necessary to create this claim in the future. This is provided so that payors may forward claims to other payors in the Coordination of Benefit for adjudication rather than the provider being required to initiate each adjudication.) - no reason provided

Cardinality Problem.

CommunicationRequest

CommunicationRequest.identifier : Identifier [0..*]

~~Contract Contract.identifier : Identifier [0..*] Contract.term.identifier :~~

identifier does not contain the recommended logical text for short (Pattern: Business

~~[0..1]~~

for communication request; ; Resource: Unique identifier) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this communication request by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: Business identifiers assigned to this communication request by the performer or other systems which remain constant as the resource is updated and propagates from server to server.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: The identifier.type element is used to distinguish between the identifiers assigned by the requester/placer and the performer/filler. Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.) - no reason provided

CoverageEligibilityRequest

CoverageEligibilityRequest.identifier : Identifier [0..*]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided identifier does not contain the recommended logical text for short (Pattern: Business Identifier for coverage eligibility request; ; Resource: Business Identifier for coverage eligiblity request) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this coverage eligibility request by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: A unique identifier assigned to this coverage eligiblity request.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: The identifier.type element is used to distinguish between the identifiers assigned by the requester/placer and the performer/filler. Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: ) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the coverage eligibility request as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: Allows coverage eligibility requests to be distinguished and referenced.) - no reason provided

DeviceRequest

DeviceRequest.identifier : Identifier [0..*]

identifier does not contain the recommended logical text for short (Pattern: Business Identifier for device request; ; Resource: External Request identifier) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this device request by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: Identifiers assigned to this order by the orderer or by the receiver.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: The identifier.type element is used to distinguish between the identifiers assigned by the requester/placer and the performer/filler. Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: ) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the device request as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: ) - no reason provided

EnrollmentRequest

EnrollmentRequest.identifier : Identifier [0..*]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided identifier does not contain the recommended logical text for short (Pattern: Business Identifier for enrollment request; ; Resource: Business Identifier) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this enrollment request by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: The Response business identifier.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: The identifier.type element is used to distinguish between the identifiers assigned by the requester/placer and the performer/filler. Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: ) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the enrollment request as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: ) - no reason provided

ImmunizationRecommendation

ImmunizationRecommendation.identifier : Identifier [0..*]

identifier does not contain the recommended logical text for short (Pattern: Business Identifier for immunization recommendation; ; Resource: Business identifier) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this immunization recommendation by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: A unique identifier assigned to this particular recommendation record.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: The identifier.type element is used to distinguish between the identifiers assigned by the requester/placer and the performer/filler. Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: ) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the immunization recommendation as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: ) - no reason provided

MedicationRequest

MedicationRequest.identifier : Identifier [0..*]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided identifier does not contain the recommended logical text for short (Pattern: Business Identifier for medication request; ; Resource: External ids for this request) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this medication request by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: Identifiers associated with this medication request that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. They are business identifiers assigned to this resource by the performer or other systems and remain constant as the resource is updated and propagates from server to server.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: The identifier.type element is used to distinguish between the identifiers assigned by the requester/placer and the performer/filler. Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: This is a business identifier, not a resource identifier.) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the medication request as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: ) - no reason provided

NutritionOrder

NutritionOrder.identifier : Identifier [0..*]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided identifier does not contain the recommended logical text for short (Pattern: Business Identifier for nutrition order; ; Resource: Identifiers assigned to this order) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this nutrition order by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: Identifiers assigned to this order by the order sender or by the order receiver.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: The identifier.type element is used to distinguish between the identifiers assigned by the requester/placer and the performer/filler. Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: The Identifier.type element can be to indicate filler vs. placer if needed. This is explained in further detail [here](servicerequest.html#notes).) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the nutrition order as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: ) - no reason provided

~~RequestGroup~~ RequestOrchestration

~~RequestGroup.identifier~~ RequestOrchestration.identifier : Identifier [0..*]

identifier does not contain the recommended logical text for short (Pattern: Business Identifier for request orchestration; ; Resource: Business identifier) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this request orchestration by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: Allows a service to provide a unique, business identifier for the request.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: The identifier.type element is used to distinguish between the identifiers assigned by the requester/placer and the performer/filler. Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: ) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the request orchestration as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: Allows identification of the request as it is known by various participating systems and in a way that remains consistent across servers.) - no reason provided

ServiceRequest

ServiceRequest.identifier : Identifier [0..*]

identifier does not contain the recommended logical text for short (Pattern: Business Identifier for service request; ; Resource: Identifiers assigned to this order) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this service request by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: Identifiers assigned to this order instance by the orderer and/or the receiver and/or order fulfiller.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: The identifier.type element is used to distinguish between the identifiers assigned by the requester/placer and the performer/filler. Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: The identifier.type element is used to distinguish between the identifiers assigned by the orderer (known as the 'Placer' in HL7 V2) and the producer of the observations in response to the order (known as the 'Filler' in HL7 V2). For further discussion and examples see the resource notes section below.) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the service request as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: ) - no reason provided

SupplyRequest

SupplyRequest.identifier : Identifier [0..*]

identifier does not contain the recommended logical text for short (Pattern: Business Identifier for supply request; ; Resource: Business Identifier for SupplyRequest) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this supply request by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: Business identifiers assigned to this SupplyRequest by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: The identifier.type element is used to distinguish between the identifiers assigned by the requester/placer and the performer/filler. Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: The identifier.type element is used to distinguish between the identifiers assigned by the requester/placer and the performer/filler.) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the supply request as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: Allows identification of the request as it is known by various participating systems and in a way that remains consistent across servers.) - no reason provided

Task

Task.identifier : Identifier [0..*]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided identifier does not contain the recommended logical text for short (Pattern: Business Identifier for task; ; Resource: Task Instance Identifier) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this task by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: The business identifier for this task.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: The identifier.type element is used to distinguish between the identifiers assigned by the requester/placer and the performer/filler. Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: ) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the task as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: ) - no reason provided

VisionPrescription

VisionPrescription.identifier : Identifier [0..*]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this vision prescription by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: A unique identifier assigned to this vision prescription.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: The identifier.type element is used to distinguish between the identifiers assigned by the requester/placer and the performer/filler. Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: ) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the vision prescription as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: Allows vision prescriptions to be distinguished and referenced.) - no reason provided

~~Request.instantiatesCanonical~~ Request.basedOn

~~Request.instantiatesCanonical~~ Request.basedOn : ~~canonical(Definition)~~ Reference(Request) [0..*]

Resource

Matches

Issues

Tasks

Status

Notes

~~CarePlan~~ Appointment

~~CarePlan.instantiatesCanonical : canonical [0..*] CarePlan.activity.detail.instantiatesCanonical~~ Appointment.basedOn : ~~canonical~~ Reference [0..*]

Resource does not support types that are part of the pattern (Pattern: Reference(Request)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(CarePlan,DeviceRequest,MedicationRequest,ServiceRequest)) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided basedOn does not contain the recommended logical text for short (Pattern: Fulfills plan, proposal or order; ; Resource: The request this appointment is allocated to assess) - no reason provided basedOn does not contain the recommended logical text for definition (Pattern: A higher-level request resource (i.e. a plan, proposal or order) that is fulfilled in whole or in part by this appointment. Authorization from the 'basedOn' request flows through to the referencing appointment.; ; Resource: The request this appointment is allocated to assess (e.g. incoming referral or procedure request).) - no reason provided basedOn does not contain the recommended logical text for comments (Pattern: basedOn represents the 'authorization' chain for an action, not the 'reason for action'. For example, an order might be placed on hold under the authorization for a surgery. However the 'reason' for placing the hold is "to avoid interaction with anesthesia medications" .; ; Resource: ) - no reason provided basedOn does not contain the recommended logical text for requirements (Pattern: Allows tracing of authorization for the request and tracking whether proposals/recommendations were acted upon.; ; Resource: ) - no reason provided

Type Mismatch.

~~DeviceRequest~~ AppointmentResponse

~~DeviceRequest.instantiatesCanonical~~ AppointmentResponse.appointment : ~~canonical [0..*]~~ Reference [1..1]

Minimum Cardinality differs (Pattern: 0; ; Resource: 1) - no reason provided Maximum Cardinality differs (Pattern: *; ; Resource: 1) - no reason provided Resource does not support types that are part of the pattern (Pattern: Reference(Request)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(Appointment)) - no reason provided basedOn does not contain the recommended logical text for short (Pattern: Fulfills plan, proposal or order; ; Resource: Appointment this response relates to) - no reason provided basedOn does not contain the recommended logical text for definition (Pattern: A higher-level request resource (i.e. a plan, proposal or order) that is fulfilled in whole or in part by this appointment response. Authorization from the 'basedOn' request flows through to the referencing appointment response.; ; Resource: Appointment that this response is replying to.) - no reason provided basedOn does not contain the recommended logical text for comments (Pattern: basedOn represents the 'authorization' chain for an action, not the 'reason for action'. For example, an order might be placed on hold under the authorization for a surgery. However the 'reason' for placing the hold is "to avoid interaction with anesthesia medications" .; ; Resource: ) - no reason provided basedOn does not contain the recommended logical text for requirements (Pattern: Allows tracing of authorization for the request and tracking whether proposals/recommendations were acted upon.; ; Resource: ) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

~~NutritionOrder~~ CarePlan

~~NutritionOrder.instantiatesCanonical~~ CarePlan.basedOn : ~~canonical~~ Reference [0..*]

Resource does not support types that are part of the pattern (Pattern: Reference(Request)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(CarePlan,ServiceRequest,RequestOrchestration,NutritionOrder)) - no reason provided basedOn does not contain the recommended logical text for definition (Pattern: A higher-level request resource (i.e. a plan, proposal or order) that is fulfilled in whole or in part by this care plan. Authorization from the 'basedOn' request flows through to the referencing care plan.; ; Resource: A higher-level request resource (i.e. a plan, proposal or order) that is fulfilled in whole or in part by this care plan.) - no reason provided basedOn does not contain the recommended logical text for comments (Pattern: basedOn represents the 'authorization' chain for an action, not the 'reason for action'. For example, an order might be placed on hold under the authorization for a surgery. However the 'reason' for placing the hold is "to avoid interaction with anesthesia medications" .; ; Resource: ) - no reason provided basedOn does not contain the recommended logical text for requirements (Pattern: Allows tracing of authorization for the request and tracking whether proposals/recommendations were acted upon.; ; Resource: Allows tracing of the care plan and tracking whether proposals/recommendations were acted upon.) - no reason provided

Type Mismatch.

~~RequestGroup~~ CommunicationRequest

~~RequestGroup.instantiatesCanonical~~ CommunicationRequest.basedOn : ~~canonical~~ Reference [0..*]

Type Mismatch.

~~ServiceRequest~~ DeviceRequest

~~ServiceRequest.instantiatesCanonical~~ DeviceRequest.basedOn : ~~canonical~~ Reference [0..*]

Type Mismatch.

~~Task~~ MedicationRequest

~~Task.instantiatesCanonical~~ MedicationRequest.basedOn : ~~canonical [0..1]~~ Reference [0..*]

Resource does not support types that are part of the pattern (Pattern: Reference(Request)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(CarePlan,MedicationRequest,ServiceRequest,ImmunizationRecommendation)) - no reason provided basedOn does not contain the recommended logical text for short (Pattern: Fulfills plan, proposal or order; ; Resource: A plan or request that is fulfilled in whole or in part by this medication request) - no reason provided basedOn does not contain the recommended logical text for definition (Pattern: A higher-level request resource (i.e. a plan, proposal or order) that is fulfilled in whole or in part by this medication request. Authorization from the 'basedOn' request flows through to the referencing medication request.; ; Resource: A plan or request that is fulfilled in whole or in part by this medication request.) - no reason provided basedOn does not contain the recommended logical text for comments (Pattern: basedOn represents the 'authorization' chain for an action, not the 'reason for action'. For example, an order might be placed on hold under the authorization for a surgery. However the 'reason' for placing the hold is "to avoid interaction with anesthesia medications" .; ; Resource: ) - no reason provided basedOn does not contain the recommended logical text for requirements (Pattern: Allows tracing of authorization for the request and tracking whether proposals/recommendations were acted upon.; ; Resource: ) - no reason provided

Type Mismatch.

~~Request.instantiatesUri~~ NutritionOrder

~~Request.instantiatesUri~~

NutritionOrder.basedOn : ~~uri~~ Reference [0..*]

does not support types that are part of the pattern (Pattern: Reference(Request)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(CarePlan,NutritionOrder,ServiceRequest)) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided basedOn does not contain the recommended logical text for short (Pattern: Fulfills plan, proposal or order; ; Resource: What this order fulfills) - no reason provided basedOn does not contain the recommended logical text for definition (Pattern: A higher-level request resource (i.e. a plan, proposal or order) that is fulfilled in whole or in part by this nutrition order. Authorization from the 'basedOn' request flows through to the referencing nutrition order.; ; Resource: A plan or request that is fulfilled in whole or in part by this nutrition order.) - no reason provided basedOn does not contain the recommended logical text for comments (Pattern: basedOn represents the 'authorization' chain for an action, not the 'reason for action'. For example, an order might be placed on hold under the authorization for a surgery. However the 'reason' for placing the hold is "to avoid interaction with anesthesia medications" .; ; Resource: ) - no reason provided basedOn does not contain the recommended logical text for requirements (Pattern: Allows tracing of authorization for the request and tracking whether proposals/recommendations were acted upon.; ; Resource: ) - no reason provided

~~Matches~~

~~Issues~~ Type Mismatch.

~~Tasks~~ ~~Status~~

~~Notes~~

~~CarePlan~~ RequestOrchestration

~~CarePlan.instantiatesUri : uri [0..*] CarePlan.activity.detail.instantiatesUri~~ RequestOrchestration.basedOn : ~~uri~~ Reference [0..*]

Resource does not support types that are part of the pattern (Pattern: Reference(Request)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(Resource)) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided basedOn does not contain the recommended logical text for short (Pattern: Fulfills plan, proposal or order; ; Resource: Fulfills plan, proposal, or order) - no reason provided basedOn does not contain the recommended logical text for definition (Pattern: A higher-level request resource (i.e. a plan, proposal or order) that is fulfilled in whole or in part by this request orchestration. Authorization from the 'basedOn' request flows through to the referencing request orchestration.; ; Resource: A plan, proposal or order that is fulfilled in whole or in part by this request.) - no reason provided basedOn does not contain the recommended logical text for comments (Pattern: basedOn represents the 'authorization' chain for an action, not the 'reason for action'. For example, an order might be placed on hold under the authorization for a surgery. However the 'reason' for placing the hold is "to avoid interaction with anesthesia medications" .; ; Resource: ) - no reason provided

Type Mismatch.

~~DeviceRequest~~ ServiceRequest

~~DeviceRequest.instantiatesUri~~ ServiceRequest.basedOn : ~~uri~~ Reference [0..*]

Type Mismatch.

~~NutritionOrder~~ SupplyRequest

~~NutritionOrder.instantiatesUri~~ SupplyRequest.basedOn : ~~uri~~ Reference [0..*]

Type Mismatch.

~~RequestGroup~~ Task

~~RequestGroup.instantiatesUri~~ Task.basedOn : ~~uri~~ Reference [0..*]

Resource does not support types that are part of the pattern (Pattern: Reference(Request)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(Resource)) - no reason provided basedOn does not contain the recommended logical text for short (Pattern: Fulfills plan, proposal or order; ; Resource: Request fulfilled by this task) - no reason provided basedOn does not contain the recommended logical text for definition (Pattern: A higher-level request resource (i.e. a plan, proposal or order) that is fulfilled in whole or in part by this task. Authorization from the 'basedOn' request flows through to the referencing task.; ; Resource: BasedOn refers to a higher-level authorization that triggered the creation of the task. It references a "request" resource such as a ServiceRequest, MedicationRequest, CarePlan, etc. which is distinct from the "request" resource the task is seeking to fulfill. This latter resource is referenced by focus. For example, based on a CarePlan (= basedOn), a task is created to fulfill a ServiceRequest ( = focus ) to collect a specimen from a patient.) - no reason provided basedOn does not contain the recommended logical text for comments (Pattern: basedOn represents the 'authorization' chain for an action, not the 'reason for action'. For example, an order might be placed on hold under the authorization for a surgery. However the 'reason' for placing the hold is "to avoid interaction with anesthesia medications" .; ; Resource: Task.basedOn is never the same as Task.focus. Task.basedOn will typically not be present for 'please fulfill' Tasks as a distinct authorization is rarely needed to request fulfillment. If the Task is seeking fulfillment of an order, the order to be fulfilled is always communicated using `focus`, never basedOn. However, authorization may be needed to perform other types of Task actions. As an example of when both would be present, a Task seeking suspension of a prescription might have a Task.basedOn pointing to the ServiceRequest ordering surgery (which is the driver for suspending the MedicationRequest - which would be the Task.focus).) - no reason provided basedOn does not contain the recommended logical text for requirements (Pattern: Allows tracing of authorization for the request and tracking whether proposals/recommendations were acted upon.; ; Resource: ) - no reason provided

Type Mismatch.

~~ServiceRequest~~ Transport

~~ServiceRequest.instantiatesUri~~ Transport.basedOn : ~~uri~~ Reference [0..*]

Resource does not support types that are part of the pattern (Pattern: Reference(Request)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(Resource)) - no reason provided basedOn does not contain the recommended logical text for short (Pattern: Fulfills plan, proposal or order; ; Resource: Request fulfilled by this transport) - no reason provided basedOn does not contain the recommended logical text for definition (Pattern: A higher-level request resource (i.e. a plan, proposal or order) that is fulfilled in whole or in part by this transport. Authorization from the 'basedOn' request flows through to the referencing transport.; ; Resource: BasedOn refers to a higher-level authorization that triggered the creation of the transport. It references a "request" resource such as a ServiceRequest or Transport, which is distinct from the "request" resource the Transport is seeking to fulfill. This latter resource is referenced by FocusOn. For example, based on a ServiceRequest (= BasedOn), a transport is created to fulfill a procedureRequest ( = FocusOn ) to transport a specimen to the lab.) - no reason provided basedOn does not contain the recommended logical text for comments (Pattern: basedOn represents the 'authorization' chain for an action, not the 'reason for action'. For example, an order might be placed on hold under the authorization for a surgery. However the 'reason' for placing the hold is "to avoid interaction with anesthesia medications" .; ; Resource: ) - no reason provided basedOn does not contain the recommended logical text for requirements (Pattern: Allows tracing of authorization for the request and tracking whether proposals/recommendations were acted upon.; ; Resource: ) - no reason provided

Type Mismatch.

~~Request.basedOn~~ Request.replaces

~~Request.basedOn~~ Request.replaces : Reference(Request) [0..*]

Resource

Matches

Issues

Tasks

Status

Notes

Appointment

~~Appointment.basedOn~~ Appointment.replaces : Reference [0..*]

Resource does not support types that are part of the pattern (Pattern: Reference(Request)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(Appointment)) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided replaces does not contain the recommended logical text for short (Pattern: Request(s) replaced by this appointment; ; Resource: Appointment replaced by this Appointment) - no reason provided replaces does not contain the recommended logical text for definition (Pattern: Completed or terminated request(s) whose function is taken by this new appointment.; ; Resource: Appointment replaced by this Appointment in cases where there is a cancellation, the details of the cancellation can be found in the cancellationReason property (on the referenced resource).) - no reason provided replaces does not contain the recommended logical text for comments (Pattern: The replacement could be because the initial request was immediately rejected (due to an issue) or because the previous request was completed, but the need for the action described by the request remains ongoing.; ; Resource: ) - no reason provided replaces does not contain the recommended logical text for requirements (Pattern: Allows tracing the continuation of a therapy or administrative process instantiated through multiple requests.; ; Resource: ) - no reason provided

Type Mismatch.

~~AppointmentResponse~~ CarePlan

~~AppointmentResponse.appointment~~ CarePlan.replaces : Reference ~~[1..1]~~ [0..*]

~~Names are different.~~ Type Mismatch.

~~CarePlan~~ Claim

~~CarePlan.basedOn~~ Claim.related.claim : Reference ~~[0..*]~~ [0..1]

Maximum Cardinality differs (Pattern: *; ; Resource: 1) - no reason provided Resource does not support types that are part of the pattern (Pattern: Reference(Request)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(Claim)) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided replaces does not contain the recommended logical text for short (Pattern: Request(s) replaced by this claim; ; Resource: Reference to the related claim) - no reason provided replaces does not contain the recommended logical text for definition (Pattern: Completed or terminated request(s) whose function is taken by this new claim.; ; Resource: Reference to a related claim.) - no reason provided replaces does not contain the recommended logical text for comments (Pattern: The replacement could be because the initial request was immediately rejected (due to an issue) or because the previous request was completed, but the need for the action described by the request remains ongoing.; ; Resource: ) - no reason provided replaces does not contain the recommended logical text for requirements (Pattern: Allows tracing the continuation of a therapy or administrative process instantiated through multiple requests.; ; Resource: For workplace or other accidents it is common to relate separate claims arising from the same event.) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

CommunicationRequest

~~CommunicationRequest.basedOn~~ CommunicationRequest.replaces : Reference [0..*]

Type Mismatch.

DeviceRequest

~~DeviceRequest.basedOn~~ DeviceRequest.replaces : Reference [0..*]

Type Mismatch.

MedicationRequest

~~MedicationRequest.basedOn~~ MedicationRequest.priorPrescription : Reference ~~[0..*]~~ [0..1]

Maximum Cardinality differs (Pattern: *; ; Resource: 1) - no reason provided Resource does not support types that are part of the pattern (Pattern: Reference(Request)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(MedicationRequest)) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided replaces does not contain the recommended logical text for short (Pattern: Request(s) replaced by this medication request; ; Resource: Reference to an order/prescription that is being replaced by this MedicationRequest) - no reason provided replaces does not contain the recommended logical text for definition (Pattern: Completed or terminated request(s) whose function is taken by this new medication request.; ; Resource: Reference to an order/prescription that is being replaced by this MedicationRequest.) - no reason provided replaces does not contain the recommended logical text for comments (Pattern: The replacement could be because the initial request was immediately rejected (due to an issue) or because the previous request was completed, but the need for the action described by the request remains ongoing.; ; Resource: ) - no reason provided replaces does not contain the recommended logical text for requirements (Pattern: Allows tracing the continuation of a therapy or administrative process instantiated through multiple requests.; ; Resource: ) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

~~RequestGroup~~ RequestOrchestration

~~RequestGroup.basedOn~~ RequestOrchestration.replaces : Reference [0..*]

Resource does not support types that are part of the pattern (Pattern: Reference(Request)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(Resource)) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided replaces does not contain the recommended logical text for short (Pattern: Request(s) replaced by this request orchestration; ; Resource: Request(s) replaced by this request) - no reason provided replaces does not contain the recommended logical text for definition (Pattern: Completed or terminated request(s) whose function is taken by this new request orchestration.; ; Resource: Completed or terminated request(s) whose function is taken by this new request.) - no reason provided

Type Mismatch.

ServiceRequest

~~ServiceRequest.basedOn~~ ServiceRequest.replaces : Reference [0..*]

Type Mismatch.

Task

~~Task.basedOn~~

Extension task-replaces

Resource does not support types that are part of the pattern (Pattern: Reference(Request)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(Task)) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided replaces does not contain the recommended logical text for short (Pattern: Request(s) replaced by this task; ; Resource: Task(s) replaced by this Task) - no reason provided replaces does not contain the recommended logical text for definition (Pattern: Completed or terminated request(s) whose function is taken by this new task.; ; Resource: Completed or terminated task(s) whose function is taken by this new task.) - no reason provided replaces does not contain the recommended logical text for comments (Pattern: The replacement could be because the initial request was immediately rejected (due to an issue) or because the previous request was completed, but the need for the action described by the request remains ongoing.; ; Resource: The replacement could be because the initial task was immediately rejected (due to an issue) or because the previous task was completed, but the need for the action described by the task remains ongoing.) - no reason provided replaces does not contain the recommended logical text for requirements (Pattern: Allows tracing the continuation of a therapy or administrative process instantiated through multiple requests.; ; Resource: ) - no reason provided

(as an extension)

Type Mismatch.

~~Request.replaces~~ Request.groupIdentifier

~~Request.replaces~~ Request.groupIdentifier : ~~Reference(Request) [0..*]~~ Identifier [0..1]

Resource

Matches

Issues

Tasks

Status

Notes

~~CarePlan CarePlan.replaces : Reference [0..*] Claim Claim.related.claim : Reference [0..1] Names are different.~~ CommunicationRequest

~~CommunicationRequest.replaces~~ CommunicationRequest.groupIdentifier : ~~Reference [0..*]~~ Identifier [0..1]

DeviceRequest

~~DeviceRequest.priorRequest : Reference [0..*] Names are different. MedicationRequest MedicationRequest.priorPrescription~~ DeviceRequest.groupIdentifier : ~~Reference~~ Identifier [0..1]

~~Names~~

groupIdentifier does not contain the recommended logical text for short (Pattern: Composite request this is part of; ; Resource: Identifier of composite request) - no reason provided groupIdentifier does not contain the recommended logical text for definition (Pattern: A shared identifier common to all requests that were authorized more or less simultaneously by a single author, representing the identifier of the requisition, prescription or similar form.; ; Resource: A shared identifier common to multiple independent Request instances that were activated/authorized more or less simultaneously by a single author. The presence of the same identifier on each request ties those requests together and may have business ramifications in terms of reporting of results, billing, etc. E.g. a requisition number shared by a set of lab tests ordered together, or a prescription number shared by all meds ordered at one time.) - no reason provided groupIdentifier does not contain the recommended logical text for comments (Pattern: Requests

different. RequestGroup RequestGroup.replaces : Reference [0..*] ServiceRequest ServiceRequest.replaces : Reference [0..*] Task Request.replaces : Reference(Request) [0..*] => Extension task-replaces : Reference [0..*]

linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.; ; Resource: ) - no reason provided groupIdentifier does not contain the recommended logical text for requirements (Pattern: Some business processes need to know if multiple items were ordered as part of the same "prescription" or "requisition" for billing or other purposes.; ; Resource: ) - no reason provided

~~(as an extension)~~ ~~Request.groupIdentifier Request.groupIdentifier : Identifier [0..1]~~

~~Resource~~ ~~Matches~~

~~Issues~~ ~~Tasks~~

~~Status~~ ~~Notes~~

~~CommunicationRequest~~ MedicationRequest

~~CommunicationRequest.groupIdentifier~~ MedicationRequest.groupIdentifier : Identifier [0..1]

groupIdentifier does not contain the recommended logical text for definition (Pattern: A shared identifier common to all requests that were authorized more or less simultaneously by a single author, representing the identifier of the requisition, prescription or similar form.; ; Resource: A shared identifier common to multiple independent Request instances that were activated/authorized more or less simultaneously by a single author. The presence of the same identifier on each request ties those requests together and may have business ramifications in terms of reporting of results, billing, etc. E.g. a requisition number shared by a set of lab tests ordered together, or a prescription number shared by all meds ordered at one time.) - no reason provided groupIdentifier does not contain the recommended logical text for comments (Pattern: Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.; ; Resource: ) - no reason provided groupIdentifier does not contain the recommended logical text for requirements (Pattern: Some business processes need to know if multiple items were ordered as part of the same "prescription" or "requisition" for billing or other purposes.; ; Resource: Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.) - no reason provided

~~DeviceRequest~~ NutritionOrder

~~DeviceRequest.groupIdentifier~~ NutritionOrder.groupIdentifier : Identifier [0..1]

groupIdentifier does not contain the recommended logical text for short (Pattern: Composite request this is part of; ; Resource: Composite Request ID) - no reason provided groupIdentifier does not contain the recommended logical text for definition (Pattern: A shared identifier common to all requests that were authorized more or less simultaneously by a single author, representing the identifier of the requisition, prescription or similar form.; ; Resource: A shared identifier common to all nutrition orders that were authorized more or less simultaneously by a single author, representing the composite or group identifier.) - no reason provided groupIdentifier does not contain the recommended logical text for comments (Pattern: Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.; ; Resource: ) - no reason provided groupIdentifier does not contain the recommended logical text for requirements (Pattern: Some business processes need to know if multiple items were ordered as part of the same "prescription" or "requisition" for billing or other purposes.; ; Resource: ) - no reason provided

~~MedicationRequest~~ RequestOrchestration

~~MedicationRequest.groupIdentifier~~ RequestOrchestration.groupIdentifier : Identifier [0..1]

~~RequestGroup~~ ServiceRequest

~~RequestGroup.groupIdentifier~~ ServiceRequest.requisition : Identifier [0..1]

groupIdentifier does not contain the recommended logical text for short (Pattern: Composite request this is part of; ; Resource: Composite Request ID) - no reason provided groupIdentifier does not contain the recommended logical text for definition (Pattern: A shared identifier common to all requests that were authorized more or less simultaneously by a single author, representing the identifier of the requisition, prescription or similar form.; ; Resource: A shared identifier common to all service requests that were authorized more or less simultaneously by a single author, representing the composite or group identifier.) - no reason provided groupIdentifier does not contain the recommended logical text for comments (Pattern: Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.; ; Resource: Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.) - no reason provided groupIdentifier does not contain the recommended logical text for requirements (Pattern: Some business processes need to know if multiple items were ordered as part of the same "prescription" or "requisition" for billing or other purposes.; ; Resource: Some business processes need to know if multiple items were ordered as part of the same "requisition" for billing or other purposes.) - no reason provided

Names are different.

~~ServiceRequest~~ Task

~~ServiceRequest.requisition~~ Task.groupIdentifier : Identifier [0..1]

groupIdentifier does not contain the recommended logical text for short (Pattern: Composite request this is part of; ; Resource: Requisition or grouper id) - no reason provided groupIdentifier does not contain the recommended logical text for definition (Pattern: A shared identifier common to all requests that were authorized more or less simultaneously by a single author, representing the identifier of the requisition, prescription or similar form.; ; Resource: A shared identifier common to multiple independent Task and Request instances that were activated/authorized more or less simultaneously by a single author. The presence of the same identifier on each request ties those requests together and may have business ramifications in terms of reporting of results, billing, etc. E.g. a requisition number shared by a set of lab tests ordered together, or a prescription number shared by all meds ordered at one time.) - no reason provided groupIdentifier does not contain the recommended logical text for comments (Pattern: Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.; ; Resource: ) - no reason provided groupIdentifier does not contain the recommended logical text for requirements (Pattern: Some business processes need to know if multiple items were ordered as part of the same "prescription" or "requisition" for billing or other purposes.; ; Resource: Billing and/or reporting can be linked to whether multiple requests were created as a single unit.) - no reason provided

~~Names are different.~~

~~Task~~ Transport

~~Task.groupIdentifier~~ Transport.groupIdentifier : Identifier [0..1]

groupIdentifier does not contain the recommended logical text for short (Pattern: Composite request this is part of; ; Resource: Requisition or grouper id) - no reason provided groupIdentifier does not contain the recommended logical text for definition (Pattern: A shared identifier common to all requests that were authorized more or less simultaneously by a single author, representing the identifier of the requisition, prescription or similar form.; ; Resource: A shared identifier common to multiple independent Request instances that were activated/authorized more or less simultaneously by a single author. The presence of the same identifier on each request ties those requests together and may have business ramifications in terms of reporting of results, billing, etc. E.g. a requisition number shared by a set of lab tests ordered together, or a prescription number shared by all meds ordered at one time.) - no reason provided groupIdentifier does not contain the recommended logical text for comments (Pattern: Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.; ; Resource: ) - no reason provided groupIdentifier does not contain the recommended logical text for requirements (Pattern: Some business processes need to know if multiple items were ordered as part of the same "prescription" or "requisition" for billing or other purposes.; ; Resource: Billing and/or reporting can be linked to whether multiple requests were created as a single unit.) - no reason provided

Request.status

Request.status : code [1..1]

Resource

Matches

Issues

Tasks

Status

Notes

Appointment

Appointment.status : code [1..1]

status does not contain the recommended logical text for short (Pattern: draft | active | on-hold | revoked | completed | entered-in-error | unknown; ; Resource: proposed | pending | booked | arrived | fulfilled | cancelled | noshow | entered-in-error | checked-in | waitlist) - no reason provided status does not contain the recommended logical text for definition (Pattern: The current state of the appointment.; ; Resource: The overall status of the Appointment. Each of the participants has their own participation status which indicates their involvement in the process, however this status indicates the shared status.) - no reason provided status does not contain the recommended logical text for comments (Pattern: The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, completed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding]](s) or using the]] resource. A nominal state-transition diagram can be found in the] documentation Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. A status of 'active' when doNotPerform is true means that the request to not perform is currently in force. A status of completed for a "doNotPerform" request indicates that the period of non-performance is now satisfied and the request no longer holds.; ; Resource: If the Appointment's status is "cancelled" then all participants are expected to have their calendars released for the appointment period, and as such any Slots that were marked as BUSY can be re-set to FREE. This element is labeled as a modifier because the status contains the code entered-in-error that mark the Appointment as not currently valid.) - no reason provided

AppointmentResponse

AppointmentResponse.participantStatus : code [1..1]

status does not contain the recommended logical text for short (Pattern: draft | active | on-hold | revoked | completed | entered-in-error | unknown; ; Resource: accepted | declined | tentative | needs-action | entered-in-error) - no reason provided status does not contain the recommended logical text for definition (Pattern: The current state of the appointment response.; ; Resource: Participation status of the participant. When the status is declined or tentative if the start/end times are different to the appointment, then these times should be interpreted as a requested time change. When the status is accepted, the times can either be the time of the appointment (as a confirmation of the time) or can be empty.) - no reason provided status does not contain the recommended logical text for comments (Pattern: The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, completed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding]](s) or using the]] resource. A nominal state-transition diagram can be found in the] documentation Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. A status of 'active' when doNotPerform is true means that the request to not perform is currently in force. A status of completed for a "doNotPerform" request indicates that the period of non-performance is now satisfied and the request no longer holds.; ; Resource: This element is labeled as a modifier because the status contains the code entered-in-error that marks the participant as not currently valid.) - no reason provided

Names are different.

CarePlan

CarePlan.status : code [1..1]

~~CarePlan.activity.detail.status :~~

status does not contain the recommended logical text for definition (Pattern: The current state of the care plan.; ; Resource: Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record.) - no reason provided status does not contain the recommended logical text for comments (Pattern: The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, completed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding]](s) or using the]] resource. A nominal state-transition diagram can be found in the] documentation Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. A status of 'active' when doNotPerform is true means that the request to not perform is currently in force. A status of completed for a "doNotPerform" request indicates that the period of non-performance is now satisfied and the request no longer holds.; ; Resource: The unknown

~~[1..1]~~

is not to be used to convey other statuses. The unknown code should be used when one of the statuses applies, but the authoring system doesn't know the current state of the care plan. This element is labeled as a modifier because the status contains the code entered-in-error that marks the plan as not currently valid.) - no reason provided

Claim

Claim.status : code [1..1]

status does not contain the recommended logical text for short (Pattern: draft | active | on-hold | revoked | completed | entered-in-error | unknown; ; Resource: active | cancelled | draft | entered-in-error) - no reason provided status does not contain the recommended logical text for definition (Pattern: The current state of the claim.; ; Resource: The status of the resource instance.) - no reason provided status does not contain the recommended logical text for comments (Pattern: The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, completed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding]](s) or using the]] resource. A nominal state-transition diagram can be found in the] documentation Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. A status of 'active' when doNotPerform is true means that the request to not perform is currently in force. A status of completed for a "doNotPerform" request indicates that the period of non-performance is now satisfied and the request no longer holds.; ; Resource: This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.) - no reason provided

CommunicationRequest

CommunicationRequest.status : code [1..1]

status does not contain the recommended logical text for definition (Pattern: The current state of the communication request.; ; Resource: The status of the proposal or order.) - no reason provided status does not contain the recommended logical text for comments (Pattern: The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, completed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding]](s) or using the]] resource. A nominal state-transition diagram can be found in the] documentation Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. A status of 'active' when doNotPerform is true means that the request to not perform is currently in force. A status of completed for a "doNotPerform" request indicates that the period of non-performance is now satisfied and the request no longer holds.; ; Resource: ) - no reason provided

CoverageEligibilityRequest

CoverageEligibilityRequest.status : code [1..1]

status does not contain the recommended logical text for short (Pattern: draft | active | on-hold | revoked | completed | entered-in-error | unknown; ; Resource: active | cancelled | draft | entered-in-error) - no reason provided status does not contain the recommended logical text for definition (Pattern: The current state of the coverage eligibility request.; ; Resource: The status of the resource instance.) - no reason provided status does not contain the recommended logical text for comments (Pattern: The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, completed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding]](s) or using the]] resource. A nominal state-transition diagram can be found in the] documentation Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. A status of 'active' when doNotPerform is true means that the request to not perform is currently in force. A status of completed for a "doNotPerform" request indicates that the period of non-performance is now satisfied and the request no longer holds.; ; Resource: This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.) - no reason provided

DeviceRequest

DeviceRequest.status : code [0..1]

~~Violation (pattern = 1, resource =~~

differs (Pattern: 1; ; Resource:

- no reason provided status does not contain the recommended logical text for definition (Pattern: The current state of the device request.; ; Resource: The status of the request.) - no reason provided status does not contain the recommended logical text for comments (Pattern: The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, completed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding]](s) or using the]] resource. A nominal state-transition diagram can be found in the] documentation Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. A status of 'active' when doNotPerform is true means that the request to not perform is currently in force. A status of completed for a "doNotPerform" request indicates that the period of non-performance is now satisfied and the request no longer holds.; ; Resource: This element is labeled as a modifier because the status contains the codes revoked and entered-in-error that mark the request as not currently valid.) - no reason provided

Cardinality Problem.

EnrollmentRequest

EnrollmentRequest.status : code [0..1]

~~Violation (pattern = 1, resource =~~

differs (Pattern: 1; ; Resource:

- no reason provided status does not contain the recommended logical text for short (Pattern: draft | active | on-hold | revoked | completed | entered-in-error | unknown; ; Resource: active | cancelled | draft | entered-in-error) - no reason provided status does not contain the recommended logical text for definition (Pattern: The current state of the enrollment request.; ; Resource: The status of the resource instance.) - no reason provided status does not contain the recommended logical text for comments (Pattern: The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, completed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding]](s) or using the]] resource. A nominal state-transition diagram can be found in the] documentation Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. A status of 'active' when doNotPerform is true means that the request to not perform is currently in force. A status of completed for a "doNotPerform" request indicates that the period of non-performance is now satisfied and the request no longer holds.; ; Resource: This element is labeled as a modifier because the status contains codes that mark the request as not currently valid.) - no reason provided

Cardinality Problem.

MedicationRequest

MedicationRequest.status : code [1..1]

status does not contain the recommended logical text for short (Pattern: draft | active | on-hold | revoked | completed | entered-in-error | unknown; ; Resource: active | on-hold | ended | stopped | completed | cancelled | entered-in-error | draft | unknown) - no reason provided status does not contain the recommended logical text for definition (Pattern: The current state of the medication request.; ; Resource: A code specifying the current state of the order. Generally, this will be active or completed state.) - no reason provided status does not contain the recommended logical text for comments (Pattern: The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, completed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding]](s) or using the]] resource. A nominal state-transition diagram can be found in the] documentation Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. A status of 'active' when doNotPerform is true means that the request to not perform is currently in force. A status of completed for a "doNotPerform" request indicates that the period of non-performance is now satisfied and the request no longer holds.; ; Resource: This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. Clinical decision support systems should take the status into account when determining which medications to include in their algorithms.) - no reason provided

NutritionOrder

NutritionOrder.status : code [1..1]

status does not contain the recommended logical text for definition (Pattern: The current state of the nutrition order.; ; Resource: The workflow status of the nutrition order/request.) - no reason provided status does not contain the recommended logical text for comments (Pattern: The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, completed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding]](s) or using the]] resource. A nominal state-transition diagram can be found in the] documentation Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. A status of 'active' when doNotPerform is true means that the request to not perform is currently in force. A status of completed for a "doNotPerform" request indicates that the period of non-performance is now satisfied and the request no longer holds.; ; Resource: Typically the system placing the order sets the status to "requested". Thereafter, the order is maintained by the receiver that updates the status as the request is handled. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.) - no reason provided

~~RequestGroup~~ RequestOrchestration

~~RequestGroup.status~~ RequestOrchestration.status : code [1..1]

status does not contain the recommended logical text for definition (Pattern: The current state of the request orchestration.; ; Resource: The current state of the request. For request orchestrations, the status reflects the status of all the requests in the orchestration.) - no reason provided status does not contain the recommended logical text for comments (Pattern: The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, completed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding]](s) or using the]] resource. A nominal state-transition diagram can be found in the] documentation Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. A status of 'active' when doNotPerform is true means that the request to not perform is currently in force. A status of completed for a "doNotPerform" request indicates that the period of non-performance is now satisfied and the request no longer holds.; ; Resource: ) - no reason provided

ServiceRequest

ServiceRequest.status : code [1..1]

status does not contain the recommended logical text for definition (Pattern: The current state of the service request.; ; Resource: The status of the order.) - no reason provided status does not contain the recommended logical text for comments (Pattern: The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, completed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding]](s) or using the]] resource. A nominal state-transition diagram can be found in the] documentation Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. A status of 'active' when doNotPerform is true means that the request to not perform is currently in force. A status of completed for a "doNotPerform" request indicates that the period of non-performance is now satisfied and the request no longer holds.; ; Resource: The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, competed, revoked or placed on-hold. States relating to the activities of the performer are reflected on either the corresponding event (see [Event Pattern](event.html) for general discussion) or using the [Task](task.html) resource.) - no reason provided

SupplyRequest

SupplyRequest.status : code [0..1]

~~Violation (pattern = 1, resource =~~

differs (Pattern: 1; ; Resource:

- no reason provided status does not contain the recommended logical text for short (Pattern: draft | active | on-hold | revoked | completed | entered-in-error | unknown; ; Resource: draft | active | suspended +) - no reason provided status does not contain the recommended logical text for definition (Pattern: The current state of the supply request.; ; Resource: Status of the supply request.) - no reason provided status does not contain the recommended logical text for comments (Pattern: The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, completed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding]](s) or using the]] resource. A nominal state-transition diagram can be found in the] documentation Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. A status of 'active' when doNotPerform is true means that the request to not perform is currently in force. A status of completed for a "doNotPerform" request indicates that the period of non-performance is now satisfied and the request no longer holds.; ; Resource: ) - no reason provided

Cardinality Problem.

Task

Task.status : code [1..1]

status does not contain the recommended logical text for short (Pattern: draft | active | on-hold | revoked | completed | entered-in-error | unknown; ; Resource: draft | requested | received | accepted | +) - no reason provided status does not contain the recommended logical text for definition (Pattern: The current state of the task.; ; Resource: The current status of the task.) - no reason provided status does not contain the recommended logical text for comments (Pattern: The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, completed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding]](s) or using the]] resource. A nominal state-transition diagram can be found in the] documentation Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. A status of 'active' when doNotPerform is true means that the request to not perform is currently in force. A status of completed for a "doNotPerform" request indicates that the period of non-performance is now satisfied and the request no longer holds.; ; Resource: ) - no reason provided

VisionPrescription

VisionPrescription.status : code [1..1]

status does not contain the recommended logical text for short (Pattern: draft | active | on-hold | revoked | completed | entered-in-error | unknown; ; Resource: active | cancelled | draft | entered-in-error) - no reason provided status does not contain the recommended logical text for definition (Pattern: The current state of the vision prescription.; ; Resource: The status of the resource instance.) - no reason provided status does not contain the recommended logical text for comments (Pattern: The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, completed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding]](s) or using the]] resource. A nominal state-transition diagram can be found in the] documentation Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. A status of 'active' when doNotPerform is true means that the request to not perform is currently in force. A status of completed for a "doNotPerform" request indicates that the period of non-performance is now satisfied and the request no longer holds.; ; Resource: This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.) - no reason provided

Request.statusReason

Request.statusReason : CodeableConcept [0..1]

Resource

Matches

Issues

Tasks

Status

Notes

~~CarePlan CarePlan.activity.detail.statusReason : CodeableConcept [0..1]~~ CommunicationRequest

CommunicationRequest.statusReason : CodeableConcept [0..1]

statusReason does not contain the recommended logical text for definition (Pattern: Captures the reason for the current state of the communication request.; ; Resource: Captures the reason for the current state of the CommunicationRequest.) - no reason provided statusReason does not contain the recommended logical text for comments (Pattern: This is generally only used for "exception" statuses such as "suspended" or "cancelled". The reason why the communication request was created at all is captured in reasonCode, not here. .; ; Resource: This is generally only used for "exception" statuses such as "on-hold" or "revoked". The reason why the CommunicationRequest was created at all is captured in reasonCode, not here.) - no reason provided

MedicationRequest

MedicationRequest.statusReason : CodeableConcept [0..1]

statusReason does not contain the recommended logical text for definition (Pattern: Captures the reason for the current state of the medication request.; ; Resource: Captures the reason for the current state of the MedicationRequest.) - no reason provided statusReason does not contain the recommended logical text for comments (Pattern: This is generally only used for "exception" statuses such as "suspended" or "cancelled". The reason why the medication request was created at all is captured in reasonCode, not here. .; ; Resource: This is generally only used for "exception" statuses such as "suspended" or "cancelled". The reason why the MedicationRequest was created at all is captured in reasonCode, not here.) - no reason provided

Request.intent

Request.intent : code [1..1]

Resource

Matches

Issues

Tasks

Status

Notes

CarePlan

CarePlan.intent : code [1..1]

intent does not contain the recommended logical text for short (Pattern: proposal | plan | order (immutable); ; Resource: proposal | plan | order | option | directive) - no reason provided intent does not contain the recommended logical text for definition (Pattern: Indicates the level of authority/intentionality associated with the care plan and where the request fits into the workflow chain.; ; Resource: Indicates the level of authority/intentionality associated with the care plan and where the care plan fits into the workflow chain.) - no reason provided intent does not contain the recommended logical text for comments (Pattern: This element is expected to be immutable. E.g. A "proposal" instance should never change to be a "plan" instance or "order" instance. Instead, a new instance 'basedOn' the prior instance should be created with the new 'intent' value. One exception to this is that the granularity of Request.intent is allowed to change. For example, a Request identified as an "order" might later be clarified to be a "filler-order". Or, in rarer cases (to meet recipient constraints), the reverse might also occur. When resources map to this element, they are free to define as many codes as necessary to cover their space and will map to "proposal, plan or order". Can have multiple codes that map to one of these. E.g. "original order", "encoded order", "reflex order" would all map to "order". Expectation is that the set of codes is mutually exclusive or a strict all-encompassing hierarchy.; ; Resource: This element is labeled as a modifier because the intent alters when and how the resource is actually applicable. This element is expected to be immutable. E.g. A "proposal" instance should never change to be a "plan" instance or "order" instance. Instead, a new instance 'basedOn' the prior instance should be created with the new 'intent' value.) - no reason provided

CommunicationRequest

CommunicationRequest.intent : code [1..1]

intent does not contain the recommended logical text for short (Pattern: proposal | plan | order (immutable); ; Resource: proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option) - no reason provided intent does not contain the recommended logical text for definition (Pattern: Indicates the level of authority/intentionality associated with the communication request and where the request fits into the workflow chain.; ; Resource: Indicates the level of authority/intentionality associated with the CommunicationRequest and where the request fits into the workflow chain.) - no reason provided intent does not contain the recommended logical text for comments (Pattern: This element is expected to be immutable. E.g. A "proposal" instance should never change to be a "plan" instance or "order" instance. Instead, a new instance 'basedOn' the prior instance should be created with the new 'intent' value. One exception to this is that the granularity of Request.intent is allowed to change. For example, a Request identified as an "order" might later be clarified to be a "filler-order". Or, in rarer cases (to meet recipient constraints), the reverse might also occur. When resources map to this element, they are free to define as many codes as necessary to cover their space and will map to "proposal, plan or order". Can have multiple codes that map to one of these. E.g. "original order", "encoded order", "reflex order" would all map to "order". Expectation is that the set of codes is mutually exclusive or a strict all-encompassing hierarchy.; ; Resource: This element is expected to be immutable. E.g. A "proposal" instance should never change to be a "plan" instance or "order" instance. Instead, a new instance 'basedOn' the prior instance should be created with the new 'intent' value. One exception to this is that the granularity of CommunicationRequest.intent is allowed to change. For example, a Request identified as an "order" might later be clarified to be a "filler-order". Or, in rarer cases (to meet recipient constraints), the reverse might also occur.) - no reason provided

DeviceRequest

DeviceRequest.intent : code [1..1]

intent does not contain the recommended logical text for short (Pattern: proposal | plan | order (immutable); ; Resource: proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option) - no reason provided intent does not contain the recommended logical text for definition (Pattern: Indicates the level of authority/intentionality associated with the device request and where the request fits into the workflow chain.; ; Resource: Whether the request is a proposal, plan, an original order or a reflex order.) - no reason provided intent does not contain the recommended logical text for comments (Pattern: This element is expected to be immutable. E.g. A "proposal" instance should never change to be a "plan" instance or "order" instance. Instead, a new instance 'basedOn' the prior instance should be created with the new 'intent' value. One exception to this is that the granularity of Request.intent is allowed to change. For example, a Request identified as an "order" might later be clarified to be a "filler-order". Or, in rarer cases (to meet recipient constraints), the reverse might also occur. When resources map to this element, they are free to define as many codes as necessary to cover their space and will map to "proposal, plan or order". Can have multiple codes that map to one of these. E.g. "original order", "encoded order", "reflex order" would all map to "order". Expectation is that the set of codes is mutually exclusive or a strict all-encompassing hierarchy.; ; Resource: ) - no reason provided intent does not contain the recommended logical text for requirements (Pattern: Proposals/recommendations, plans and orders all use the same structure and can exist in the same fulfillment chain.; ; Resource: ) - no reason provided

MedicationRequest

MedicationRequest.intent : code [1..1]

intent does not contain the recommended logical text for short (Pattern: proposal | plan | order (immutable); ; Resource: proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option) - no reason provided intent does not contain the recommended logical text for definition (Pattern: Indicates the level of authority/intentionality associated with the medication request and where the request fits into the workflow chain.; ; Resource: Whether the request is a proposal, plan, or an original order.) - no reason provided intent does not contain the recommended logical text for comments (Pattern: This element is expected to be immutable. E.g. A "proposal" instance should never change to be a "plan" instance or "order" instance. Instead, a new instance 'basedOn' the prior instance should be created with the new 'intent' value. One exception to this is that the granularity of Request.intent is allowed to change. For example, a Request identified as an "order" might later be clarified to be a "filler-order". Or, in rarer cases (to meet recipient constraints), the reverse might also occur. When resources map to this element, they are free to define as many codes as necessary to cover their space and will map to "proposal, plan or order". Can have multiple codes that map to one of these. E.g. "original order", "encoded order", "reflex order" would all map to "order". Expectation is that the set of codes is mutually exclusive or a strict all-encompassing hierarchy.; ; Resource: It is expected that the type of requester will be restricted for different stages of a MedicationRequest. For example, Proposals can be created by a patient, relatedPerson, Practitioner or Device. Plans can be created by Practitioners, Patients, RelatedPersons and Devices. Original orders can be created by a Practitioner only. An instance-order is an instantiation of a request or order and may be used to populate Medication Administration Record. This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.) - no reason provided intent does not contain the recommended logical text for requirements (Pattern: Proposals/recommendations, plans and orders all use the same structure and can exist in the same fulfillment chain.; ; Resource: ) - no reason provided

NutritionOrder

NutritionOrder.intent : code [1..1]

intent does not contain the recommended logical text for short (Pattern: proposal | plan | order (immutable); ; Resource: proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option) - no reason provided intent does not contain the recommended logical text for definition (Pattern: Indicates the level of authority/intentionality associated with the nutrition order and where the request fits into the workflow chain.; ; Resource: Indicates the level of authority/intentionality associated with the NutrionOrder and where the request fits into the workflow chain.) - no reason provided intent does not contain the recommended logical text for comments (Pattern: This element is expected to be immutable. E.g. A "proposal" instance should never change to be a "plan" instance or "order" instance. Instead, a new instance 'basedOn' the prior instance should be created with the new 'intent' value. One exception to this is that the granularity of Request.intent is allowed to change. For example, a Request identified as an "order" might later be clarified to be a "filler-order". Or, in rarer cases (to meet recipient constraints), the reverse might also occur. When resources map to this element, they are free to define as many codes as necessary to cover their space and will map to "proposal, plan or order". Can have multiple codes that map to one of these. E.g. "original order", "encoded order", "reflex order" would all map to "order". Expectation is that the set of codes is mutually exclusive or a strict all-encompassing hierarchy.; ; Resource: When resources map to this element, they are free to define as many codes as necessary to cover their space and will map to "proposal, plan or order". Can have multiple codes that map to one of these. E.g. "original order", "encoded order", "reflex order" would all map to "order". Expectation is that the set of codes is mutually exclusive or a strict all-encompassing hierarchy.) - no reason provided

~~RequestGroup~~ RequestOrchestration

~~RequestGroup.intent~~ RequestOrchestration.intent : code [1..1]

intent does not contain the recommended logical text for short (Pattern: proposal | plan | order (immutable); ; Resource: proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option) - no reason provided intent does not contain the recommended logical text for definition (Pattern: Indicates the level of authority/intentionality associated with the request orchestration and where the request fits into the workflow chain.; ; Resource: Indicates the level of authority/intentionality associated with the request and where the request fits into the workflow chain.) - no reason provided intent does not contain the recommended logical text for comments (Pattern: This element is expected to be immutable. E.g. A "proposal" instance should never change to be a "plan" instance or "order" instance. Instead, a new instance 'basedOn' the prior instance should be created with the new 'intent' value. One exception to this is that the granularity of Request.intent is allowed to change. For example, a Request identified as an "order" might later be clarified to be a "filler-order". Or, in rarer cases (to meet recipient constraints), the reverse might also occur. When resources map to this element, they are free to define as many codes as necessary to cover their space and will map to "proposal, plan or order". Can have multiple codes that map to one of these. E.g. "original order", "encoded order", "reflex order" would all map to "order". Expectation is that the set of codes is mutually exclusive or a strict all-encompassing hierarchy.; ; Resource: ) - no reason provided

ServiceRequest

ServiceRequest.intent : code [1..1]

intent does not contain the recommended logical text for short (Pattern: proposal | plan | order (immutable); ; Resource: proposal | plan | directive | order +) - no reason provided intent does not contain the recommended logical text for definition (Pattern: Indicates the level of authority/intentionality associated with the service request and where the request fits into the workflow chain.; ; Resource: Whether the request is a proposal, plan, an original order or a reflex order.) - no reason provided intent does not contain the recommended logical text for comments (Pattern: This element is expected to be immutable. E.g. A "proposal" instance should never change to be a "plan" instance or "order" instance. Instead, a new instance 'basedOn' the prior instance should be created with the new 'intent' value. One exception to this is that the granularity of Request.intent is allowed to change. For example, a Request identified as an "order" might later be clarified to be a "filler-order". Or, in rarer cases (to meet recipient constraints), the reverse might also occur. When resources map to this element, they are free to define as many codes as necessary to cover their space and will map to "proposal, plan or order". Can have multiple codes that map to one of these. E.g. "original order", "encoded order", "reflex order" would all map to "order". Expectation is that the set of codes is mutually exclusive or a strict all-encompassing hierarchy.; ; Resource: This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.) - no reason provided intent does not contain the recommended logical text for requirements (Pattern: Proposals/recommendations, plans and orders all use the same structure and can exist in the same fulfillment chain.; ; Resource: ) - no reason provided

Task

Task.intent : code [1..1]

IsModifier differs (Pattern: true; ; Resource: false) - no reason provided intent does not contain the recommended logical text for short (Pattern: proposal | plan | order (immutable); ; Resource: unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option) - no reason provided intent does not contain the recommended logical text for definition (Pattern: Indicates the level of authority/intentionality associated with the task and where the request fits into the workflow chain.; ; Resource: Indicates the "level" of actionability associated with the Task, i.e. i+R[9]Cs this a proposed task, a planned task, an actionable task, etc.) - no reason provided intent does not contain the recommended logical text for comments (Pattern: This element is expected to be immutable. E.g. A "proposal" instance should never change to be a "plan" instance or "order" instance. Instead, a new instance 'basedOn' the prior instance should be created with the new 'intent' value. One exception to this is that the granularity of Request.intent is allowed to change. For example, a Request identified as an "order" might later be clarified to be a "filler-order". Or, in rarer cases (to meet recipient constraints), the reverse might also occur. When resources map to this element, they are free to define as many codes as necessary to cover their space and will map to "proposal, plan or order". Can have multiple codes that map to one of these. E.g. "original order", "encoded order", "reflex order" would all map to "order". Expectation is that the set of codes is mutually exclusive or a strict all-encompassing hierarchy.; ; Resource: This element is immutable. Proposed tasks, planned tasks, etc. must be distinct instances. In most cases, Tasks will have an intent of "order".) - no reason provided intent does not contain the recommended logical text for requirements (Pattern: Proposals/recommendations, plans and orders all use the same structure and can exist in the same fulfillment chain.; ; Resource: ) - no reason provided

Transport

Transport.intent : code [1..1]

IsModifier differs (Pattern: true; ; Resource: false) - no reason provided intent does not contain the recommended logical text for short (Pattern: proposal | plan | order (immutable); ; Resource: unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option) - no reason provided intent does not contain the recommended logical text for definition (Pattern: Indicates the level of authority/intentionality associated with the transport and where the request fits into the workflow chain.; ; Resource: Indicates the "level" of actionability associated with the Transport, i.e. i+R[9]Cs this a proposed transport, a planned transport, an actionable transport, etc.) - no reason provided intent does not contain the recommended logical text for comments (Pattern: This element is expected to be immutable. E.g. A "proposal" instance should never change to be a "plan" instance or "order" instance. Instead, a new instance 'basedOn' the prior instance should be created with the new 'intent' value. One exception to this is that the granularity of Request.intent is allowed to change. For example, a Request identified as an "order" might later be clarified to be a "filler-order". Or, in rarer cases (to meet recipient constraints), the reverse might also occur. When resources map to this element, they are free to define as many codes as necessary to cover their space and will map to "proposal, plan or order". Can have multiple codes that map to one of these. E.g. "original order", "encoded order", "reflex order" would all map to "order". Expectation is that the set of codes is mutually exclusive or a strict all-encompassing hierarchy.; ; Resource: This element is immutable. Proposed transports, planned transports, etc. must be distinct instances. In most cases, Transports will have an intent of "order".) - no reason provided intent does not contain the recommended logical text for requirements (Pattern: Proposals/recommendations, plans and orders all use the same structure and can exist in the same fulfillment chain.; ; Resource: ) - no reason provided

Request.priority

Request.priority : code [0..1]

Resource

Matches

Issues

Tasks

Status

Notes

Appointment

Appointment.priority : ~~unsignedInt~~ CodeableConcept [0..1]

~~The type 'unsignedInt' is~~

Resource does

~~legal according to~~

support types that are part of

~~(unsignedInt vs~~

(Pattern:

- no reason provided Resource supports types that are not part of the pattern (; Resource: CodeableConcept) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided Binding strengths differ (Pattern: required; ; Resource: example) - no reason provided priority does not contain the recommended logical text for short (Pattern: routine | urgent | asap | stat; ; Resource: Used to make informed decisions if needing to re-prioritize) - no reason provided priority does not contain the recommended logical text for definition (Pattern: Indicates how quickly the appointment should be addressed with respect to other requests.; ; Resource: The priority of the appointment. Can be used to make informed decisions if needing to re-prioritize appointments. (The iCal Standard specifies 0 as undefined, 1 as highest, 9 as lowest priority).) - no reason provided

Type Mismatch.

GF#22101

investigations

waiting for committee discussion

Claim

Claim.priority : CodeableConcept ~~[1..1]~~ [0..1]

~~The type 'CodeableConcept' is~~

Resource does

~~legal according to~~

support types that are part of

~~(CodeableConcept vs~~

(Pattern:

- no reason provided Resource supports types that are not part of the pattern (; Resource: CodeableConcept) - no reason provided Binding strengths differ (Pattern: required; ; Resource: example) - no reason provided priority does not contain the recommended logical text for short (Pattern: routine | urgent | asap | stat; ; Resource: Desired processing urgency) - no reason provided priority does not contain the recommended logical text for definition (Pattern: Indicates how quickly the claim should be addressed with respect to other requests.; ; Resource: The provider-required urgency of processing the request. Typical values include: stat, normal, deferred.) - no reason provided

Type Mismatch.

CommunicationRequest

CommunicationRequest.priority : code [0..1]

priority does not contain the recommended logical text for definition (Pattern: Indicates how quickly the communication request should be addressed with respect to other requests.; ; Resource: Characterizes how quickly the proposed act must be initiated. Includes concepts such as stat, urgent, routine.) - no reason provided

CoverageEligibilityRequest

CoverageEligibilityRequest.priority : CodeableConcept [0..1]

~~The type 'CodeableConcept' is~~

Resource does

~~legal according to~~

support types that are part of

~~(CodeableConcept vs~~

(Pattern:

- no reason provided Resource supports types that are not part of the pattern (; Resource: CodeableConcept) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided Binding strengths differ (Pattern: required; ; Resource: example) - no reason provided priority does not contain the recommended logical text for short (Pattern: routine | urgent | asap | stat; ; Resource: Desired processing priority) - no reason provided priority does not contain the recommended logical text for definition (Pattern: Indicates how quickly the coverage eligibility request should be addressed with respect to other requests.; ; Resource: When the requestor expects the processor to complete processing.) - no reason provided

Type Mismatch.

DeviceRequest

DeviceRequest.priority : code [0..1]

priority does not contain the recommended logical text for definition (Pattern: Indicates how quickly the device request should be addressed with respect to other requests.; ; Resource: Indicates how quickly the request should be addressed with respect to other requests.) - no reason provided

MedicationRequest

MedicationRequest.priority : code [0..1]

priority does not contain the recommended logical text for definition (Pattern: Indicates how quickly the medication request should be addressed with respect to other requests.; ; Resource: Indicates how quickly the Medication Request should be addressed with respect to other requests.) - no reason provided

~~RequestGroup~~ NutritionOrder

~~RequestGroup.priority~~ NutritionOrder.priority : code [0..1]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided priority does not contain the recommended logical text for definition (Pattern: Indicates how quickly the nutrition order should be addressed with respect to other requests.; ; Resource: Indicates how quickly the Nutrition Order should be addressed with respect to other requests.) - no reason provided

RequestOrchestration

~~RequestGroup.action.priority~~ RequestOrchestration.priority : code [0..1]

priority does not contain the recommended logical text for definition (Pattern: Indicates how quickly the request orchestration should be addressed with respect to other requests.; ; Resource: Indicates how quickly the request should be addressed with respect to other requests.) - no reason provided

RequestOrchestration.action.priority : code [0..1]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided priority does not contain the recommended logical text for definition (Pattern: Indicates how quickly the request orchestration should be addressed with respect to other requests.; ; Resource: Indicates how quickly the action should be addressed with respect to other actions.) - no reason provided

ServiceRequest

ServiceRequest.priority : code [0..1]

priority does not contain the recommended logical text for definition (Pattern: Indicates how quickly the service request should be addressed with respect to other requests.; ; Resource: Indicates how quickly the ServiceRequest should be addressed with respect to other requests.) - no reason provided

SupplyRequest

SupplyRequest.priority : code [0..1]

priority does not contain the recommended logical text for definition (Pattern: Indicates how quickly the supply request should be addressed with respect to other requests.; ; Resource: Indicates how quickly this SupplyRequest should be addressed with respect to other requests.) - no reason provided

Task

Task.priority : code [0..1]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided priority does not contain the recommended logical text for definition (Pattern: Indicates how quickly the task should be addressed with respect to other requests.; ; Resource: Indicates how quickly the Task should be addressed with respect to other requests.) - no reason provided

~~Request.doNotPerform~~ Transport

~~Request.doNotPerform~~

Transport.priority : ~~boolean~~ code [0..1]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided priority does not contain the recommended logical text for definition (Pattern: Indicates how quickly the transport should be addressed with respect to other requests.; ; Resource: Indicates how quickly the Transport should be addressed with respect to other requests.) - no reason provided

~~Resource~~

~~Matches~~ ~~Issues~~

~~Tasks~~ ~~Status~~

~~Notes~~

~~CarePlan~~ Request.doNotPerform

Request.doNotPerform : boolean [0..1]

Resource

Matches

Issues

Tasks

Status

Notes

CommunicationRequest

CommunicationRequest.doNotPerform : boolean [0..1]

doNotPerform does not contain the recommended logical text for short (Pattern: true if request is prohibiting action; ; Resource: True if request is prohibiting action) - no reason provided doNotPerform does not contain the recommended logical text for definition (Pattern: If true indicates that the communication request is asking for the specified action to *not* occur.; ; Resource: If true indicates that the CommunicationRequest is asking for the specified action to *not* occur.) - no reason provided doNotPerform does not contain the recommended logical text for comments (Pattern: The attributes provided with the request qualify what is not to be done. For example, if an effectiveTime is provided, the "do not" request only applies within the specified time. If a performerType is specified then the "do not" request only applies to performers of that type. Qualifiers include: code, subject, occurrence, performerType and performer. In some cases, the Request.code may pre-coordinate prohibition into the requested action. E.g. "NPO" (nothing by mouth), "DNR" (do not recussitate). If this happens, doNotPerform SHALL NOT be set to true. I.e. The resource shall not have double negation. (E.g. "Do not DNR").; ; Resource: The attributes provided with the request qualify what is not to be done.) - no reason provided doNotPerform does not contain the recommended logical text for requirements (Pattern: Supports things like Do Not Recussitate, Nothing by mouth, etc.; ; Resource: ) - no reason provided

ServiceRequest

ServiceRequest.doNotPerform : boolean [0..1]

doNotPerform does not contain the recommended logical text for short (Pattern: true if request is prohibiting action; ; Resource: True if service/procedure should not be performed) - no reason provided doNotPerform does not contain the recommended logical text for definition (Pattern: If true indicates that the service request is asking for the specified action to *not* occur.; ; Resource: Set this to true if the record is saying that the service/procedure should NOT be performed.) - no reason provided doNotPerform does not contain the recommended logical text for comments (Pattern: The attributes provided with the request qualify what is not to be done. For example, if an effectiveTime is provided, the "do not" request only applies within the specified time. If a performerType is specified then the "do not" request only applies to performers of that type. Qualifiers include: code, subject, occurrence, performerType and performer. In some cases, the Request.code may pre-coordinate prohibition into the requested action. E.g. "NPO" (nothing by mouth), "DNR" (do not recussitate). If this happens, doNotPerform SHALL NOT be set to true. I.e. The resource shall not have double negation. (E.g. "Do not DNR").; ; Resource: In general, only the code and timeframe will be present, though occasional additional qualifiers such as body site or even performer could be included to narrow the scope of the prohibition. If the ServiceRequest.code and ServiceRequest.doNotPerform both contain negation, that will reinforce prohibition and should not have a double negative interpretation.) - no reason provided doNotPerform does not contain the recommended logical text for requirements (Pattern: Supports things like Do Not Recussitate, Nothing by mouth, etc.; ; Resource: Used for do not ambulate, do not elevate head of bed, do not flush NG tube, do not take blood pressure on a certain arm, etc.) - no reason provided

~~Request.code~~ Request.category

~~Request.code~~ Request.category : CodeableConcept ~~[0..1]~~ [0..*]

Resource

Matches

Issues

Tasks

Status

Notes

~~Appointment~~ Request.code

Request.code : CodeableConcept ~~[0..*] Maximum Cardinality Violation (pattern = 1, resource = *) Names are different. Cardinality Problem.~~ [0..1]

Resource

~~CarePlan~~ Matches

~~CarePlan.activity.detail.code : CodeableConcept [0..1]~~ Issues

Tasks

Status

Notes

~~Contract~~ Appointment

~~Contract.type : CodeableConcept [0..1] Contract.term.type~~ Appointment.serviceType : ~~CodeableConcept [0..1]~~ CodeableReference [0..*]

Names are different.
Type Mismatch.
Cardinality Problem.

DeviceRequest

~~DeviceRequest.code[x]~~ DeviceRequest.code : ~~Reference, CodeableConcept~~ CodeableReference [1..1]

~~The type 'Reference' is~~

Minimum Cardinality differs (Pattern: 0; ; Resource: 1) - no reason provided Resource does

~~legal according to~~

support types that are part of

~~(Reference, CodeableConcept vs~~

(Pattern:

- no reason provided Resource supports types that are not part of the pattern (; Resource: CodeableReference(Device,DeviceDefinition)) - no reason provided code does not contain the recommended logical text for short (Pattern: Service requested/ordered; ; Resource: Device requested) - no reason provided code does not contain the recommended logical text for definition (Pattern: A code that identifies the specific service or action being asked to be done (or not done).; ; Resource: The details of the device to be used.) - no reason provided

~~Names are different.~~ Type Mismatch.
Cardinality Problem.

ImmunizationRecommendation

ImmunizationRecommendation.recommendation.vaccineCode : CodeableConcept [0..*]

~~Violation (pattern = 1, resource =~~

differs (Pattern: 1; ; Resource:

- no reason provided code does not contain the recommended logical text for short (Pattern: Service requested/ordered; ; Resource: Vaccine or vaccine group recommendation applies to) - no reason provided code does not contain the recommended logical text for definition (Pattern: A code that identifies the specific service or action being asked to be done (or not done).; ; Resource: Vaccine(s) or vaccine group that pertain to the recommendation.) - no reason provided

Names are different.
Cardinality Problem.

MedicationRequest

~~MedicationRequest.medication[x]~~ MedicationRequest.medication : ~~CodeableConcept, Reference~~ CodeableReference [1..1]

~~The type 'Reference' is~~

Minimum Cardinality differs (Pattern: 0; ; Resource: 1) - no reason provided Resource does

~~legal according to~~

support types that are part of

~~(CodeableConcept, Reference vs~~

(Pattern:

- no reason provided Resource supports types that are not part of the pattern (; Resource: CodeableReference(Medication)) - no reason provided code does not contain the recommended logical text for short (Pattern: Service requested/ordered; ; Resource: Medication to be taken) - no reason provided code does not contain the recommended logical text for definition (Pattern: A code that identifies the specific service or action being asked to be done (or not done).; ; Resource: Identifies the medication being requested. This is a link to a resource that represents the medication which may be the details of the medication or simply an attribute carrying a code that identifies the medication from a known list of medications.) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

NutritionOrder

NutritionOrder.oralDiet.type : CodeableConcept [0..*]

~~Violation (pattern = 1, resource =~~

differs (Pattern: 1; ; Resource:

- no reason provided code does not contain the recommended logical text for short (Pattern: Service requested/ordered; ; Resource: Type of oral diet or diet restrictions that describe what can be consumed orally) - no reason provided code does not contain the recommended logical text for definition (Pattern: A code that identifies the specific service or action being asked to be done (or not done).; ; Resource: The kind of diet or dietary restriction such as fiber restricted diet or diabetic diet.) - no reason provided

NutritionOrder.oralDiet.nutrient.modifier : CodeableConcept [0..1]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided code does not contain the recommended logical text for short (Pattern: Service requested/ordered; ; Resource: Type of nutrient that is being modified) - no reason provided code does not contain the recommended logical text for definition (Pattern: A code that identifies the specific service or action being asked to be done (or not done).; ; Resource: The nutrient that is being modified such as carbohydrate or sodium.) - no reason provided

NutritionOrder.oralDiet.texture.modifier : CodeableConcept [0..1]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided code does not contain the recommended logical text for short (Pattern: Service requested/ordered; ; Resource: Code to indicate how to alter the texture of the foods, e.g. pureed) - no reason provided code does not contain the recommended logical text for definition (Pattern: A code that identifies the specific service or action being asked to be done (or not done).; ; Resource: Any texture modifications (for solid foods) that should be made, e.g. easy to chew, chopped, ground, and pureed.) - no reason provided

NutritionOrder.oralDiet.texture.foodType : CodeableConcept [0..1]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided code does not contain the recommended logical text for short (Pattern: Service requested/ordered; ; Resource: Concepts that are used to identify an entity that is ingested for nutritional purposes) - no reason provided code does not contain the recommended logical text for definition (Pattern: A code that identifies the specific service or action being asked to be done (or not done).; ; Resource: The food type(s) (e.g. meats, all foods) that the texture modification applies to. This could be all foods types.) - no reason provided

NutritionOrder.oralDiet.fluidConsistencyType : CodeableConcept [0..*]

~~Violation (pattern = 1, resource =~~

differs (Pattern: 1; ; Resource:

- no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided code does not contain the recommended logical text for short (Pattern: Service requested/ordered; ; Resource: The required consistency of fluids and liquids provided to the patient) - no reason provided code does not contain the recommended logical text for definition (Pattern: A code that identifies the specific service or action being asked to be done (or not done).; ; Resource: The required consistency (e.g. honey-thick, nectar-thick, thin, thickened.) of liquids or fluids served to the patient.) - no reason provided

NutritionOrder.supplement.type : ~~CodeableConcept~~ CodeableReference [0..1]

Resource does not support types that are part of the pattern (Pattern: CodeableConcept) - no reason provided Resource supports types that are not part of the pattern (; Resource: CodeableReference(NutritionProduct)) - no reason provided code does not contain the recommended logical text for short (Pattern: Service requested/ordered; ; Resource: Type of supplement product requested) - no reason provided code does not contain the recommended logical text for definition (Pattern: A code that identifies the specific service or action being asked to be done (or not done).; ; Resource: The kind of nutritional supplement product required such as a high protein or pediatric clear liquid supplement.) - no reason provided

NutritionOrder.enteralFormula.baseFormulaType : ~~CodeableConcept~~ CodeableReference [0..1]

Resource does not support types that are part of the pattern (Pattern: CodeableConcept) - no reason provided Resource supports types that are not part of the pattern (; Resource: CodeableReference(NutritionProduct)) - no reason provided code does not contain the recommended logical text for short (Pattern: Service requested/ordered; ; Resource: Type of enteral or infant formula) - no reason provided code does not contain the recommended logical text for definition (Pattern: A code that identifies the specific service or action being asked to be done (or not done).; ; Resource: The type of enteral or infant formula such as an adult standard formula with fiber or a soy-based infant formula.) - no reason provided

~~NutritionOrder.enteralFormula.additiveType~~ NutritionOrder.enteralFormula.additive.type : ~~CodeableConcept~~ CodeableReference [0..1]

Resource does not support types that are part of the pattern (Pattern: CodeableConcept) - no reason provided Resource supports types that are not part of the pattern (; Resource: CodeableReference(NutritionProduct)) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided code does not contain the recommended logical text for short (Pattern: Service requested/ordered; ; Resource: Type of modular component to add to the feeding) - no reason provided code does not contain the recommended logical text for definition (Pattern: A code that identifies the specific service or action being asked to be done (or not done).; ; Resource: Indicates the type of modular component such as protein, carbohydrate, fat or fiber to be provided in addition to or mixed with the base formula.) - no reason provided

Names are different.
~~Cardinality Problem.~~ Type Mismatch.

~~RequestGroup~~ RequestOrchestration

~~RequestGroup.code~~ RequestOrchestration.code : CodeableConcept [0..1]

code does not contain the recommended logical text for short (Pattern: Service requested/ordered; ; Resource: What's being requested/ordered) - no reason provided code does not contain the recommended logical text for definition (Pattern: A code that identifies the specific service or action being asked to be done (or not done).; ; Resource: A code that identifies what the overall request orchestration is.) - no reason provided

~~RequestGroup.action.code~~ RequestOrchestration.action.code : CodeableConcept [0..*]

~~Violation (pattern = 1, resource =~~

differs (Pattern: 1; ; Resource:

- no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided code does not contain the recommended logical text for short (Pattern: Service requested/ordered; ; Resource: Code representing the meaning of the action or sub-actions) - no reason provided code does not contain the recommended logical text for definition (Pattern: A code that identifies the specific service or action being asked to be done (or not done).; ; Resource: A code that provides meaning for the action or action group. For example, a section may have a LOINC code for a section of a documentation template.) - no reason provided

Cardinality Problem.

ServiceRequest

ServiceRequest.code : ~~CodeableConcept~~ CodeableReference [0..1]

Resource does not support types that are part of the pattern (Pattern: CodeableConcept) - no reason provided Resource supports types that are not part of the pattern (; Resource: CodeableReference(ActivityDefinition,PlanDefinition)) - no reason provided code does not contain the recommended logical text for short (Pattern: Service requested/ordered; ; Resource: What is being requested/ordered) - no reason provided code does not contain the recommended logical text for definition (Pattern: A code that identifies the specific service or action being asked to be done (or not done).; ; Resource: A code or reference that identifies a particular service (i.e., procedure, diagnostic investigation, or panel of investigations) that have been requested.) - no reason provided

Type Mismatch.

SupplyRequest

~~SupplyRequest.item[x]~~ SupplyRequest.item : ~~CodeableConcept, Reference~~ CodeableReference [1..1]

~~The type 'Reference' is~~

Minimum Cardinality differs (Pattern: 0; ; Resource: 1) - no reason provided Resource does

~~legal according to~~

support types that are part of

~~(CodeableConcept, Reference vs~~

(Pattern:

- no reason provided Resource supports types that are not part of the pattern (; Resource: CodeableReference(Medication,Substance,Device,DeviceDefinition,BiologicallyDerivedProduct,NutritionProduct,InventoryItem)) - no reason provided code does not contain the recommended logical text for short (Pattern: Service requested/ordered; ; Resource: Medication, Substance, or Device requested to be supplied) - no reason provided code does not contain the recommended logical text for definition (Pattern: A code that identifies the specific service or action being asked to be done (or not done).; ; Resource: The item that is requested to be supplied. This is either a link to a resource representing the details of the item or a code that identifies the item from a known list.) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

Task

Task.doNotPerform : boolean [0..1]

Resource does not support types that are part of the pattern (Pattern: CodeableConcept) - no reason provided Resource supports types that are not part of the pattern (; Resource: boolean) - no reason provided IsModifier differs (Pattern: false; ; Resource: true) - no reason provided Only one element has bindings (Pattern: true; ; Resource: false) - no reason provided code does not contain the recommended logical text for short (Pattern: Service requested/ordered; ; Resource: True if Task is prohibiting action) - no reason provided code does not contain the recommended logical text for definition (Pattern: A code that identifies the specific service or action being asked to be done (or not done).; ; Resource: If true indicates that the Task is asking for the specified action to *not* occur.) - no reason provided

Task.code : CodeableConcept [0..1]

code does not contain the recommended logical text for short (Pattern: Service requested/ordered; ; Resource: Task Type) - no reason provided code does not contain the recommended logical text for definition (Pattern: A code that identifies the specific service or action being asked to be done (or not done).; ; Resource: A name or code (or both) briefly describing what the task involves.) - no reason provided

Names are different.
Type Mismatch.

Transport

Transport.code : CodeableConcept [0..1]

code does not contain the recommended logical text for short (Pattern: Service requested/ordered; ; Resource: Transport Type) - no reason provided code does not contain the recommended logical text for definition (Pattern: A code that identifies the specific service or action being asked to be done (or not done).; ; Resource: A name or code (or both) briefly describing what the transport involves.) - no reason provided

Request.product

Resource

Matches

Issues

Tasks

Status

Notes

Request.subject

Request.subject : Reference(Patient|Group) [1..1]

Resource

Matches

Issues

Tasks

Status

Notes

~~CarePlan~~ Appointment

~~CarePlan.subject~~ Appointment.participant : ~~Reference [1..1]~~ BackboneElement [1..*]

Maximum Cardinality differs (Pattern: 1; ; Resource: *) - no reason provided Resource does not support types that are part of the pattern (Pattern: Reference(Patient,Group)) - no reason provided Resource supports types that are not part of the pattern (; Resource: BackboneElement) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided subject does not contain the recommended logical text for short (Pattern: Individual the service is ordered/prohibited for; ; Resource: Participants involved in appointment) - no reason provided subject does not contain the recommended logical text for definition (Pattern: The individual or set of individuals the action is to be performed/not performed on or for.; ; Resource: List of participants involved in the appointment.) - no reason provided subject does not contain the recommended logical text for requirements (Pattern: Links the request to the Patient context.; ; Resource: ) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

~~Claim~~ CarePlan

~~Claim.patient~~ CarePlan.subject : Reference [1..1]

subject does not contain the recommended logical text for short (Pattern: Individual the service is ordered/prohibited for; ; Resource: Who the care plan is for) - no reason provided subject does not contain the recommended logical text for definition (Pattern: The individual or set of individuals the action is to be performed/not performed on or for.; ; Resource: Identifies the patient or group whose intended care is described by the plan.) - no reason provided subject does not contain the recommended logical text for requirements (Pattern: Links the request to the Patient context.; ; Resource: ) - no reason provided

~~Names are different.~~

~~CommunicationRequest~~ Claim

~~CommunicationRequest.subject~~ Claim.patient : Reference ~~[0..1]~~ [1..1]

~~Minimum Cardinality Violation (pattern = 1, resource = 0)~~

Resource does not support types that are part of the pattern (Pattern: Reference(Group)) - no reason provided subject does not contain the recommended logical text for short (Pattern: Individual the service is ordered/prohibited for; ; Resource: The recipient of the products and services) - no reason provided subject does not contain the recommended logical text for definition (Pattern: The individual or set of individuals the action is to be performed/not performed on or for.; ; Resource: The party to whom the professional services and/or products have been supplied or are being considered and for whom actual or forecast reimbursement is sought.) - no reason provided subject does not contain the recommended logical text for requirements (Pattern: Links the request to the Patient context.; ; Resource: The patient must be supplied to the insurer so that confirmation of coverage and service history may be considered as part of the authorization and/or adjudiction.) - no reason provided

~~Cardinality Problem.~~ Names are different.
Type Mismatch.

~~Contract~~ CommunicationRequest

~~Contract.subject~~ CommunicationRequest.subject : Reference ~~[0..*]~~ [0..1]

~~Violation (pattern = 1, resource = 0), Maximum Cardinality Violation (pattern = 1, resource = *)~~

differs (Pattern: 1; ; Resource: 0) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided subject does not contain the recommended logical text for short (Pattern: Individual the service is ordered/prohibited for; ; Resource: Focus of message) - no reason provided subject does not contain the recommended logical text for definition (Pattern: The individual or set of individuals the action is to be performed/not performed on or for.; ; Resource: The patient or group that is the focus of this communication request.) - no reason provided subject does not contain the recommended logical text for requirements (Pattern: Links the request to the Patient context.; ; Resource: ) - no reason provided

Cardinality Problem.

CoverageEligibilityRequest

CoverageEligibilityRequest.patient : Reference [1..1]

Resource does not support types that are part of the pattern (Pattern: Reference(Group)) - no reason provided subject does not contain the recommended logical text for short (Pattern: Individual the service is ordered/prohibited for; ; Resource: Intended recipient of products and services) - no reason provided subject does not contain the recommended logical text for definition (Pattern: The individual or set of individuals the action is to be performed/not performed on or for.; ; Resource: The party who is the beneficiary of the supplied coverage and for whom eligibility is sought.) - no reason provided subject does not contain the recommended logical text for requirements (Pattern: Links the request to the Patient context.; ; Resource: Required to provide context and coverage validation.) - no reason provided

Names are different.
Type Mismatch.

DeviceRequest

DeviceRequest.subject : Reference [1..1]

Resource supports types that are not part of the pattern (; Resource: Reference(Location,Device)) - no reason provided subject does not contain the recommended logical text for short (Pattern: Individual the service is ordered/prohibited for; ; Resource: Focus of request) - no reason provided subject does not contain the recommended logical text for definition (Pattern: The individual or set of individuals the action is to be performed/not performed on or for.; ; Resource: The patient who will use the device.) - no reason provided subject does not contain the recommended logical text for requirements (Pattern: Links the request to the Patient context.; ; Resource: ) - no reason provided

Type Mismatch.

EnrollmentRequest

EnrollmentRequest.candidate : Reference [0..1]

~~Violation (pattern = 1, resource =~~

differs (Pattern: 1; ; Resource:

- no reason provided Resource does not support types that are part of the pattern (Pattern: Reference(Group)) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided subject does not contain the recommended logical text for short (Pattern: Individual the service is ordered/prohibited for; ; Resource: The subject to be enrolled) - no reason provided subject does not contain the recommended logical text for definition (Pattern: The individual or set of individuals the action is to be performed/not performed on or for.; ; Resource: Patient Resource.) - no reason provided subject does not contain the recommended logical text for requirements (Pattern: Links the request to the Patient context.; ; Resource: ) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

ImmunizationRecommendation

ImmunizationRecommendation.patient : Reference [1..1]

Resource does not support types that are part of the pattern (Pattern: Reference(Group)) - no reason provided subject does not contain the recommended logical text for short (Pattern: Individual the service is ordered/prohibited for; ; Resource: Who this profile is for) - no reason provided subject does not contain the recommended logical text for definition (Pattern: The individual or set of individuals the action is to be performed/not performed on or for.; ; Resource: The patient the recommendation(s) are for.) - no reason provided subject does not contain the recommended logical text for requirements (Pattern: Links the request to the Patient context.; ; Resource: ) - no reason provided

Names are different.
Type Mismatch.

MedicationRequest

MedicationRequest.subject : Reference [1..1]

subject does not contain the recommended logical text for short (Pattern: Individual the service is ordered/prohibited for; ; Resource: Individual or group for whom the medication has been requested) - no reason provided subject does not contain the recommended logical text for definition (Pattern: The individual or set of individuals the action is to be performed/not performed on or for.; ; Resource: The individual or group for whom the medication has been requested.) - no reason provided subject does not contain the recommended logical text for requirements (Pattern: Links the request to the Patient context.; ; Resource: ) - no reason provided

NutritionOrder

~~NutritionOrder.patient~~ NutritionOrder.subject : Reference [1..1]

subject does not contain the recommended logical text for short (Pattern: Individual the service is ordered/prohibited for; ; Resource: Who requires the diet, formula or nutritional supplement) - no reason provided subject does not contain the recommended logical text for definition (Pattern: The individual or set of individuals the action is to be performed/not performed on or for.; ; Resource: The person or set of individuals who needs the nutrition order for an oral diet, nutritional supplement and/or enteral or formula feeding.) - no reason provided subject does not contain the recommended logical text for requirements (Pattern: Links the request to the Patient context.; ; Resource: ) - no reason provided

~~Names are different.~~

~~RequestGroup~~ RequestOrchestration

~~RequestGroup.subject~~ RequestOrchestration.subject : Reference [0..1]

~~Violation (pattern = 1, resource =~~

differs (Pattern: 1; ; Resource:

- no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(CareTeam,Device,HealthcareService,Location,Organization,Practitioner,PractitionerRole,RelatedPerson)) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided subject does not contain the recommended logical text for short (Pattern: Individual the service is ordered/prohibited for; ; Resource: Who the request orchestration is about) - no reason provided subject does not contain the recommended logical text for definition (Pattern: The individual or set of individuals the action is to be performed/not performed on or for.; ; Resource: The subject for which the request orchestration was created.) - no reason provided subject does not contain the recommended logical text for requirements (Pattern: Links the request to the Patient context.; ; Resource: ) - no reason provided

Type Mismatch.
Cardinality Problem.

ServiceRequest

ServiceRequest.subject : Reference [1..1]

Resource supports types that are not part of the pattern (; Resource: Reference(Location,Device)) - no reason provided subject does not contain the recommended logical text for short (Pattern: Individual the service is ordered/prohibited for; ; Resource: Individual or Entity the service is ordered for) - no reason provided subject does not contain the recommended logical text for definition (Pattern: The individual or set of individuals the action is to be performed/not performed on or for.; ; Resource: 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).) - no reason provided subject does not contain the recommended logical text for requirements (Pattern: Links the request to the Patient context.; ; Resource: ) - no reason provided

Type Mismatch.

Task

Task.for : Reference [0..1]

~~Violation (pattern = 1, resource =~~

differs (Pattern: 1; ; Resource:

- no reason provided Resource does not support types that are part of the pattern (Pattern: Reference(Patient,Group)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(Resource)) - no reason provided subject does not contain the recommended logical text for short (Pattern: Individual the service is ordered/prohibited for; ; Resource: Beneficiary of the Task) - no reason provided subject does not contain the recommended logical text for definition (Pattern: The individual or set of individuals the action is to be performed/not performed on or for.; ; Resource: The entity who benefits from the performance of the service specified in the task (e.g., the patient).) - no reason provided subject does not contain the recommended logical text for requirements (Pattern: Links the request to the Patient context.; ; Resource: Used to track tasks outstanding for a beneficiary. Do not use to track the task owner or creator (see owner and creator respectively). This can also affect access control.) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

Transport

Transport.for : Reference [0..1]

Minimum Cardinality differs (Pattern: 1; ; Resource: 0) - no reason provided Resource does not support types that are part of the pattern (Pattern: Reference(Patient,Group)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(Resource)) - no reason provided subject does not contain the recommended logical text for short (Pattern: Individual the service is ordered/prohibited for; ; Resource: Beneficiary of the Transport) - no reason provided subject does not contain the recommended logical text for definition (Pattern: The individual or set of individuals the action is to be performed/not performed on or for.; ; Resource: The entity who benefits from the performance of the service specified in the transport (e.g., the patient).) - no reason provided subject does not contain the recommended logical text for requirements (Pattern: Links the request to the Patient context.; ; Resource: Used to track transports outstanding for a beneficiary. Do not use to track the transport owner or creator (see owner and creator respectively). This can also affect access control.) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

VisionPrescription

VisionPrescription.patient : Reference [1..1]

Resource does not support types that are part of the pattern (Pattern: Reference(Group)) - no reason provided subject does not contain the recommended logical text for short (Pattern: Individual the service is ordered/prohibited for; ; Resource: Who prescription is for) - no reason provided subject does not contain the recommended logical text for definition (Pattern: The individual or set of individuals the action is to be performed/not performed on or for.; ; Resource: A resource reference to the person to whom the vision prescription applies.) - no reason provided subject does not contain the recommended logical text for requirements (Pattern: Links the request to the Patient context.; ; Resource: Needed to identify the patient for whom the vision prescription has been issued.) - no reason provided

Names are different.
Type Mismatch.

Request.encounter

Request.encounter : Reference(Encounter) [0..1]

Resource

Matches

Issues

Tasks

Status

Notes

CarePlan

CarePlan.encounter : Reference [0..1]

encounter does not contain the recommended logical text for short (Pattern: Encounter the care plan is tied to; ; Resource: The Encounter during which this CarePlan was created) - no reason provided encounter does not contain the recommended logical text for definition (Pattern: The Encounter during which this care plan was created or to which the creation of this record is tightly associated.; ; Resource: The Encounter during which this CarePlan was created or to which the creation of this record is tightly associated.) - no reason provided encounter does not contain the recommended logical text for comments (Pattern: This will typically be the encounter during which the care plan was created. However, some {{title}s may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission activities).; ; Resource: This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. CarePlan activities conducted as a result of the care plan may well occur as part of other encounters.) - no reason provided encounter does not contain the recommended logical text for requirements (Pattern: Links the care plan to the Encounter context.; ; Resource: ) - no reason provided

CommunicationRequest

CommunicationRequest.encounter : Reference [0..1]

encounter does not contain the recommended logical text for short (Pattern: Encounter the communication request is tied to; ; Resource: The Encounter during which this CommunicationRequest was created) - no reason provided encounter does not contain the recommended logical text for definition (Pattern: The Encounter during which this communication request was created or to which the creation of this record is tightly associated.; ; Resource: The Encounter during which this CommunicationRequest was created or to which the creation of this record is tightly associated.) - no reason provided encounter does not contain the recommended logical text for comments (Pattern: This will typically be the encounter during which the communication request was created. However, some {{title}s may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission activities).; ; Resource: This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter.) - no reason provided encounter does not contain the recommended logical text for requirements (Pattern: Links the communication request to the Encounter context.; ; Resource: ) - no reason provided

DeviceRequest

DeviceRequest.encounter : Reference [0..1]

encounter does not contain the recommended logical text for short (Pattern: Encounter the device request is tied to; ; Resource: Encounter motivating request) - no reason provided encounter does not contain the recommended logical text for definition (Pattern: The Encounter during which this device request was created or to which the creation of this record is tightly associated.; ; Resource: An encounter that provides additional context in which this request is made.) - no reason provided encounter does not contain the recommended logical text for comments (Pattern: This will typically be the encounter during which the device request was created. However, some {{title}s may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission activities).; ; Resource: ) - no reason provided encounter does not contain the recommended logical text for requirements (Pattern: Links the device request to the Encounter context.; ; Resource: ) - no reason provided

MedicationRequest

MedicationRequest.encounter : Reference [0..1]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided encounter does not contain the recommended logical text for short (Pattern: Encounter the medication request is tied to; ; Resource: Encounter created as part of encounter/admission/stay) - no reason provided encounter does not contain the recommended logical text for definition (Pattern: The Encounter during which this medication request was created or to which the creation of this record is tightly associated.; ; Resource: The Encounter during which this [x] was created or to which the creation of this record is tightly associated.) - no reason provided encounter does not contain the recommended logical text for comments (Pattern: This will typically be the encounter during which the medication request was created. However, some {{title}s may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission activities).; ; Resource: This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter." If there is a need to link to episodes of care they will be handled with an extension.) - no reason provided encounter does not contain the recommended logical text for requirements (Pattern: Links the medication request to the Encounter context.; ; Resource: ) - no reason provided

NutritionOrder

NutritionOrder.encounter : Reference [0..1]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided encounter does not contain the recommended logical text for short (Pattern: Encounter the nutrition order is tied to; ; Resource: The encounter associated with this nutrition order) - no reason provided encounter does not contain the recommended logical text for definition (Pattern: The Encounter during which this nutrition order was created or to which the creation of this record is tightly associated.; ; Resource: An encounter that provides additional information about the healthcare context in which this request is made.) - no reason provided encounter does not contain the recommended logical text for comments (Pattern: This will typically be the encounter during which the nutrition order was created. However, some {{title}s may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission activities).; ; Resource: ) - no reason provided encounter does not contain the recommended logical text for requirements (Pattern: Links the nutrition order to the Encounter context.; ; Resource: ) - no reason provided

~~RequestGroup~~ RequestOrchestration

~~RequestGroup.encounter~~ RequestOrchestration.encounter : Reference [0..1]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided encounter does not contain the recommended logical text for short (Pattern: Encounter the request orchestration is tied to; ; Resource: Created as part of) - no reason provided encounter does not contain the recommended logical text for definition (Pattern: The Encounter during which this request orchestration was created or to which the creation of this record is tightly associated.; ; Resource: Describes the context of the request orchestration, if any.) - no reason provided encounter does not contain the recommended logical text for comments (Pattern: This will typically be the encounter during which the request orchestration was created. However, some {{title}s may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission activities).; ; Resource: ) - no reason provided encounter does not contain the recommended logical text for requirements (Pattern: Links the request orchestration to the Encounter context.; ; Resource: ) - no reason provided

ServiceRequest

ServiceRequest.encounter : Reference [0..1]

encounter does not contain the recommended logical text for short (Pattern: Encounter the service request is tied to; ; Resource: Encounter in which the request was created) - no reason provided encounter does not contain the recommended logical text for definition (Pattern: The Encounter during which this service request was created or to which the creation of this record is tightly associated.; ; Resource: An encounter that provides additional information about the healthcare context in which this request is made.) - no reason provided encounter does not contain the recommended logical text for comments (Pattern: This will typically be the encounter during which the service request was created. However, some {{title}s may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission activities).; ; Resource: ) - no reason provided encounter does not contain the recommended logical text for requirements (Pattern: Links the service request to the Encounter context.; ; Resource: ) - no reason provided

Task

Task.encounter : Reference [0..1]

encounter does not contain the recommended logical text for short (Pattern: Encounter the task is tied to; ; Resource: Healthcare event during which this task originated) - no reason provided encounter does not contain the recommended logical text for definition (Pattern: The Encounter during which this task was created or to which the creation of this record is tightly associated.; ; Resource: The healthcare event (e.g. a patient and healthcare provider interaction) during which this task was created.) - no reason provided encounter does not contain the recommended logical text for comments (Pattern: This will typically be the encounter during which the task was created. However, some {{title}s may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission activities).; ; Resource: ) - no reason provided encounter does not contain the recommended logical text for requirements (Pattern: Links the task to the Encounter context.; ; Resource: For some tasks it may be important to know the link between the encounter the task originated within.) - no reason provided

Transport

Transport.encounter : Reference [0..1]

encounter does not contain the recommended logical text for short (Pattern: Encounter the transport is tied to; ; Resource: Healthcare event during which this transport originated) - no reason provided encounter does not contain the recommended logical text for definition (Pattern: The Encounter during which this transport was created or to which the creation of this record is tightly associated.; ; Resource: The healthcare event (e.g. a patient and healthcare provider interaction) during which this transport was created.) - no reason provided encounter does not contain the recommended logical text for comments (Pattern: This will typically be the encounter during which the transport was created. However, some {{title}s may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission activities).; ; Resource: ) - no reason provided encounter does not contain the recommended logical text for requirements (Pattern: Links the transport to the Encounter context.; ; Resource: For some transports it may be important to know the link between the encounter the transport originated within.) - no reason provided

VisionPrescription

VisionPrescription.encounter : Reference [0..1]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided encounter does not contain the recommended logical text for short (Pattern: Encounter the vision prescription is tied to; ; Resource: Created during encounter / admission / stay) - no reason provided encounter does not contain the recommended logical text for definition (Pattern: The Encounter during which this vision prescription was created or to which the creation of this record is tightly associated.; ; Resource: A reference to a resource that identifies the particular occurrence of contact between patient and health care provider during which the prescription was issued.) - no reason provided encounter does not contain the recommended logical text for comments (Pattern: This will typically be the encounter during which the vision prescription was created. However, some {{title}s may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission activities).; ; Resource: ) - no reason provided encounter does not contain the recommended logical text for requirements (Pattern: Links the vision prescription to the Encounter context.; ; Resource: Used in some jurisdictions to link clinical events to claim items.) - no reason provided

Request.occurrence[x]

Request.occurrence[x] : dateTime|Period|Timing [0..1]

Resource

Matches

Issues

Tasks

Status

Notes

Appointment

Appointment.start : instant [0..1]

~~The type 'instant'~~

Resource does not support types that are part of the pattern (Pattern: dateTime, Period, Timing) - no reason provided Resource supports types that are not part of the pattern (; Resource: instant) - no reason provided occurrence[x] does not contain the recommended logical text for short (Pattern: When service should (not) occur; ; Resource: When appointment

to take place) - no reason provided occurrence[x] does

~~legal according~~

contain the recommended logical text for definition (Pattern: The date or time(s) at which the activity or service is desired

occur or not occur.; ; Resource: Date/Time that

~~pattern (instant vs dateTime|Period|Timing)~~

appointment is to take place.) - no reason provided

Appointment.end : instant [0..1]

~~The type 'instant'~~

Resource does not support types that are part of the pattern (Pattern: dateTime, Period, Timing) - no reason provided Resource supports types that are not part of the pattern (; Resource: instant) - no reason provided occurrence[x] does not contain the recommended logical text for short (Pattern: When service should (not) occur; ; Resource: When appointment

to conclude) - no reason provided occurrence[x] does

~~legal according~~

contain the recommended logical text for definition (Pattern: The date or time(s) at which the activity or service is desired

occur or not occur.; ; Resource: Date/Time that

~~pattern (instant vs dateTime|Period|Timing)~~

appointment is to conclude.) - no reason provided

Appointment.minutesDuration : positiveInt [0..1]

Resource does not support types that are part of the pattern (Pattern: dateTime, Period, Timing) - no reason provided Resource supports types that are not part of the pattern (; Resource: positiveInt) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided occurrence[x] does not contain the recommended logical text for short (Pattern: When service should (not) occur; ; Resource: Can be less than start/end (e.g. estimate)) - no reason provided occurrence[x] does not contain the recommended logical text for definition (Pattern:

~~type 'positiveInt'~~

date or time(s) at which the activity or service

desired to occur or

~~legal according~~

occur.; ; Resource: Number of minutes that the appointment is

take. This can be less than

~~pattern (positiveInt vs dateTime|Period|Timing)~~

duration between the start and end times. For example, where the actual time of appointment is only an estimate or if a 30 minute appointment is being requested, but any time would work. Also, if there is, for example, a planned 15 minute break in the middle of a long appointment, the duration may be 15 minutes less than the difference between the start and end.) - no reason provided

Appointment.requestedPeriod : Period [0..*]

~~Violation (pattern = 1, resource =~~

differs (Pattern: 1; ; Resource:

- no reason provided Resource does not support types that are part of the pattern (Pattern: dateTime, Timing) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided occurrence[x] does not contain the recommended logical text for short (Pattern: When service should (not) occur; ; Resource: Potential date/time interval(s) requested to allocate the appointment within) - no reason provided occurrence[x] does not contain the recommended logical text for definition (Pattern: The date or time(s) at which the activity or service is desired to occur or not occur.; ; Resource: A set of date ranges (potentially including times) that the appointment is preferred to be scheduled within. The duration (usually in minutes) could also be provided to indicate the length of the appointment to fill and populate the start/end times for the actual allocated time. However, in other situations the duration may be calculated by the scheduling system.) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

AppointmentResponse

AppointmentResponse.start : instant [0..1]

Resource does not support types that are part of the pattern (Pattern: dateTime, Period, Timing) - no reason provided Resource supports types that are not part of the pattern (; Resource: instant) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided occurrence[x] does not contain the recommended logical text for short (Pattern: When service should (not) occur; ; Resource: Time from appointment, or requested new start time) - no reason provided occurrence[x] does not contain the recommended logical text for definition (Pattern:

~~type 'instant'~~

date or time(s) at which the activity or service

~~not legal according~~

desired

occur or not occur.; ; Resource: Date/Time that

~~pattern (instant vs dateTime|Period|Timing)~~

appointment is to take place, or requested new start time.) - no reason provided

AppointmentResponse.end : instant [0..1]

Resource does not support types that are part of the pattern (Pattern: dateTime, Period, Timing) - no reason provided Resource supports types that are not part of the pattern (; Resource: instant) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided occurrence[x] does not contain the recommended logical text for short (Pattern: When service should (not) occur; ; Resource: Time from appointment, or requested new end time) - no reason provided occurrence[x] does not contain the recommended logical text for definition (Pattern:

~~type 'instant'~~

date or time(s) at which the activity or service

desired to occur or

~~legal according~~

occur.; ; Resource: This may be either the same as the appointment request

confirm

~~pattern (instant vs dateTime|Period|Timing)~~

details of the appointment, or alternately a new time to request a re-negotiation of the end time.) - no reason provided

Names are different.
Type Mismatch.

CarePlan

CarePlan.period : Period [0..1]

~~CarePlan.activity.detail.scheduled[x] : Timing, Period, string [0..1]~~

~~type 'string'~~

date or time(s) at which the activity or service

~~not legal according~~

desired

occur or not occur.; ; Resource: Indicates when

~~pattern (Timing, Period, string vs dateTime|Period|Timing)~~

plan did (or is intended to) come into effect and end.) - no reason provided

Names are different.
Type Mismatch.

CommunicationRequest

CommunicationRequest.occurrence[x] : dateTime, Period [0..1]

~~Contract Contract.applies : Period [0..1] Contract.term.applies : Period [0..1]~~

Resource does not support types that are part of the pattern (Pattern: Timing) - no reason provided occurrence[x] does not contain the recommended logical text for short (Pattern: When service should (not) occur; ; Resource: When scheduled) - no reason provided occurrence[x] does not contain the recommended logical text for definition (Pattern: The date or time(s) at which the activity or service is desired to occur or not occur.; ; Resource: The time when this communication is to occur.) - no reason provided

~~Names are different.~~ Type Mismatch.

DeviceRequest

DeviceRequest.occurrence[x] : dateTime, Period, Timing [0..1]

occurrence[x] does not contain the recommended logical text for short (Pattern: When service should (not) occur; ; Resource: Desired time or schedule for use) - no reason provided occurrence[x] does not contain the recommended logical text for definition (Pattern: The date or time(s) at which the activity or service is desired to occur or not occur.; ; Resource: The timing schedule for the use of the device. The Schedule data type allows many different expressions, for example. "Every 8 hours"; "Three times a day"; "1/2 an hour before breakfast for 10 days from 23-Dec 2011:"; "15 Oct 2013, 17 Oct 2013 and 1 Nov 2013".) - no reason provided

ImmunizationRecommendation

ImmunizationRecommendation.recommendation.dateCriterion : BackboneElement [0..*]

~~Violation (pattern = 1, resource =~~

differs (Pattern: 1; ; Resource:

- no reason provided Resource does not support types that are part of the pattern (Pattern: dateTime, Period, Timing) - no reason provided Resource supports types that are not part of the pattern (; Resource: BackboneElement) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided occurrence[x] does not contain the recommended logical text for short (Pattern: When service should (not) occur; ; Resource: Dates governing proposed immunization) - no reason provided occurrence[x] does not contain the recommended logical text for definition (Pattern:

~~type 'BackboneElement'~~

date or time(s) at which the activity or service

desired to occur or

~~legal according~~

occur.; ; Resource: Vaccine date recommendations. For example, earliest date

~~the pattern (BackboneElement vs dateTime|Period|Timing)~~

administer, latest date to administer, etc.) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

~~MedicationRequest~~ NutritionOrder

~~MedicationRequest.dosageInstruction~~ NutritionOrder.oralDiet.schedule.timing : ~~Dosage~~ Timing [0..*]

~~Violation (pattern = 1, resource =~~

differs (Pattern: 1; ; Resource:

- no reason provided Resource does not support types that are part of the pattern (Pattern: dateTime, Period) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided occurrence[x] does not contain the recommended logical text for short (Pattern: When service should (not) occur; ; Resource: Scheduled frequency of diet) - no reason provided occurrence[x] does not contain the recommended logical text for definition (Pattern:

~~type 'Dosage'~~

date or time(s) at which the activity or service

desired to occur or

~~legal according~~

occur.; ; Resource: The time period and frequency at which the diet should be given. The diet should be given for the combination of all schedules if more than one schedule is present.) - no reason provided

NutritionOrder.supplement.schedule.timing : Timing [0..*]

Maximum Cardinality differs (Pattern: 1; ; Resource: *) - no reason provided Resource does not support types that are part of the pattern (Pattern: dateTime, Period) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided occurrence[x] does not contain the recommended logical text for short (Pattern: When service should (not) occur; ; Resource: Scheduled frequency of diet) - no reason provided occurrence[x] does not contain the recommended logical text for definition (Pattern: The date or time(s) at which the activity or service is desired

occur or not occur.; ; Resource: The time period and frequency at which the supplement should be given. The supplement should be given for the combination of all schedules if more than one schedule is present.) - no reason provided

NutritionOrder.enteralFormula.administration.schedule.timing : Timing [0..*]

Maximum Cardinality differs (Pattern: 1; ; Resource: *) - no reason provided Resource does not support types that are part of

~~(Dosage vs dateTime|Period|Timing)~~

(Pattern: dateTime, Period) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided occurrence[x] does not contain the recommended logical text for short (Pattern: When service should (not) occur; ; Resource: Scheduled frequency of enteral formula) - no reason provided occurrence[x] does not contain the recommended logical text for definition (Pattern: The date or time(s) at which the activity or service is desired to occur or not occur.; ; Resource: The time period and frequency at which the enteral formula should be given. The enteral formula should be given for the combination of all schedules if more than one schedule is present.) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

~~NutritionOrder~~ RequestOrchestration

NutritionOrder.oralDiet.schedule : Timing [0..*] Maximum Cardinality Violation (pattern = 1, resource = *) NutritionOrder.supplement.schedule : Timing [0..*] Maximum Cardinality Violation (pattern = 1, resource = *) NutritionOrder.enteralFormula.administration.schedule RequestOrchestration.action.timing[x] : dateTime, Age, Period, Duration, Range, Timing [0..1]

Resource supports types that are not part of the pattern (; Resource: Duration, Range, Age) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided occurrence[x] does not contain the recommended logical text for short (Pattern: When service should (not) occur; ; Resource: When the action should take place) - no reason provided occurrence[x] does not contain the recommended logical text for definition (Pattern: The date or time(s) at which the activity or service is desired to occur or not occur.; ; Resource: An optional value describing when the action should be performed.) - no reason provided

Names are different.
~~Cardinality Problem.~~ Type Mismatch.

~~RequestGroup~~ ServiceRequest

~~RequestGroup.action.timing[x]~~ ServiceRequest.occurrence[x] : dateTime, ~~Age,~~ Period, ~~Duration, Range,~~ Timing [0..1]

~~The type 'Age' is~~

occurrence[x] does

~~legal according to~~

contain

~~pattern (dateTime, Age, Period, Duration, Range, Timing vs dateTime|Period|Timing) , The type 'Duration' is~~

recommended logical text for short (Pattern: When service should (not) occur; ; Resource: When service should occur) - no reason provided occurrence[x] does

~~legal according to~~

contain

~~pattern (dateTime, Age, Period, Duration, Range, Timing vs dateTime|Period|Timing) ,~~

recommended logical text for definition (Pattern:

~~type 'Range'~~

date or time(s) at which the activity or service

~~not legal according~~

desired

occur or not occur.; ; Resource: The date/time at which

~~pattern (dateTime, Age, Period, Duration, Range, Timing vs dateTime|Period|Timing)~~

requested service should occur.) - no reason provided

~~Names are different.~~

~~ServiceRequest~~ SupplyRequest

~~ServiceRequest.occurrence[x]~~ SupplyRequest.occurrence[x] : dateTime, Period, Timing [0..1]

occurrence[x] does not contain the recommended logical text for short (Pattern: When service should (not) occur; ; Resource: When the request should be fulfilled) - no reason provided occurrence[x] does not contain the recommended logical text for definition (Pattern: The date or time(s) at which the activity or service is desired to occur or not occur.; ; Resource: When the request should be fulfilled.) - no reason provided

~~SupplyRequest~~ Task

~~SupplyRequest.occurrence[x]~~ Task.requestedPeriod : ~~dateTime, Period, Timing~~ Period [0..1]

Resource does not support types that are part of the pattern (Pattern: dateTime, Timing) - no reason provided occurrence[x] does not contain the recommended logical text for short (Pattern: When service should (not) occur; ; Resource: When the task should be performed) - no reason provided occurrence[x] does not contain the recommended logical text for definition (Pattern: The date or time(s) at which the activity or service is desired to occur or not occur.; ; Resource: Indicates the start and/or end of the period of time when completion of the task is desired to take place.) - no reason provided

Names are different.
Type Mismatch.

Request.authoredOn

Request.authoredOn : dateTime [0..1]

Resource

Matches

Issues

Tasks

Status

Notes

Appointment

Appointment.created : dateTime [0..1]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided authoredOn does not contain the recommended logical text for short (Pattern: When request was created/transitioned to active; ; Resource: The date that this appointment was initially created) - no reason provided authoredOn does not contain the recommended logical text for definition (Pattern: For draft appointments, indicates the date of initial creation. For requests with other statuses, indicates the date of activation.; ; Resource: The date that this appointment was initially created. This could be different to the meta.lastModified value on the initial entry, as this could have been before the resource was created on the FHIR server, and should remain unchanged over the lifespan of the appointment.) - no reason provided

Names are different.

CarePlan

CarePlan.created : dateTime [0..1]

authoredOn does not contain the recommended logical text for short (Pattern: When request was created/transitioned to active; ; Resource: Date record was first recorded) - no reason provided authoredOn does not contain the recommended logical text for definition (Pattern: For draft care plans, indicates the date of initial creation. For requests with other statuses, indicates the date of activation.; ; Resource: Represents when this particular CarePlan record was created in the system, which is often a system-generated date.) - no reason provided

Names are different.

Claim

Claim.created : dateTime [1..1]

Minimum Cardinality differs (Pattern: 0; ; Resource: 1) - no reason provided authoredOn does not contain the recommended logical text for short (Pattern: When request was created/transitioned to active; ; Resource: Resource creation date) - no reason provided authoredOn does not contain the recommended logical text for definition (Pattern: For draft claims, indicates the date of initial creation. For requests with other statuses, indicates the date of activation.; ; Resource: The date this resource was created.) - no reason provided

Names are different.
Cardinality Problem.

CommunicationRequest

CommunicationRequest.authoredOn : dateTime [0..1]

authoredOn does not contain the recommended logical text for short (Pattern: When request was created/transitioned to active; ; Resource: When request transitioned to being actionable) - no reason provided authoredOn does not contain the recommended logical text for definition (Pattern: For draft communication requests, indicates the date of initial creation. For requests with other statuses, indicates the date of activation.; ; Resource: For draft requests, indicates the date of initial creation. For requests with other statuses, indicates the date of activation.) - no reason provided

CoverageEligibilityRequest

CoverageEligibilityRequest.created : dateTime [1..1]

Minimum Cardinality differs (Pattern: 0; ; Resource: 1) - no reason provided authoredOn does not contain the recommended logical text for short (Pattern: When request was created/transitioned to active; ; Resource: Creation date) - no reason provided authoredOn does not contain the recommended logical text for definition (Pattern: For draft coverage eligibility requests, indicates the date of initial creation. For requests with other statuses, indicates the date of activation.; ; Resource: The date when this resource was created.) - no reason provided

Names are different.
Cardinality Problem.

DeviceRequest

DeviceRequest.authoredOn : dateTime [0..1]

authoredOn does not contain the recommended logical text for short (Pattern: When request was created/transitioned to active; ; Resource: When recorded) - no reason provided authoredOn does not contain the recommended logical text for definition (Pattern: For draft device requests, indicates the date of initial creation. For requests with other statuses, indicates the date of activation.; ; Resource: When the request transitioned to being actionable.) - no reason provided

EnrollmentRequest

EnrollmentRequest.created : dateTime [0..1]

Names are different.

ImmunizationRecommendation

ImmunizationRecommendation.date : dateTime [1..1]

Minimum Cardinality differs (Pattern: 0; ; Resource: 1) - no reason provided authoredOn does not contain the recommended logical text for short (Pattern: When request was created/transitioned to active; ; Resource: Date recommendation(s) created) - no reason provided authoredOn does not contain the recommended logical text for definition (Pattern: For draft immunization recommendations, indicates the date of initial creation. For requests with other statuses, indicates the date of activation.; ; Resource: The date the immunization recommendation(s) were created.) - no reason provided

Names are different.
Cardinality Problem.

MedicationRequest

MedicationRequest.authoredOn : dateTime [0..1]

authoredOn does not contain the recommended logical text for short (Pattern: When request was created/transitioned to active; ; Resource: When request was initially authored) - no reason provided authoredOn does not contain the recommended logical text for definition (Pattern: For draft medication requests, indicates the date of initial creation. For requests with other statuses, indicates the date of activation.; ; Resource: The date (and perhaps time) when the prescription was initially written or authored on.) - no reason provided

NutritionOrder

NutritionOrder.dateTime : dateTime [1..1]

Minimum Cardinality differs (Pattern: 0; ; Resource: 1) - no reason provided authoredOn does not contain the recommended logical text for short (Pattern: When request was created/transitioned to active; ; Resource: Date and time the nutrition order was requested) - no reason provided authoredOn does not contain the recommended logical text for definition (Pattern: For draft nutrition orders, indicates the date of initial creation. For requests with other statuses, indicates the date of activation.; ; Resource: The date and time that this nutrition order was requested.) - no reason provided

Names are different.
Cardinality Problem.

~~RequestGroup~~ RequestOrchestration

~~RequestGroup.authoredOn~~ RequestOrchestration.authoredOn : dateTime [0..1]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided authoredOn does not contain the recommended logical text for short (Pattern: When request was created/transitioned to active; ; Resource: When the request orchestration was authored) - no reason provided authoredOn does not contain the recommended logical text for definition (Pattern: For draft request orchestrations, indicates the date of initial creation. For requests with other statuses, indicates the date of activation.; ; Resource: Indicates when the request orchestration was created.) - no reason provided

ServiceRequest

ServiceRequest.authoredOn : dateTime [0..1]

authoredOn does not contain the recommended logical text for short (Pattern: When request was created/transitioned to active; ; Resource: Date request signed) - no reason provided authoredOn does not contain the recommended logical text for definition (Pattern: For draft service requests, indicates the date of initial creation. For requests with other statuses, indicates the date of activation.; ; Resource: When the request transitioned to being actionable.) - no reason provided

SupplyRequest

SupplyRequest.authoredOn : dateTime [0..1]

authoredOn does not contain the recommended logical text for short (Pattern: When request was created/transitioned to active; ; Resource: When the request was made) - no reason provided authoredOn does not contain the recommended logical text for definition (Pattern: For draft supply requests, indicates the date of initial creation. For requests with other statuses, indicates the date of activation.; ; Resource: When the request was made.) - no reason provided

Task

Task.authoredOn : dateTime [0..1]

Transport

Transport.authoredOn : dateTime [0..1]

VisionPrescription

VisionPrescription.dateWritten : dateTime [1..1]

Minimum Cardinality differs (Pattern: 0; ; Resource: 1) - no reason provided authoredOn does not contain the recommended logical text for short (Pattern: When request was created/transitioned to active; ; Resource: When prescription was authorized) - no reason provided authoredOn does not contain the recommended logical text for definition (Pattern: For draft vision prescriptions, indicates the date of initial creation. For requests with other statuses, indicates the date of activation.; ; Resource: The date (and perhaps time) when the prescription was written.) - no reason provided

Names are different.
Cardinality Problem.

Request.requester

Resource

Matches

Issues

Tasks

Status

Notes

CarePlan

~~CarePlan.author~~ CarePlan.custodian : Reference [0..1]

Resource supports types that are not part of the pattern (; Resource: Reference(CareTeam)) - no reason provided requester does not contain the recommended logical text for short (Pattern: Who/what is requesting service; ; Resource: Who is the designated responsible party) - no reason provided requester does not contain the recommended logical text for definition (Pattern: Who initiated the {{request}} and has responsibility for its activation.; ; Resource: When populated, the custodian is responsible for the care plan. The care plan is attributed to the custodian.) - no reason provided

Names are different.
Type Mismatch.

Claim

Claim.provider : Reference ~~[1..1]~~ [0..1]

Resource does not support types that are part of the pattern (Pattern: Reference(Patient,RelatedPerson,Device)) - no reason provided requester does not contain the recommended logical text for short (Pattern: Who/what is requesting service; ; Resource: Party responsible for the claim) - no reason provided requester does not contain the recommended logical text for definition (Pattern: Who initiated the {{request}} and has responsibility for its activation.; ; Resource: The provider which is responsible for the claim, predetermination or preauthorization.) - no reason provided

Names are different.
Type Mismatch.

CommunicationRequest

CommunicationRequest.requester : Reference [0..1]

requester does not contain the recommended logical text for short (Pattern: Who/what is requesting service; ; Resource: Who asks for the information to be shared) - no reason provided requester does not contain the recommended logical text for definition (Pattern: Who initiated the {{request}} and has responsibility for its activation.; ; Resource: The device, individual, or organization who asks for the information to be shared.) - no reason provided

CoverageEligibilityRequest

CoverageEligibilityRequest.provider : Reference [0..1]

Resource does not support types that are part of the pattern (Pattern: Reference(Patient,RelatedPerson,Device)) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided requester does not contain the recommended logical text for short (Pattern: Who/what is requesting service; ; Resource: Party responsible for the request) - no reason provided requester does not contain the recommended logical text for definition (Pattern: Who initiated the {{request}} and has responsibility for its activation.; ; Resource: The provider which is responsible for the request.) - no reason provided

CoverageEligibilityRequest.item.provider : Reference [0..1]

Resource does not support types that are part of the pattern (Pattern: Reference(Organization,Patient,RelatedPerson,Device)) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided requester does not contain the recommended logical text for short (Pattern: Who/what is requesting service; ; Resource: Perfoming practitioner) - no reason provided requester does not contain the recommended logical text for definition (Pattern: Who initiated the {{request}} and has responsibility for its activation.; ; Resource: The practitioner who is responsible for the product or service to be rendered to the patient.) - no reason provided

Names are different.
Type Mismatch.

DeviceRequest

DeviceRequest.requester : Reference [0..1]

Resource does not support types that are part of the pattern (Pattern: Reference(Patient,RelatedPerson)) - no reason provided requester does not contain the recommended logical text for short (Pattern: Who/what is requesting service; ; Resource: Who/what submitted the device request) - no reason provided requester does not contain the recommended logical text for definition (Pattern: Who initiated the {{request}} and has responsibility for its activation.; ; Resource: The individual or entity who initiated the request and has responsibility for its activation.) - no reason provided

Type Mismatch.

EnrollmentRequest

EnrollmentRequest.provider : Reference [0..1]

Resource does not support types that are part of the pattern (Pattern: Reference(Patient,RelatedPerson,Device)) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided requester does not contain the recommended logical text for short (Pattern: Who/what is requesting service; ; Resource: Responsible practitioner) - no reason provided requester does not contain the recommended logical text for definition (Pattern: Who initiated the {{request}} and has responsibility for its activation.; ; Resource: The practitioner who is responsible for the services rendered to the patient.) - no reason provided

Names are different.
Type Mismatch.

MedicationRequest

MedicationRequest.requester : Reference [0..1]

requester does not contain the recommended logical text for short (Pattern: Who/what is requesting service; ; Resource: Who/What requested the Request) - no reason provided requester does not contain the recommended logical text for definition (Pattern: Who initiated the {{request}} and has responsibility for its activation.; ; Resource: The individual, organization, or device that initiated the request and has responsibility for its activation.) - no reason provided

NutritionOrder

NutritionOrder.orderer : Reference [0..1]

Resource does not support types that are part of the pattern (Pattern: Reference(Organization,Patient,RelatedPerson,Device)) - no reason provided requester does not contain the recommended logical text for short (Pattern: Who/what is requesting service; ; Resource: Who ordered the diet, formula or nutritional supplement) - no reason provided requester does not contain the recommended logical text for definition (Pattern: Who initiated the {{request}} and has responsibility for its activation.; ; Resource: The practitioner that holds legal responsibility for ordering the diet, nutritional supplement, or formula feedings.) - no reason provided

Names are different.
Type Mismatch.

~~RequestGroup~~ RequestOrchestration

~~RequestGroup.author~~ RequestOrchestration.author : Reference [0..1]

Resource does not support types that are part of the pattern (Pattern: Reference(Organization,Patient,RelatedPerson)) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided requester does not contain the recommended logical text for short (Pattern: Who/what is requesting service; ; Resource: Device or practitioner that authored the request orchestration) - no reason provided requester does not contain the recommended logical text for definition (Pattern: Who initiated the {{request}} and has responsibility for its activation.; ; Resource: Provides a reference to the author of the request orchestration.) - no reason provided

Names are different.
Type Mismatch.

ServiceRequest

ServiceRequest.requester : Reference [0..1]

requester does not contain the recommended logical text for definition (Pattern: Who initiated the {{request}} and has responsibility for its activation.; ; Resource: The individual who initiated the request and has responsibility for its activation.) - no reason provided

SupplyRequest

SupplyRequest.requester : Reference [0..1]

Resource supports types that are not part of the pattern (; Resource: Reference(CareTeam)) - no reason provided requester does not contain the recommended logical text for short (Pattern: Who/what is requesting service; ; Resource: Individual making the request) - no reason provided requester does not contain the recommended logical text for definition (Pattern: Who initiated the {{request}} and has responsibility for its activation.; ; Resource: The device, practitioner, etc. who initiated the request.) - no reason provided

Type Mismatch.

Task

Task.requester : Reference [0..1]

requester does not contain the recommended logical text for short (Pattern: Who/what is requesting service; ; Resource: Who is asking for task to be done) - no reason provided requester does not contain the recommended logical text for definition (Pattern: Who initiated the {{request}} and has responsibility for its activation.; ; Resource: The creator of the task.) - no reason provided

Transport

Transport.requester : Reference [0..1]

requester does not contain the recommended logical text for short (Pattern: Who/what is requesting service; ; Resource: Who is asking for transport to be done) - no reason provided requester does not contain the recommended logical text for definition (Pattern: Who initiated the {{request}} and has responsibility for its activation.; ; Resource: The creator of the transport.) - no reason provided

VisionPrescription

VisionPrescription.prescriber : Reference [1..1]

Minimum Cardinality differs (Pattern: 0; ; Resource: 1) - no reason provided Resource does not support types that are part of the pattern (Pattern: Reference(Organization,Patient,RelatedPerson,Device)) - no reason provided requester does not contain the recommended logical text for short (Pattern: Who/what is requesting service; ; Resource: Who authorized the vision prescription) - no reason provided requester does not contain the recommended logical text for definition (Pattern: Who initiated the {{request}} and has responsibility for its activation.; ; Resource: The healthcare professional responsible for authorizing the prescription.) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

Request.reported[x]

Resource

Matches

Issues

Tasks

Status

Notes

Request.performerType

Request.performerType : CodeableConcept [0..1]

Resource

Matches

Issues

Tasks

Status

Notes

AppointmentResponse

AppointmentResponse.participantType : CodeableConcept [0..*]

~~Violation (pattern = 1, resource =~~

differs (Pattern: 1; ; Resource:

- no reason provided Binding strengths differ (Pattern: example; ; Resource: extensible) - no reason provided performerType does not contain the recommended logical text for short (Pattern: Desired kind of service performer; ; Resource: Role of participant in the appointment) - no reason provided performerType does not contain the recommended logical text for definition (Pattern: The type of individual that is desired to act upon/ not act upon the {{request}}.; ; Resource: Role of participant in the appointment.) - no reason provided performerType does not contain the recommended logical text for comments (Pattern: If specified without indicating a performer, this indicates that the performer must be (or can't be) of the specified type. If specified with a performer then it indicates the requirements of the performer if the designated performer is not available. If doNotPerform is true, then only one of performerType and performer should be present.; ; Resource: The role of the participant can be used to declare what the actor will be doing in the scope of the referenced appointment. If the actor is not specified, then it is expected that the actor will be filled in at a later stage of planning. This value SHALL be the same as specified on the referenced Appointment so that they can be matched, and subsequently updated.) - no reason provided

Names are different.
Cardinality Problem.

~~DeviceRequest~~ MedicationRequest

~~DeviceRequest.performerType~~ MedicationRequest.performerType : CodeableConcept [0..1]

Binding strengths differ (Pattern: example; ; Resource: extensible) - no reason provided performerType does not contain the recommended logical text for short (Pattern: Desired kind of service performer; ; Resource: Desired kind of performer of the medication administration) - no reason provided performerType does not contain the recommended logical text for definition (Pattern: The type of individual that is desired to act upon/ not act upon the {{request}}.; ; Resource: Indicates the type of performer of the administration of the medication.) - no reason provided performerType does not contain the recommended logical text for comments (Pattern: If specified without indicating a performer, this indicates that the performer must be (or can't be) of the specified type. If specified with a performer then it indicates the requirements of the performer if the designated performer is not available. If doNotPerform is true, then only one of performerType and performer should be present.; ; Resource: If specified without indicating a performer, this indicates that the performer must be of the specified type. If specified with a performer then it indicates the requirements of the performer if the designated performer is not available.) - no reason provided

~~MedicationRequest~~ ServiceRequest

~~MedicationRequest.performerType~~ ServiceRequest.performerType : CodeableConcept [0..1]

performerType does not contain the recommended logical text for short (Pattern: Desired kind of service performer; ; Resource: Performer role) - no reason provided performerType does not contain the recommended logical text for definition (Pattern: The type of individual that is desired to act upon/ not act upon the {{request}}.; ; Resource: Desired type of performer for doing the requested service.) - no reason provided performerType does not contain the recommended logical text for comments (Pattern: If specified without indicating a performer, this indicates that the performer must be (or can't be) of the specified type. If specified with a performer then it indicates the requirements of the performer if the designated performer is not available. If doNotPerform is true, then only one of performerType and performer should be present.; ; Resource: This is a role, not a participation type. In other words, does not describe the task but describes the capacity. For example, “compounding pharmacy”, “psychiatrist” or “internal referral”.) - no reason provided

~~ServiceRequest~~ Task

~~ServiceRequest.performerType~~ Task.requestedPerformer : ~~CodeableConcept [0..1]~~ CodeableReference [0..*]

Maximum Cardinality differs (Pattern: 1; ; Resource: *) - no reason provided Resource does not support types that are part of the pattern (Pattern: CodeableConcept) - no reason provided Resource supports types that are not part of the pattern (; Resource: CodeableReference(Practitioner,PractitionerRole,Organization,CareTeam,HealthcareService,Patient,Device,RelatedPerson)) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided performerType does not contain the recommended logical text for short (Pattern: Desired kind of service performer; ; Resource: Who should perform Task) - no reason provided performerType does not contain the recommended logical text for definition (Pattern: The type of individual that is desired to act upon/ not act upon the {{request}}.; ; Resource: The kind of participant or specific participant that should perform the task.) - no reason provided performerType does not contain the recommended logical text for comments (Pattern: If specified without indicating a performer, this indicates that the performer must be (or can't be) of the specified type. If specified with a performer then it indicates the requirements of the performer if the designated performer is not available. If doNotPerform is true, then only one of performerType and performer should be present.; ; Resource: ) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

Transport

Transport.performerType : CodeableConcept [0..*]

Maximum Cardinality differs (Pattern: 1; ; Resource: *) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided performerType does not contain the recommended logical text for short (Pattern: Desired kind of service performer; ; Resource: Requested performer) - no reason provided performerType does not contain the recommended logical text for definition (Pattern: The type of individual that is desired to act upon/ not act upon the {{request}}.; ; Resource: The kind of participant that should perform the transport.) - no reason provided performerType does not contain the recommended logical text for comments (Pattern: If specified without indicating a performer, this indicates that the performer must be (or can't be) of the specified type. If specified with a performer then it indicates the requirements of the performer if the designated performer is not available. If doNotPerform is true, then only one of performerType and performer should be present.; ; Resource: ) - no reason provided

Cardinality Problem.

Request.performer

Resource

Matches

Issues

Tasks

Status

Notes

Appointment

Appointment.participant : BackboneElement [1..*]

Minimum Cardinality differs (Pattern: 0; ; Resource: 1) - no reason provided

~~Violation (pattern = 1, resource =~~

differs (Pattern: 1; ; Resource:

~~The type 'BackboneElement' is~~

- no reason provided Resource does

~~legal according to~~

support types that are part of

(Pattern: Reference(Practitioner,PractitionerRole,Organization,CareTeam,HealthcareService,Patient,Device,RelatedPerson)) - no reason provided Resource supports types that are not part of the pattern (; Resource: BackboneElement) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided performer does not contain the recommended logical text for short (Pattern: Specific desired (non)performer; ; Resource: Participants involved in appointment) - no reason provided performer does not contain the recommended logical text for definition (Pattern: Indicates who or what is being asked to perform (or not perform) the {{request}}.; ; Resource: List of participants involved in the appointment.) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

AppointmentResponse

AppointmentResponse.actor : Reference [0..1]

Resource does not support types that are part of the pattern (Pattern: Reference(Organization,CareTeam)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(Group,Location)) - no reason provided performer does not contain the recommended logical text for short (Pattern: Specific desired (non)performer; ; Resource: Person(s), Location, HealthcareService, or Device) - no reason provided performer does not contain the recommended logical text for definition (Pattern: Indicates who or what is being asked to perform (or not perform) the {{request}}.; ; Resource: A Person, Location, HealthcareService, or Device that is participating in the appointment.) - no reason provided

Names are different.
Type Mismatch.

CarePlan

CarePlan.careTeam : Reference [0..*]

~~Violation (pattern = 1, resource = *) CarePlan.activity.detail.performer : Reference [0..*] Maximum Cardinality Violation (pattern = 1, resource =~~

differs (Pattern: 1; ; Resource:

- no reason provided Resource does not support types that are part of the pattern (Pattern: Reference(Practitioner,PractitionerRole,Organization,HealthcareService,Patient,Device,RelatedPerson)) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided performer does not contain the recommended logical text for short (Pattern: Specific desired (non)performer; ; Resource: Who's involved in plan?) - no reason provided performer does not contain the recommended logical text for definition (Pattern: Indicates who or what is being asked to perform (or not perform) the {{request}}.; ; Resource: Identifies all people and organizations who are expected to be involved in the care envisioned by this plan.) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

Claim

Claim.insurer : Reference [0..1]

Resource does not support types that are part of the pattern (Pattern: Reference(Practitioner,PractitionerRole,CareTeam,HealthcareService,Patient,Device,RelatedPerson)) - no reason provided performer does not contain the recommended logical text for short (Pattern: Specific desired (non)performer; ; Resource: Target) - no reason provided performer does not contain the recommended logical text for definition (Pattern: Indicates who or what is being asked to perform (or not perform) the {{request}}.; ; Resource: The Insurer who is target of the request.) - no reason provided

Names are different.
Type Mismatch.

CommunicationRequest

CommunicationRequest.recipient : Reference [0..*]

~~Violation (pattern = 1, resource =~~

differs (Pattern: 1; ; Resource:

- no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(Group,Endpoint)) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided performer does not contain the recommended logical text for short (Pattern: Specific desired (non)performer; ; Resource: Who to share the information with) - no reason provided performer does not contain the recommended logical text for definition (Pattern: Indicates who or what is being asked to perform (or not perform) the {{request}}.; ; Resource: The entity (e.g. person, organization, clinical information system, device, group, or care team) which is the intended target of the communication.) - no reason provided

~~CommunicationRequest.sender~~ CommunicationRequest.informationProvider : Reference ~~[0..1]~~ [0..*]

~~Names are different.~~

Maximum

~~Problem. Contract Contract.term.action.type : CodeableConcept [1..1] The type 'CodeableConcept'~~

differs (Pattern: 1; ; Resource: *) - no reason provided Resource does not support types that are part of the pattern (Pattern: Reference(CareTeam)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(Endpoint)) - no reason provided performer does not contain the recommended logical text for short (Pattern: Specific desired (non)performer; ; Resource: Who should share the information) - no reason provided performer does not contain the recommended logical text for definition (Pattern: Indicates who or what

being asked to perform (or

~~legal according~~

perform) the {{request}}.; ; Resource: The entity (e.g. person, organization, clinical information system, or device) which is

source of the communication.) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

CoverageEligibilityRequest

CoverageEligibilityRequest.insurer : Reference [1..1]

Minimum Cardinality differs (Pattern: 0; ; Resource: 1) - no reason provided Resource does not support types that are part of the pattern (Pattern: Reference(Practitioner,PractitionerRole,CareTeam,HealthcareService,Patient,Device,RelatedPerson)) - no reason provided performer does not contain the recommended logical text for short (Pattern: Specific desired (non)performer; ; Resource: Coverage issuer) - no reason provided performer does not contain the recommended logical text for definition (Pattern: Indicates who or what is being asked to perform (or not perform) the {{request}}.; ; Resource: The Insurer who issued the coverage in question and is the recipient of the request.) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

DeviceRequest

DeviceRequest.performer : ~~Reference~~ CodeableReference [0..1]

Resource does not support types that are part of the pattern (Pattern: Reference(Practitioner,PractitionerRole,Organization,CareTeam,HealthcareService,Patient,Device,RelatedPerson)) - no reason provided Resource supports types that are not part of the pattern (; Resource: CodeableReference(Practitioner,PractitionerRole,Organization,CareTeam,HealthcareService,Patient,Device,RelatedPerson)) - no reason provided performer does not contain the recommended logical text for short (Pattern: Specific desired (non)performer; ; Resource: Requested Filler) - no reason provided performer does not contain the recommended logical text for definition (Pattern: Indicates who or what is being asked to perform (or not perform) the {{request}}.; ; Resource: The desired individual or entity to provide the device to the subject of the request (e.g., patient, location).) - no reason provided

Type Mismatch.

EnrollmentRequest

EnrollmentRequest.insurer : Reference [0..1]

Resource does not support types that are part of the pattern (Pattern: Reference(Practitioner,PractitionerRole,CareTeam,HealthcareService,Patient,Device,RelatedPerson)) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided performer does not contain the recommended logical text for short (Pattern: Specific desired (non)performer; ; Resource: Target) - no reason provided performer does not contain the recommended logical text for definition (Pattern: Indicates who or what is being asked to perform (or not perform) the {{request}}.; ; Resource: The Insurer who is target of the request.) - no reason provided

Names are different.
Type Mismatch.

MedicationRequest

MedicationRequest.performer : Reference ~~[0..1]~~ [0..*]

Maximum Cardinality differs (Pattern: 1; ; Resource: *) - no reason provided Resource does not support types that are part of the pattern (Pattern: Reference(Device)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(DeviceDefinition)) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided performer does not contain the recommended logical text for short (Pattern: Specific desired (non)performer; ; Resource: Intended performer of administration) - no reason provided performer does not contain the recommended logical text for definition (Pattern: Indicates who or what is being asked to perform (or not perform) the {{request}}.; ; Resource: The specified desired performer of the medication treatment (e.g. the performer of the medication administration). For devices, this is the device that is intended to perform the administration of the medication. An IV Pump would be an example of a device that is performing the administration. Both the IV Pump and the practitioner that set the rate or bolus on the pump can be listed as performers.) - no reason provided

Type Mismatch.
Cardinality Problem.

~~RequestGroup~~ RequestOrchestration

~~RequestGroup.action.participant~~ RequestOrchestration.action.participant : ~~Reference~~ BackboneElement [0..*]

~~Violation (pattern = 1, resource =~~

differs (Pattern: 1; ; Resource:

- no reason provided Resource does not support types that are part of the pattern (Pattern: Reference(Practitioner,PractitionerRole,Organization,CareTeam,HealthcareService,Patient,Device,RelatedPerson)) - no reason provided Resource supports types that are not part of the pattern (; Resource: BackboneElement) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided performer does not contain the recommended logical text for short (Pattern: Specific desired (non)performer; ; Resource: Who should perform the action) - no reason provided performer does not contain the recommended logical text for definition (Pattern: Indicates who or what is being asked to perform (or not perform) the {{request}}.; ; Resource: The participant that should perform or be responsible for this action.) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

ServiceRequest

ServiceRequest.performer : Reference [0..*]

~~Violation (pattern = 1, resource =~~

differs (Pattern: 1; ; Resource:

- no reason provided performer does not contain the recommended logical text for short (Pattern: Specific desired (non)performer; ; Resource: Requested performer) - no reason provided performer does not contain the recommended logical text for definition (Pattern: Indicates who or what is being asked to perform (or not perform) the {{request}}.; ; Resource: The desired performer for doing the requested service. For example, the surgeon, dermatopathologist, endoscopist, etc.) - no reason provided

Cardinality Problem.

SupplyRequest

SupplyRequest.supplier : Reference [0..*]

~~Violation (pattern = 1, resource =~~

differs (Pattern: 1; ; Resource:

- no reason provided Resource does not support types that are part of the pattern (Pattern: Reference(Practitioner,PractitionerRole,CareTeam,Patient,Device,RelatedPerson)) - no reason provided performer does not contain the recommended logical text for short (Pattern: Specific desired (non)performer; ; Resource: Who is intended to fulfill the request) - no reason provided performer does not contain the recommended logical text for definition (Pattern: Indicates who or what is being asked to perform (or not perform) the {{request}}.; ; Resource: Who is intended to fulfill the request.) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

~~CommunicationRequest~~ Task

~~CommunicationRequest.reasonCode~~ Task.owner : ~~CodeableConcept [0..*]~~ Reference [0..1]

Resource does not support types that are part of the pattern (Pattern: Reference(HealthcareService,Device)) - no reason provided performer does not contain the recommended logical text for short (Pattern: Specific desired (non)performer; ; Resource: Responsible individual) - no reason provided performer does not contain the recommended logical text for definition (Pattern: Indicates who or what is being asked to perform (or not perform) the {{request}}.; ; Resource: Party responsible for managing task execution.) - no reason provided

Names are different.
Type Mismatch.

~~Contract~~ Transport

~~Contract.term.action.intent~~ Transport.owner : ~~CodeableConcept [1..1]~~ Reference [0..1]

performer does not contain the recommended logical text for short (Pattern: Specific desired (non)performer; ; Resource: Responsible individual) - no reason provided performer does not contain the recommended logical text for definition (Pattern: Indicates who or what is being asked to perform (or not perform) the {{request}}.; ; Resource: Individual organization or Device currently responsible for transport execution.) - no reason provided

Names are different.

~~RequestGroup~~ Request.deliverTo

Resource

~~Task~~ Matches

~~Task.location : Reference [0..1] The type 'Reference' is not legal according to the pattern (Reference vs CodeableConcept)~~ Issues

~~Names are different.~~ Tasks

Status

Notes

~~Request.reasonReference~~ Request.reason

Resource

Matches

Issues

Tasks

Status

Notes

Appointment

~~Appointment.reasonReference~~ Appointment.reason : ~~Reference~~ CodeableReference [0..*]

reason does not contain the recommended logical text for short (Pattern: Why is service (not) needed?; ; Resource: Reason this appointment is scheduled) - no reason provided reason does not contain the recommended logical text for definition (Pattern: Describes why the request is being made in coded or textual form, or Indicates another resource whose existence justifies this request.; ; Resource: The reason that this appointment is being scheduled. This is more clinical than administrative. This can be coded, or as specified using information from another resource. When the patient arrives and the encounter begins it may be used as the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure.) - no reason provided reason does not contain the recommended logical text for comments (Pattern: Textual reasons can be captured using reasonCode.text. If doNoPerform is true, this will be the reason why the request is being made to not act.; ; Resource: ) - no reason provided

CarePlan

CarePlan.addresses : ~~Reference [0..*] CarePlan.activity.detail.reasonReference : Reference~~ CodeableReference [0..*]

reason does not contain the recommended logical text for short (Pattern: Why is service (not) needed?; ; Resource: Health issues this plan addresses) - no reason provided reason does not contain the recommended logical text for definition (Pattern: Describes why the request is being made in coded or textual form, or Indicates another resource whose existence justifies this request.; ; Resource: Identifies the conditions/problems/concerns/diagnoses/etc. whose management and/or mitigation are handled by this plan.) - no reason provided reason does not contain the recommended logical text for comments (Pattern: Textual reasons can be captured using reasonCode.text. If doNoPerform is true, this will be the reason why the request is being made to not act.; ; Resource: Use CarePlan.addresses.concept when a code sufficiently describes the concern (e.g. condition, problem, diagnosis, risk). Use CarePlan.addresses.reference when referencing a resource, which allows more information to be conveyed, such as onset date. CarePlan.addresses.concept and CarePlan.addresses.reference are not meant to be duplicative. For a single concern, either CarePlan.addresses.concept or CarePlan.addresses.reference can be used. CarePlan.addresses.concept may be a summary code, or CarePlan.addresses.reference may be used to reference a very precise definition of the concern using Condition. Both CarePlan.addresses.concept and CarePlan.addresses.reference can be used if they are describing different concerns for the care plan.) - no reason provided

Names are different.

~~Claim~~ CommunicationRequest

~~Claim.diagnosis~~ CommunicationRequest.reason : ~~BackboneElement~~ CodeableReference [0..*]

~~The type 'BackboneElement'~~

reason does not contain the recommended logical text for short (Pattern: Why is service (not) needed?; ; Resource: Why

communication needed?) - no reason provided reason does

~~legal according to~~

contain

~~pattern (BackboneElement vs Reference(Condition|Observation|DiagnosticReport|DocumentReference))~~

recommended logical text for definition (Pattern: Describes why the request is being made in coded or textual form, or Indicates another resource whose existence justifies this request.; ; Resource: Describes why the request is being made in coded or textual form.) - no reason provided reason does not contain the recommended logical text for comments (Pattern: Textual reasons can be captured using reasonCode.text. If doNoPerform is true, this will be the reason why the request is being made to not act.; ; Resource: Textual reasons can be captured using reasonCode.text.) - no reason provided

~~Names are different.~~

~~CommunicationRequest~~ DeviceRequest

~~CommunicationRequest.reasonReference~~ DeviceRequest.reason : ~~Reference~~ CodeableReference [0..*]

reason does not contain the recommended logical text for short (Pattern: Why is service (not) needed?; ; Resource: Coded/Linked Reason for request) - no reason provided reason does not contain the recommended logical text for definition (Pattern: Describes why the request is being made in coded or textual form, or Indicates another resource whose existence justifies this request.; ; Resource: Reason or justification for the use of this device.) - no reason provided reason does not contain the recommended logical text for comments (Pattern: Textual reasons can be captured using reasonCode.text. If doNoPerform is true, this will be the reason why the request is being made to not act.; ; Resource: ) - no reason provided

~~DeviceRequest~~ MedicationRequest

~~DeviceRequest.reasonReference~~ MedicationRequest.reason : ~~Reference~~ CodeableReference [0..*]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided reason does not contain the recommended logical text for short (Pattern: Why is service (not) needed?; ; Resource: Reason or indication for ordering or not ordering the medication) - no reason provided reason does not contain the recommended logical text for definition (Pattern: Describes why the request is being made in coded or textual form, or Indicates another resource whose existence justifies this request.; ; Resource: The reason or the indication for ordering or not ordering the medication.) - no reason provided reason does not contain the recommended logical text for comments (Pattern: Textual reasons can be captured using reasonCode.text. If doNoPerform is true, this will be the reason why the request is being made to not act.; ; Resource: This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonReference.) - no reason provided

~~MedicationRequest~~ RequestOrchestration

~~MedicationRequest.reasonReference~~ RequestOrchestration.reason : ~~Reference~~ CodeableReference [0..*]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided reason does not contain the recommended logical text for short (Pattern: Why is service (not) needed?; ; Resource: Why the request orchestration is needed) - no reason provided reason does not contain the recommended logical text for definition (Pattern: Describes why the request is being made in coded or textual form, or Indicates another resource whose existence justifies this request.; ; Resource: Describes the reason for the request orchestration in coded or textual form.) - no reason provided reason does not contain the recommended logical text for comments (Pattern: Textual reasons can be captured using reasonCode.text. If doNoPerform is true, this will be the reason why the request is being made to not act.; ; Resource: ) - no reason provided

~~RequestGroup~~ ServiceRequest

~~RequestGroup.reasonReference~~ ServiceRequest.reason : ~~Reference~~ CodeableReference [0..*]

reason does not contain the recommended logical text for short (Pattern: Why is service (not) needed?; ; Resource: Explanation/Justification for procedure or service) - no reason provided reason does not contain the recommended logical text for definition (Pattern: Describes why the request is being made in coded or textual form, or Indicates another resource whose existence justifies this request.; ; Resource: An explanation or justification for why this service is being requested in coded or textual form. This is often for billing purposes. May relate to the resources referred to in `supportingInfo`.) - no reason provided reason does not contain the recommended logical text for comments (Pattern: Textual reasons can be captured using reasonCode.text. If doNoPerform is true, this will be the reason why the request is being made to not act.; ; Resource: This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all. To be as specific as possible, a reference to *Observation* or *Condition* should be used if available. Otherwise, use `concept.text` element if the data is free (uncoded) text as shown in the [CT Scan example](servicerequest-example-di.html).) - no reason provided

~~ServiceRequest~~ SupplyRequest

~~ServiceRequest.reasonReference~~ SupplyRequest.reason : ~~Reference~~ CodeableReference [0..*]

~~SupplyRequest~~ Task

~~SupplyRequest.reasonReference~~ Task.reason : ~~Reference~~ CodeableReference [0..*]

IsSummary differs (Pattern: true; ; Resource: false) - no reason provided reason does not contain the recommended logical text for short (Pattern: Why is service (not) needed?; ; Resource: Why task is needed) - no reason provided reason does not contain the recommended logical text for definition (Pattern: Describes why the request is being made in coded or textual form, or Indicates another resource whose existence justifies this request.; ; Resource: A description, code, or reference indicating why this task needs to be performed.) - no reason provided reason does not contain the recommended logical text for comments (Pattern: Textual reasons can be captured using reasonCode.text. If doNoPerform is true, this will be the reason why the request is being made to not act.; ; Resource: This will typically not be present for Tasks with a code of 'please fulfill' as, for those, the reason for action is conveyed on the Request pointed to by Task.focus. Some types of tasks will not need a 'reason'. E.g. a request to discharge a patient can be inferred to be 'because the patient is ready' and this would not need a reason to be stated on the Task.) - no reason provided

~~Task~~ Transport

~~Task.reasonReference~~ Transport.reason : ~~Reference~~ CodeableReference [0..1]

Maximum Cardinality differs (Pattern: *; ; Resource: 1) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided reason does not contain the recommended logical text for short (Pattern: Why is service (not) needed?; ; Resource: Why transport is needed) - no reason provided reason does not contain the recommended logical text for definition (Pattern: Describes why the request is being made in coded or textual form, or Indicates another resource whose existence justifies this request.; ; Resource: A resource reference indicating why this transport needs to be performed.) - no reason provided reason does not contain the recommended logical text for comments (Pattern: Textual reasons can be captured using reasonCode.text. If doNoPerform is true, this will be the reason why the request is being made to not act.; ; Resource: Transports might be justified based on an Observation, a Condition, a past or planned procedure, etc. This should only be included if there is no focus or if it differs from the reason indicated on the focus. Use the CodeableConcept text element in `Transport.reasonCode` if the data is free (uncoded) text.) - no reason provided

Cardinality Problem.

Request.insurance

Request.insurance : Reference(Coverage|ClaimResponse) [0..*]

Resource

Matches

Issues

Tasks

Status

Notes

DeviceRequest

DeviceRequest.insurance : Reference [0..*]

insurance does not contain the recommended logical text for definition (Pattern: Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be relevant in delivering the requested service.; ; Resource: Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be required for delivering the requested service.) - no reason provided

EnrollmentRequest

EnrollmentRequest.coverage : Reference [0..1]

Maximum Cardinality differs (Pattern: *; ; Resource: 1) - no reason provided Resource does not support types that are part of the pattern (Pattern: Reference(ClaimResponse)) - no reason provided insurance does not contain the recommended logical text for short (Pattern: Associated insurance coverage; ; Resource: Insurance information) - no reason provided insurance does not contain the recommended logical text for definition (Pattern: Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be relevant in delivering the requested service.; ; Resource: Reference to the program or plan identification, underwriter or payor.) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

MedicationRequest

MedicationRequest.insurance : Reference [0..*]

ServiceRequest

ServiceRequest.insurance : Reference [0..*]

insurance does not contain the recommended logical text for definition (Pattern: Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be relevant in delivering the requested service.; ; Resource: Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be needed for delivering the requested service.) - no reason provided

Task

Task.insurance : Reference [0..*]

Transport

Transport.insurance : Reference [0..*]

Request.supportingInfo

Request.supportingInfo : Reference(Any) [0..*]

Resource

Matches

Issues

Tasks

Status

Notes

Appointment

Appointment.supportingInformation : Reference [0..*]

Resource does not support types that are part of the pattern (Pattern: Reference(Any)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(Resource)) - no reason provided supportingInfo does not contain the recommended logical text for short (Pattern: Extra information to use in performing request; ; Resource: Additional information to support the appointment) - no reason provided supportingInfo does not contain the recommended logical text for definition (Pattern: Information that may be needed by/relevant to the performer in their execution of this appointment.; ; Resource: Additional information to support the appointment provided when making the appointment.) - no reason provided supportingInfo does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: ) - no reason provided

Names are different.
Type Mismatch.

CarePlan

CarePlan.supportingInfo : Reference [0..*]

Resource does not support types that are part of the pattern (Pattern: Reference(Any)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(Resource)) - no reason provided supportingInfo does not contain the recommended logical text for short (Pattern: Extra information to use in performing request; ; Resource: Information considered as part of plan) - no reason provided supportingInfo does not contain the recommended logical text for definition (Pattern: Information that may be needed by/relevant to the performer in their execution of this care plan.; ; Resource: Identifies portions of the patient's record that specifically influenced the formation of the plan. These might include comorbidities, recent procedures, limitations, recent assessments, etc.) - no reason provided supportingInfo does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: Use "concern" to identify specific conditions addressed by the care plan. supportingInfo can be used to convey one or more Advance Directives or Medical Treatment Consent Directives by referencing Consent or any other request resource with intent = directive.) - no reason provided

Type Mismatch.

Claim

Claim.supportingInfo : BackboneElement [0..*]

~~The type 'BackboneElement' is~~

Resource does

~~legal according to~~

support types that are part of

~~(BackboneElement vs~~

(Pattern:

- no reason provided Resource supports types that are not part of the pattern (; Resource: BackboneElement) - no reason provided supportingInfo does not contain the recommended logical text for short (Pattern: Extra information to use in performing request; ; Resource: Supporting information) - no reason provided supportingInfo does not contain the recommended logical text for definition (Pattern: Information that may be needed by/relevant to the performer in their execution of this claim.; ; Resource: Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues.) - no reason provided supportingInfo does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: Often there are multiple jurisdiction specific valuesets which are required.) - no reason provided

Type Mismatch.

CommunicationRequest

CommunicationRequest.about : Reference [0..*]

Resource does not support types that are part of the pattern (Pattern: Reference(Any)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(Resource)) - no reason provided supportingInfo does not contain the recommended logical text for short (Pattern: Extra information to use in performing request; ; Resource: Resources that pertain to this communication request) - no reason provided supportingInfo does not contain the recommended logical text for definition (Pattern: Information that may be needed by/relevant to the performer in their execution of this communication request.; ; Resource: Other resources that pertain to this communication request and to which this communication request should be associated.) - no reason provided supportingInfo does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: Don't use CommunicationRequest.about element when a more specific element exists, such as basedOn, reasonReference, or replaces.) - no reason provided

Names are different.
Type Mismatch.

DeviceRequest

DeviceRequest.supportingInfo : Reference [0..*]

Resource does not support types that are part of the pattern (Pattern: Reference(Any)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(Resource)) - no reason provided supportingInfo does not contain the recommended logical text for short (Pattern: Extra information to use in performing request; ; Resource: Additional clinical information) - no reason provided supportingInfo does not contain the recommended logical text for definition (Pattern: Information that may be needed by/relevant to the performer in their execution of this device request.; ; Resource: Additional clinical information about the patient that may influence the request fulfilment. For example, this may include where on the subject's body the device will be used (i.e. the target site).) - no reason provided supportingInfo does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: ) - no reason provided

Type Mismatch.

ImmunizationRecommendation

ImmunizationRecommendation.recommendation.supportingPatientInformation : Reference [0..*]

Resource does not support types that are part of the pattern (Pattern: Reference(Any)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(Resource)) - no reason provided supportingInfo does not contain the recommended logical text for short (Pattern: Extra information to use in performing request; ; Resource: Patient observations supporting recommendation) - no reason provided supportingInfo does not contain the recommended logical text for definition (Pattern: Information that may be needed by/relevant to the performer in their execution of this immunization recommendation.; ; Resource: Patient Information that supports the status and recommendation. This includes patient observations, adverse reactions and allergy/intolerance information.) - no reason provided supportingInfo does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: ) - no reason provided

Names are different.
Type Mismatch.

MedicationRequest

MedicationRequest.supportingInformation : Reference [0..*]

Resource does not support types that are part of the pattern (Pattern: Reference(Any)) - no reason provided Resource supports types that are not part of the pattern (; Resource: Reference(Resource)) - no reason provided supportingInfo does not contain the recommended logical text for short (Pattern: Extra information to use in performing request; ; Resource: Information to support fulfilling of the medication) - no reason provided supportingInfo does not contain the recommended logical text for definition (Pattern: Information that may be needed by/relevant to the performer in their execution of this medication request.; ; Resource: Information to support fulfilling (i.e. dispensing or administering) of the medication, for example, patient height and weight, a MedicationStatement for the patient).) - no reason provided supportingInfo does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: This attribute can be used to reference a MedicationStatement about the patients' medication use.) - no reason provided

Names are different.
Type Mismatch.

NutritionOrder

NutritionOrder.oralDiet.instruction : string [0..1]

~~The type 'string' is~~

Maximum Cardinality differs (Pattern: *; ; Resource: 1) - no reason provided Resource does

~~legal according to~~

support types that are part of

~~(string vs~~

(Pattern:

- no reason provided Resource supports types that are not part of the pattern (; Resource: string) - no reason provided IsSummary differs (Pattern: false; ; Resource: true) - no reason provided supportingInfo does not contain the recommended logical text for short (Pattern: Extra information to use in performing request; ; Resource: Instructions or additional information about the oral diet) - no reason provided supportingInfo does not contain the recommended logical text for definition (Pattern: Information that may be needed by/relevant to the performer in their execution of this nutrition order.; ; Resource: Free text or additional instructions or information pertaining to the oral diet.) - no reason provided supportingInfo does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: Free text dosage instructions can be used for cases where the instructions are too complex to code.) - no reason provided

NutritionOrder.supplement.instruction : string [0..1]

~~The type 'string' is~~

Maximum Cardinality differs (Pattern: *; ; Resource: 1) - no reason provided Resource does

~~legal according to~~

support types that are part of

~~(string vs~~

(Pattern:

- no reason provided Resource supports types that are not part of the pattern (; Resource: string) - no reason provided IsSummary differs (Pattern: false; ; Resource: true) - no reason provided supportingInfo does not contain the recommended logical text for short (Pattern: Extra information to use in performing request; ; Resource: Instructions or additional information about the oral supplement) - no reason provided supportingInfo does not contain the recommended logical text for definition (Pattern: Information that may be needed by/relevant to the performer in their execution of this nutrition order.; ; Resource: Free text or additional instructions or information pertaining to the oral supplement.) - no reason provided supportingInfo does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: Free text dosage instructions can be used for cases where the instructions are too complex to code.) - no reason provided

NutritionOrder.enteralFormula.administrationInstruction : ~~string~~ markdown [0..1]

~~The type 'string' is~~

Maximum Cardinality differs (Pattern: *; ; Resource: 1) - no reason provided Resource does

~~legal according to~~

support types that are part of

~~(string vs~~

(Pattern:

- no reason provided Resource supports types that are not part of the pattern (; Resource: markdown) - no reason provided IsSummary differs (Pattern: false; ; Resource: true) - no reason provided supportingInfo does not contain the recommended logical text for short (Pattern: Extra information to use in performing request; ; Resource: Formula feeding instructions expressed as text) - no reason provided supportingInfo does not contain the recommended logical text for definition (Pattern: Information that may be needed by/relevant to the performer in their execution of this nutrition order.; ; Resource: Free text formula administration, feeding instructions or additional instructions or information.) - no reason provided supportingInfo does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: Free text dosage instructions can be used for cases where the instructions are too complex to code.) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

~~RequestGroup~~ RequestOrchestration

~~RequestGroup.action.documentation~~ RequestOrchestration.action.documentation : RelatedArtifact [0..*]

~~The type 'RelatedArtifact' is~~

Resource does

~~legal according to~~

support types that are part of

~~(RelatedArtifact vs~~

(Pattern:

- no reason provided Resource supports types that are not part of the pattern (; Resource: RelatedArtifact) - no reason provided supportingInfo does not contain the recommended logical text for short (Pattern: Extra information to use in performing request; ; Resource: Supporting documentation for the intended performer of the action) - no reason provided supportingInfo does not contain the recommended logical text for definition (Pattern: Information that may be needed by/relevant to the performer in their execution of this request orchestration.; ; Resource: Didactic or other informational resources associated with the action that can be provided to the CDS recipient. Information resources can include inline text commentary and links to web resources.) - no reason provided supportingInfo does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: ) - no reason provided

Names are different.
Type Mismatch.

ServiceRequest

ServiceRequest.supportingInfo : ~~Reference~~ CodeableReference [0..*]

Resource does not support types that are part of the pattern (Pattern: Reference(Any)) - no reason provided Resource supports types that are not part of the pattern (; Resource: CodeableReference(Resource)) - no reason provided supportingInfo does not contain the recommended logical text for short (Pattern: Extra information to use in performing request; ; Resource: Additional clinical information) - no reason provided supportingInfo does not contain the recommended logical text for definition (Pattern: Information that may be needed by/relevant to the performer in their execution of this service request.; ; Resource: 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.) - no reason provided supportingInfo does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: To represent information about how the services are to be delivered use the `instructions` element.) - no reason provided

Type Mismatch.

Request.note

Request.note : Annotation [0..*]

Resource

Matches

Issues

Tasks

Status

Notes

Appointment

~~Appointment.comment~~ Appointment.note : ~~string [0..1]~~ Annotation [0..*]

~~The type 'string'~~

note does not contain the recommended logical text for short (Pattern: Comments made about appointment; ; Resource: Additional comments) - no reason provided note does not contain the recommended logical text for definition (Pattern: Comments made about the appointment by the requester, performer, subject or other participants.; ; Resource: Additional notes/comments about the appointment.) - no reason provided note does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: Additional text to aid in facilitating the appointment. For instance, a note might be, "patient should proceed immediately to infusion room upon arrival" Where this

a planned appointment and the start/end dates are

~~legal according~~

set then this field can be used

provide additional guidance on

~~pattern (string vs Annotation)~~

details of the appointment request, including any restrictions on when to book it. Typically only the concept.text will be used, however occasionally a reference to some generic documentation (or specific) and also supports coded instructions if/when they are required.) - no reason provided

~~Names are different.~~

AppointmentResponse

AppointmentResponse.comment : ~~string~~ markdown [0..1]

~~The type 'string' is~~

Maximum Cardinality differs (Pattern: *; ; Resource: 1) - no reason provided Resource does

~~legal according to~~

support types that are part of

~~(string vs~~

(Pattern:

- no reason provided Resource supports types that are not part of the pattern (; Resource: markdown) - no reason provided note does not contain the recommended logical text for short (Pattern: Comments made about appointment response; ; Resource: Additional comments) - no reason provided note does not contain the recommended logical text for definition (Pattern: Comments made about the appointment response by the requester, performer, subject or other participants.; ; Resource: Additional comments about the appointment.) - no reason provided note does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: This comment is particularly important when the responder is declining, tentatively accepting or requesting another time to indicate the reasons why.) - no reason provided

Names are different.
Type Mismatch.
Cardinality Problem.

CarePlan

CarePlan.note : Annotation [0..*]

note does not contain the recommended logical text for short (Pattern: Comments made about care plan; ; Resource: Comments about the plan) - no reason provided note does not contain the recommended logical text for definition (Pattern: Comments made about the care plan by the requester, performer, subject or other participants.; ; Resource: General notes about the care plan not covered elsewhere.) - no reason provided note does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: ) - no reason provided

CommunicationRequest

CommunicationRequest.payload.content[x] : ~~string,~~ Attachment, ~~Reference~~ Reference, CodeableConcept [1..1]

~~The type 'string' is~~

Minimum Cardinality differs (Pattern: 0; ; Resource: 1) - no reason provided Maximum Cardinality differs (Pattern: *; ; Resource: 1) - no reason provided Resource does

~~legal according to~~

support types that are part of

~~(string, Attachment, Reference vs~~

(Pattern:

~~, The type 'Attachment' is~~

- no reason provided Resource supports types that are

~~legal according to~~

part of

~~(string,~~

(; Resource: Reference(Resource),

~~Reference vs Annotation) ,~~

CodeableConcept) - no reason provided note does not contain the recommended logical text for short (Pattern: Comments made about communication request; ; Resource: Message part content) - no reason provided note does not contain the recommended logical text for definition (Pattern: Comments made about the communication request by the requester, performer, subject or other participants.; ; Resource:

~~type 'Reference'~~

communicated content (or for multi-part communications, one portion of the communication).) - no reason provided note does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: The content can be codified or textual. As an example of codified content, when working with machine generated communications, the payload may be drawn from a finite, terminology defined set of communications, especially for short, status update kinds of communications where more of a natural language approach isn't appropriate. If the content isn't codified, contentCodeableConcept.text can be used. When using contentCodeableConcept, the CodeableConcept is what is being communicated and

~~legal according to~~

a categorization of

~~pattern (string, Attachment, Reference vs Annotation)~~

content.) - no reason provided

CommunicationRequest.note : Annotation [0..*]

note does not contain the recommended logical text for definition (Pattern: Comments made about the communication request by the requester, performer, subject or other participants.; ; Resource: Comments made about the request by the requester, sender, recipient, subject or other participants.) - no reason provided note does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: ) - no reason provided

Names are different.
Type Mismatch.

DeviceRequest

DeviceRequest.note : Annotation [0..*]

note does not contain the recommended logical text for short (Pattern: Comments made about device request; ; Resource: Notes or comments) - no reason provided note does not contain the recommended logical text for definition (Pattern: Comments made about the device request by the requester, performer, subject or other participants.; ; Resource: Details about this request that were not represented at all or sufficiently in one of the attributes provided in a class. These may include for example a comment, an instruction, or a note associated with the statement.) - no reason provided note does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: ) - no reason provided

MedicationRequest

MedicationRequest.note : Annotation [0..*]

note does not contain the recommended logical text for short (Pattern: Comments made about medication request; ; Resource: Information about the prescription) - no reason provided note does not contain the recommended logical text for definition (Pattern: Comments made about the medication request by the requester, performer, subject or other participants.; ; Resource: Extra information about the prescription that could not be conveyed by the other attributes.) - no reason provided note does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: ) - no reason provided

NutritionOrder

NutritionOrder.note : Annotation [0..*]

note does not contain the recommended logical text for short (Pattern: Comments made about nutrition order; ; Resource: Comments) - no reason provided note does not contain the recommended logical text for definition (Pattern: Comments made about the nutrition order by the requester, performer, subject or other participants.; ; Resource: Comments made about the {{title}} by the requester, performer, subject or other participants.) - no reason provided note does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: This element SHALL NOT be used to supply free text instructions for the diet which are represented in the `.oralDiet.instruction`, `supplement.instruction`, or `enteralFormula.administrationInstruction` elements.) - no reason provided

~~RequestGroup~~ RequestOrchestration

~~RequestGroup.note~~ RequestOrchestration.note : Annotation [0..*]

note does not contain the recommended logical text for short (Pattern: Comments made about request orchestration; ; Resource: Additional notes about the response) - no reason provided note does not contain the recommended logical text for definition (Pattern: Comments made about the request orchestration by the requester, performer, subject or other participants.; ; Resource: Provides a mechanism to communicate additional information about the response.) - no reason provided note does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: ) - no reason provided

ServiceRequest

ServiceRequest.note : Annotation [0..*]

note does not contain the recommended logical text for short (Pattern: Comments made about service request; ; Resource: Comments) - no reason provided note does not contain the recommended logical text for definition (Pattern: Comments made about the service request by the requester, performer, subject or other participants.; ; Resource: Any other notes and comments made about the service request. For example, internal billing notes.) - no reason provided note does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: ) - no reason provided

Task

Task.note : Annotation [0..*]

note does not contain the recommended logical text for short (Pattern: Comments made about task; ; Resource: Comments made about the task) - no reason provided note does not contain the recommended logical text for definition (Pattern: Comments made about the task by the requester, performer, subject or other participants.; ; Resource: Free-text information captured about the task as it progresses.) - no reason provided note does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: ) - no reason provided

Transport

Transport.note : Annotation [0..*]

note does not contain the recommended logical text for short (Pattern: Comments made about transport; ; Resource: Comments made about the transport) - no reason provided note does not contain the recommended logical text for definition (Pattern: Comments made about the transport by the requester, performer, subject or other participants.; ; Resource: Free-text information captured about the transport as it progresses.) - no reason provided note does not contain the recommended logical text for comments (Pattern: See guidance on [notes vs. supportingInfo](request.html#notes).; ; Resource: ) - no reason provided

Request.relevantHistory

Request.relevantHistory : Reference(Provenance) [0..*]

Resource

Matches

Issues

Tasks

Status

Notes

DeviceRequest

DeviceRequest.relevantHistory : Reference [0..*]

relevantHistory does not contain the recommended logical text for short (Pattern: Key events in history of device request; ; Resource: Request provenance) - no reason provided relevantHistory does not contain the recommended logical text for definition (Pattern: Links to Provenance records for past versions of this resource or fulfilling request or event resources that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the resource.; ; Resource: Key events in the history of the request.) - no reason provided relevantHistory does not contain the recommended logical text for comments (Pattern: This element does not point to the Provenance associated with the *current* version of the resource - as it would be created after this version existed. The Provenance for the current version can be retrieved with a _revinclude. Referenced provenances SHOULD adhere to the [provenance-relevant-history profile](provenance-relevant-history.html). See additional guidance [here](request.html#history).; ; Resource: This might not include provenances for all versions of the request - only those deemed "relevant" or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a "relevant" change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.) - no reason provided

MedicationRequest

MedicationRequest.eventHistory : Reference [0..*]

relevantHistory does not contain the recommended logical text for short (Pattern: Key events in history of medication request; ; Resource: A list of events of interest in the lifecycle) - no reason provided relevantHistory does not contain the recommended logical text for comments (Pattern: This element does not point to the Provenance associated with the *current* version of the resource - as it would be created after this version existed. The Provenance for the current version can be retrieved with a _revinclude. Referenced provenances SHOULD adhere to the [provenance-relevant-history profile](provenance-relevant-history.html). See additional guidance [here](request.html#history).; ; Resource: This might not include provenances for all versions of the request – only those deemed "relevant" or important. This SHALL NOT include the provenance associated with this current version of the resource. (If that provenance is deemed to be a "relevant" change, it will need to be added as part of a later update. Until then, it can be queried directly as the provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.).) - no reason provided

Names are different.

ServiceRequest

ServiceRequest.relevantHistory : Reference [0..*]

relevantHistory does not contain the recommended logical text for short (Pattern: Key events in history of service request; ; Resource: Request provenance) - no reason provided relevantHistory does not contain the recommended logical text for definition (Pattern: Links to Provenance records for past versions of this resource or fulfilling request or event resources that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the resource.; ; Resource: Key events in the history of the request.) - no reason provided relevantHistory does not contain the recommended logical text for comments (Pattern: This element does not point to the Provenance associated with the *current* version of the resource - as it would be created after this version existed. The Provenance for the current version can be retrieved with a _revinclude. Referenced provenances SHOULD adhere to the [provenance-relevant-history profile](provenance-relevant-history.html). See additional guidance [here](request.html#history).; ; Resource: This might not include provenances for all versions of the request – only those deemed “relevant” or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.) - no reason provided

Task

Task.relevantHistory : Reference [0..*]

relevantHistory does not contain the recommended logical text for short (Pattern: Key events in history of task; ; Resource: Key events in history of the Task) - no reason provided relevantHistory does not contain the recommended logical text for definition (Pattern: Links to Provenance records for past versions of this resource or fulfilling request or event resources that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the resource.; ; Resource: Links to Provenance records for past versions of this Task that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the task.) - no reason provided relevantHistory does not contain the recommended logical text for comments (Pattern: This element does not point to the Provenance associated with the *current* version of the resource - as it would be created after this version existed. The Provenance for the current version can be retrieved with a _revinclude. Referenced provenances SHOULD adhere to the [provenance-relevant-history profile](provenance-relevant-history.html). See additional guidance [here](request.html#history).; ; Resource: This element does not point to the Provenance associated with the *current* version of the resource - as it would be created after this version existed. The Provenance for the current version can be retrieved with a _revinclude.) - no reason provided

Transport

Transport.relevantHistory : Reference [0..*]

relevantHistory does not contain the recommended logical text for short (Pattern: Key events in history of transport; ; Resource: Key events in history of the Transport) - no reason provided relevantHistory does not contain the recommended logical text for definition (Pattern: Links to Provenance records for past versions of this resource or fulfilling request or event resources that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the resource.; ; Resource: Links to Provenance records for past versions of this Transport that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the transport.) - no reason provided relevantHistory does not contain the recommended logical text for comments (Pattern: This element does not point to the Provenance associated with the *current* version of the resource - as it would be created after this version existed. The Provenance for the current version can be retrieved with a _revinclude. Referenced provenances SHOULD adhere to the [provenance-relevant-history profile](provenance-relevant-history.html). See additional guidance [here](request.html#history).; ; Resource: This element does not point to the Provenance associated with the *current* version of the resource - as it would be created after this version existed. The Provenance for the current version can be retrieved with a _revinclude.) - no reason provided