Profile Comparison between http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request vs http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request

Left:CDex Task Data Request Profile (http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request)
Right:CDex Task Data Request Profile (http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request)

Messages

ErrorStructureDefinition.versionValues for version differ: '1.0.0' vs '2.0.0'
InformationStructureDefinition.dateValues for date differ: '2022-03-28T13:46:42+00:00' vs '2023-03-22T00:17:45+11:00'
ErrorStructureDefinition.baseDefinitionValues for baseDefinition differ: 'http://hl7.org/fhir/us/davinci-hrex/StructureDefinition/hrex-task-data-request' vs 'http://hl7.org/fhir/StructureDefinition/Task'
WarningTaskElements differ in definition: 'This Task profile is used to solicit information from a system when direct query is not possible and human intervention might be required' vs 'This Task profile is used by the CDex Data Consumer (e.g. Payer or other Provider) to solicit information from a Data Source (e.g., Provider) asynchronously where human involvement to find/aggregate/filter/approve requests may be required.'
WarningTask.identifierElements differ in definition for mustSupport: 'false' vs 'true'
WarningTask.businessStatusElements differ in short: 'E.g. 'waiting on internal review'' vs 'For example, 'waiting on internal review''
WarningTask.codeElements differ in short: 'Task Type' vs 'data-request-code | data-request-query | data-request-questionnaire'
WarningTask.codeElements differ in definition: 'A name or code (or both) briefly describing what the task involves.' vs 'The code element is used to indicate that Task is a request for data and whether the data request is a code, FHIR query syntax or a questionnaire. The code element is a required element and must be populated with one of the following values: 'data-request-code', 'data-request-query',or 'data-request-questionnaire'.'
WarningTask.code.codingElements differ in definition for mustSupport: 'false' vs 'true'
InformationTask.code.codingElement minimum cardinalities differ: '0' vs '1'
WarningTask.code.coding.systemElements differ in definition for mustSupport: 'false' vs 'true'
WarningTask.code.coding.codeElements differ in definition for mustSupport: 'false' vs 'true'
InformationTask.code.coding.codeElement minimum cardinalities differ: '0' vs '1'
WarningTask.forElements differ in short: 'Member being queried' vs 'Member (i.e., patient) being queried'
WarningTask.for.identifierElements differ in short: 'Logical reference, when literal reference is not known' vs 'Patient Member ID'
WarningTask.for.identifierElements differ in definition: 'An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.' vs 'business identifier representing the Patient'
WarningTask.for.identifierElements differ in definition for mustSupport: 'false' vs 'true'
WarningTask.requester.identifierElements differ in short: 'Logical reference, when literal reference is not known' vs 'Data Consumer ID'
WarningTask.requester.identifierElements differ in definition: 'An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.' vs 'business identifier representing the Data Consumer'
WarningTask.requester.identifierElements differ in definition for mustSupport: 'false' vs 'true'
WarningTask.owner.identifierElements differ in short: 'Logical reference, when literal reference is not known' vs 'Provider ID'
WarningTask.owner.identifierElements differ in definition: 'An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.' vs 'business identifier representing the Provider'
WarningTask.owner.identifierElements differ in definition for mustSupport: 'false' vs 'true'
WarningTask.reasonReferenceElements differ in comments: 'Likely targets would be HRex Coverage, PCDE Claim (for prior authorization) or a bare Claim resource for referencing an actual Claim.' vs 'Example targets would be HRex Coverage, PCDE Claim (for prior authorization) or a bare Claim resource for referencing an actual Claim.'
WarningTask.reasonReference.identifierElements differ in short: 'Logical reference, when literal reference is not known' vs 'Coverage or Claim ID'
WarningTask.reasonReference.identifierElements differ in definition: 'An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.' vs 'business identifier representing the coverage, claim, or prior-authorization ID'
WarningTask.reasonReference.identifierElements differ in comments: 'When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).' vs 'Most payer systems will not expose their claim and prior authorization records as a FHIR resource. They will provide a unique business identifier for the claim or prior authorization using `Task.reasonReference.identifier`. This could be a payer-assigned or provider-assigned identifier which **SHOULD** be communicated in `Task.reasonReference.identifier.type` using the 'FILL' for the payer and 'PLAC' for the provider.'
WarningTask.reasonReference.identifierElements differ in definition for mustSupport: 'false' vs 'true'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/us/davinci-hrex/StructureDefinition/hrex-task-data-requesthttp://hl7.org/fhir/StructureDefinition/Task
    • Values Differ
    .copyrightUsed by permission of HL7 International all rights reserved Creative Commons License
      .date2022-03-28T13:46:42+00:002023-03-22T00:17:45+11:00
      • Values Differ
      .descriptionThis Task profile is based upon the [Da Vinci Hrex Task Data Request](http://hl7.org/fhir/us/davinci-hrex/StructureDefinition/hrex-task-data-request). It adds the following additional constraints for CDEX: - A 'meta.tag' element representing work-queue hints. - A `Task.input` element slice representing the types of documents to be returned using the extensible LOINC® Document types value set. - A `Task.input` element slice representing a flag to indicate whether the requested data requires a signature. - A `Task.input` element slice representing the purpose of use for the requested data using an extensible *CDex Purpose of Use Value Set*.This Task profile is used to solicit information from a system. The Data Consumer uses it when direct query transactions are not an option, and the transaction may require human intervention. It represents both the data request and the returned "data request". Data requests are supplied as codes, free-text, or FHIR Restful queries. It can also support requests for more detailed missing data using Questionnaire, CQL, and QuestionnaireResponse as supported by Da Vinci DTR. It constrains the following elements to be *mandatory* (min=1): - A Task.status with a required binding to HRex [Task Status ValueSet](http://hl7.org/fhir/us/davinci-hrex/STU1/ValueSet-hrex-task-status.html) (this element is a mandatory Task element). For guidance when the provider is not able to complete the Task, refer to the [When The Task Cannot Be Completed section](http://hl7.org/fhir/us/davinci-cdex/STU2/task-based-approach.html#when-the-task-cannot-be-completed). - A Task.intent fixed to "order" (this element is a mandatory Task element) - A Task.code of either "data-request-code", "data-request-code", or "data-request-questionnaire" communicating that the Data Consumer is requesting data using a code(or free text), a FHIR RESTful query, or a data request questionnaire. - If the code is "data-request-query", the provider system returns data(s) identified by the FHIR RESTful query in the "query" input parameter. - If the code is "data-request-code", the provider system returns data(s) identified by the LOINC code in the "code" input parameter. - If the code is "data-request-questionnaire", the provider system uses [Documentation Templates and Rules (DTR)](http://hl7.org/fhir/us/davinci-dtr/2022May/) to complete the Questionnaire referenced in the "questionnaire" input parameter. - A Task.for element representing the member (i.e.,patient) for whom the data is being requested - A Task.requester element communicating who is requesting the data - A Task.owner element representing the Provider who is being asked to provide the data It constrains following elements to be [*must support*](task-based-conformance.html#cdex-must-support-definition) (min=0): - A Task.identifier element representing the unique data request identifier - A Task.basedOn element to communicate the order (ServiceRequest, CommunicationRequest, etc.) that authorizes the data request - A Task.statusReason.text to communicate the reason for the status (for example, if the Task is rejected or failed) - A Task.businessStatus.text element representing the progress in retrieving the data (for example, "waiting on internal review"). - A Task.for.reference.identifier element representing a patient business identifier like a Member ID - A Task.requester.reference.identifier element representing the Data Consumer business identifier - A Task.owner.reference.identifier element representing the Provider business identifier - A Task.reasonCode.text to communicate why the data is being requested - A Task.reasonReference.reference.identifier for the claim, pre-auth or coverage business identifier - A "query" Task.input element to communicate to the provider what information is needed using a FHIR RESTful query.* - A "code" Task.input element to communicate to the provider what information is needed using a LOINC code.* - For the "code" Task.input element, an extensible LOINC® Document types value set to communicate the specific information being requested - A Task.input element representing a flag to indicate whether the requested data requires a signature - A "data" Task.output element referring to FHIR resource(s) representing the result(s) of the data request code. It defines the following elements to be *optional*: - A meta.tag element representing work-queue hints. - A "questionnaire" Task.input element to communicate to the provider a URL of a data request [FHIR Questionnaire](http://hl7.org/fhir/questionnaire.html) that conforms to the [DTR SDC Questionnaire Profile](http://hl7.org/fhir/us/davinci-dtr/StructureDefinition/dtr-sdc-questionnaire) or the [DTR SDC Questionnaire for Adaptive Form Profile](http://hl7.org/fhir/us/davinci-dtr/StructureDefinition/dtr-sdc-questionnaire-adapt).* - A questionnaireDisplay extension to communicate the display name of the Questionnaire - A Task.input element representing the purpose of use for the requested data using an extensible [CDex Purpose of Use Value Set](http://hl7.org/fhir/us/davinci-cdex/ValueSet/cdex-POU) - A "response" Task.output element which is a local reference to the [FHIR QuestionnaireResponse](http://hl7.org/fhir/questionnaireresponse.html) resulting from the data request Questionnaire. The QuestionnaireResponse conforms to the [SDC Questionnaire Response Profile](http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse) or the [SDC Adaptive Questionnaire Response Profile](http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse-adapt). It prohibits the following elements (max=0): - Task.focus \* Either a "query", "code", or "questionnaire" Task.input element is required
      • Values Differ
      .experimental
        .fhirVersion4.0.1
          .jurisdiction
            ..jurisdiction[0]urn:iso:std:iso:3166#US
              .kindresource
                .nameCDexTaskDataRequest
                  .publisherHL7 International - Patient Care Work Group
                    .purpose
                      .statusactive
                        .titleCDex Task Data Request Profile
                          .typeTask
                            .urlhttp://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
                              .version1.0.02.0.0
                              • Values Differ

                              Structure

                              NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                              .. Task C0..*HRexTaskDataRequestA task to be performed
                              C0..*TaskA task to be performed
                              cdex-7: If code = "data-request-code", must have one "code" input.
                              cdex-12: If code = "data-request-query", must have one "query" input.
                              cdex-8: If code = "data-request-questionnaire", must have one "questionnaire" input.
                              cdex-9: Must have exactly one input that is data-query or data-code or questionnaire
                              tdr-2: Task statusReason SHALL be populated if status is 'rejected' or 'failed'
                              tdr-3: Task output SHALL be populated if status is 'completed'
                              cdex-11: If code = "data-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse.
                              • Elements differ in definition: 'This Task profile is used to solicit information from a system when direct query is not possible and human intervention might be required' vs 'This Task profile is used by the CDex Data Consumer (e.g. Payer or other Provider) to solicit information from a Data Source (e.g., Provider) asynchronously where human involvement to find/aggregate/filter/approve requests may be required.'
                              ... id Σ0..1stringLogical id of this artifactΣ0..1idLogical id of this artifact
                                ... meta Σ0..1MetaMetadata about the resourceΣ0..1MetaMetadata about the resource
                                  .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                    .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                    Slice: Unordered, Open by value:url
                                    0..*ExtensionAdditional content defined by implementations
                                    Slice: Unordered, Open by value:url
                                      .... versionId Σ0..1idVersion specific identifierΣ0..1idVersion specific identifier
                                        .... lastUpdated Σ0..1instantWhen the resource version last changedΣ0..1instantWhen the resource version last changed
                                          .... source Σ0..1uriIdentifies where the resource comes fromΣ0..1uriIdentifies where the resource comes from
                                            .... profile Σ0..*canonical(StructureDefinition)Profiles this resource claims to conform to
                                            Σ0..*canonical(StructureDefinition)Profiles this resource claims to conform to
                                              .... security Σ0..*CodingSecurity Labels applied to this resource
                                              Binding: ?? (extensible): Security Labels from the Healthcare Privacy and Security Classification System.


                                              Σ0..*CodingSecurity Labels applied to this resource
                                              Binding: ?? (extensible): Security Labels from the Healthcare Privacy and Security Classification System.


                                                .... Slices for tag Σ0..*CodingTags applied to this resource
                                                Slice: Unordered, Open by pattern:$this
                                                Binding: ?? (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".


                                                Σ0..*CodingTags applied to this resource
                                                Slice: Unordered, Open by pattern:$this
                                                Binding: ?? (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".


                                                  ..... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                    ..... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                                    Slice: Unordered, Open by value:url
                                                    0..*ExtensionAdditional content defined by implementations
                                                    Slice: Unordered, Open by value:url
                                                      ..... system Σ0..1uriIdentity of the terminology systemΣ0..1uriIdentity of the terminology system
                                                        ..... version Σ0..1stringVersion of the system - if relevantΣ0..1stringVersion of the system - if relevant
                                                          ..... code Σ1..1codeSymbol in syntax defined by the systemΣ1..1codeSymbol in syntax defined by the system
                                                            ..... display Σ0..1stringRepresentation defined by the systemΣ0..1stringRepresentation defined by the system
                                                              ..... userSelected Σ0..1booleanIf this coding was chosen directly by the userΣ0..1booleanIf this coding was chosen directly by the user
                                                                ... implicitRules ?!Σ0..1uriA set of rules under which this content was created?!Σ0..1uriA set of rules under which this content was created
                                                                  ... language 0..1codeLanguage of the resource content
                                                                  Binding: ?? (preferred): A human language.

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

                                                                  Additional BindingsPurpose
                                                                  ??Max Binding
                                                                    ... text 0..1NarrativeText summary of the resource, for human interpretation0..1NarrativeText summary of the resource, for human interpretation
                                                                      ... contained 0..*ResourceContained, inline Resources
                                                                      0..*ResourceContained, inline Resources
                                                                        ... extension 0..*ExtensionAdditional content defined by implementations
                                                                        0..*ExtensionAdditional content defined by implementations
                                                                          ... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
                                                                          ?!0..*ExtensionExtensions that cannot be ignored
                                                                            ... identifier 0..*IdentifierTask Instance Identifier
                                                                            S0..*IdentifierTask Instance Identifier
                                                                            • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                            ... instantiatesCanonical Σ0..1canonical(ActivityDefinition)Formal definition of taskΣ0..1canonical(ActivityDefinition)Formal definition of task
                                                                              ... instantiatesUri Σ0..1uriFormal definition of taskΣ0..1uriFormal definition of task
                                                                                ... basedOn SΣ0..*Reference(Resource)Authorization for data request
                                                                                SΣ0..*Reference(Resource)Authorization for data request
                                                                                  ... groupIdentifier Σ0..1IdentifierRequisition or grouper idΣ0..1IdentifierRequisition or grouper id
                                                                                    ... partOf Σ0..*Reference(Task)Composite task
                                                                                    Σ0..*Reference(Task)Composite task
                                                                                      ... status ?!SΣ1..1codedraft | requested | received | accepted | +
                                                                                      Binding: ?? (required)
                                                                                      ?!SΣC1..1codedraft | requested | received | accepted | +
                                                                                      Binding: ?? (required)
                                                                                        ... statusReason SΣ0..1CodeableConceptReason for current status
                                                                                        Binding: ?? (example): Codes to identify the reason for current status. These will typically be specific to a particular workflow.

                                                                                        SΣC0..1CodeableConceptReason for current status
                                                                                        Binding: ?? (example): Codes to identify the reason for current status. These will typically be specific to a particular workflow.

                                                                                          .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                            .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                                                                            Slice: Unordered, Open by value:url
                                                                                            0..*ExtensionAdditional content defined by implementations
                                                                                            Slice: Unordered, Open by value:url
                                                                                              .... coding Σ0..*CodingCode defined by a terminology system
                                                                                              Σ0..*CodingCode defined by a terminology system
                                                                                                .... text SΣ1..1stringPlain text representation of the conceptSΣ1..1stringPlain text representation of the concept
                                                                                                  ... businessStatus SΣ0..1CodeableConceptE.g. 'waiting on internal review'
                                                                                                  Binding: ?? (example): The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc.

                                                                                                  SΣ0..1CodeableConceptFor example, 'waiting on internal review'
                                                                                                  Binding: ?? (example): The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc.

                                                                                                  • Elements differ in short: 'E.g. 'waiting on internal review'' vs 'For example, 'waiting on internal review''
                                                                                                  .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                                    .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                                                                                    Slice: Unordered, Open by value:url
                                                                                                    0..*ExtensionAdditional content defined by implementations
                                                                                                    Slice: Unordered, Open by value:url
                                                                                                      .... coding Σ0..*CodingCode defined by a terminology system
                                                                                                      Σ0..*CodingCode defined by a terminology system
                                                                                                        .... text SΣ1..1stringPlain text representation of the conceptSΣ1..1stringPlain text representation of the concept
                                                                                                          ... intent SΣ1..1codeunknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
                                                                                                          Binding: ?? (required): Distinguishes whether the task is a proposal, plan or full order.


                                                                                                          Fixed Value: order
                                                                                                          SΣ1..1codeunknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
                                                                                                          Binding: ?? (required): Distinguishes whether the task is a proposal, plan or full order.


                                                                                                          Fixed Value: order
                                                                                                            ... priority 0..1coderoutine | urgent | asap | stat
                                                                                                            Binding: ?? (required): The task's priority.

                                                                                                            0..1coderoutine | urgent | asap | stat
                                                                                                            Binding: ?? (required): The task's priority.

                                                                                                              ... code SΣ1..1CodeableConceptTask Type
                                                                                                              Binding: ?? (example): Codes to identify what the task involves. These will typically be specific to a particular workflow.


                                                                                                              Required Pattern: {"coding":[{"system":"http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp","code":"data-request"}]}
                                                                                                              SΣC1..1CodeableConceptdata-request-code | data-request-query | data-request-questionnaire
                                                                                                              Binding: ?? (required)
                                                                                                              • Elements differ in short: 'Task Type' vs 'data-request-code | data-request-query | data-request-questionnaire'
                                                                                                              • Elements differ in definition: 'A name or code (or both) briefly describing what the task involves.' vs 'The code element is used to indicate that Task is a request for data and whether the data request is a code, FHIR query syntax or a questionnaire. The code element is a required element and must be populated with one of the following values: "data-request-code", "data-request-query",or "data-request-questionnaire".'
                                                                                                              .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                                                .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                                                                                                Slice: Unordered, Open by value:url
                                                                                                                0..*ExtensionAdditional content defined by implementations
                                                                                                                Slice: Unordered, Open by value:url
                                                                                                                  .... coding Σ0..*CodingCode defined by a terminology system
                                                                                                                  SΣ1..*CodingCode defined by a terminology system
                                                                                                                  • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                                                  • Element minimum cardinalities differ: '0' vs '1'
                                                                                                                  ..... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                                                    ..... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                                                                                                    Slice: Unordered, Open by value:url
                                                                                                                    0..*ExtensionAdditional content defined by implementations
                                                                                                                    Slice: Unordered, Open by value:url
                                                                                                                      ..... system Σ0..1uriIdentity of the terminology systemSΣ0..1uriIdentity of the terminology system
                                                                                                                      Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
                                                                                                                      • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                                                      ..... version Σ0..1stringVersion of the system - if relevantΣ0..1stringVersion of the system - if relevant
                                                                                                                        ..... code Σ0..1codeSymbol in syntax defined by the systemSΣ1..1codeSymbol in syntax defined by the system
                                                                                                                        • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                                                        • Element minimum cardinalities differ: '0' vs '1'
                                                                                                                        ..... display Σ0..1stringRepresentation defined by the systemΣ0..1stringRepresentation defined by the system
                                                                                                                          ..... userSelected Σ0..1booleanIf this coding was chosen directly by the userΣ0..1booleanIf this coding was chosen directly by the user
                                                                                                                            .... text Σ0..1stringPlain text representation of the conceptΣ0..1stringPlain text representation of the concept
                                                                                                                              ... description Σ0..1stringHuman-readable explanation of taskΣ0..1stringHuman-readable explanation of task
                                                                                                                                ... focus Σ0..0Σ0..0
                                                                                                                                  ... for SΣ1..1Reference(US Core Patient Profile)Member being queriedSΣ1..1Reference(US Core Patient Profile)Member (i.e., patient) being queried
                                                                                                                                  • Elements differ in short: 'Member being queried' vs 'Member (i.e., patient) being queried'
                                                                                                                                  .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                                                                    .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                                                                                                                    Slice: Unordered, Open by value:url
                                                                                                                                    0..*ExtensionAdditional content defined by implementations
                                                                                                                                    Slice: Unordered, Open by value:url
                                                                                                                                      .... reference ΣC0..1stringLiteral reference, Relative, internal or absolute URLΣC0..1stringLiteral reference, Relative, internal or absolute URL
                                                                                                                                        .... type Σ0..1uriType the reference refers to (e.g. "Patient")
                                                                                                                                        Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).

                                                                                                                                        Σ0..1uriType the reference refers to (e.g. "Patient")
                                                                                                                                        Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).

                                                                                                                                          .... identifier Σ0..1IdentifierLogical reference, when literal reference is not knownSΣ0..1IdentifierPatient Member ID
                                                                                                                                          • Elements differ in short: 'Logical reference, when literal reference is not known' vs 'Patient Member ID'
                                                                                                                                          • Elements differ in definition: 'An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.' vs 'business identifier representing the Patient'
                                                                                                                                          • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                                                                          .... display Σ0..1stringText alternative for the resourceΣ0..1stringText alternative for the resource
                                                                                                                                            ... encounter Σ0..1Reference(Encounter)Healthcare event during which this task originatedΣ0..1Reference(Encounter)Healthcare event during which this task originated
                                                                                                                                              ... executionPeriod Σ0..1PeriodStart and end time of executionΣ0..1PeriodStart and end time of execution
                                                                                                                                                ... authoredOn SC1..1dateTimeTask Creation DateSC1..1dateTimeTask Creation Date
                                                                                                                                                  ... lastModified ΣC0..1dateTimeTask Last Modified DateΣC0..1dateTimeTask Last Modified Date
                                                                                                                                                    ... requester SΣ1..1Reference(US Core Organization Profile | US Core Practitioner Profile)Who is asking for dataSΣ1..1Reference(US Core Organization Profile | US Core Practitioner Profile)Who is asking for data
                                                                                                                                                      .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                                                                                        .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                                                                                                                                        Slice: Unordered, Open by value:url
                                                                                                                                                        0..*ExtensionAdditional content defined by implementations
                                                                                                                                                        Slice: Unordered, Open by value:url
                                                                                                                                                          .... reference ΣC0..1stringLiteral reference, Relative, internal or absolute URLΣC0..1stringLiteral reference, Relative, internal or absolute URL
                                                                                                                                                            .... type Σ0..1uriType the reference refers to (e.g. "Patient")
                                                                                                                                                            Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).

                                                                                                                                                            Σ0..1uriType the reference refers to (e.g. "Patient")
                                                                                                                                                            Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).

                                                                                                                                                              .... identifier Σ0..1IdentifierLogical reference, when literal reference is not knownSΣ0..1IdentifierData Consumer ID
                                                                                                                                                              • Elements differ in short: 'Logical reference, when literal reference is not known' vs 'Data Consumer ID'
                                                                                                                                                              • Elements differ in definition: 'An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.' vs 'business identifier representing the Data Consumer'
                                                                                                                                                              • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                                                                                              .... display Σ0..1stringText alternative for the resourceΣ0..1stringText alternative for the resource
                                                                                                                                                                ... performerType 0..*CodeableConceptRequested performer
                                                                                                                                                                Binding: ?? (preferred): The type(s) of task performers allowed.


                                                                                                                                                                0..*CodeableConceptRequested performer
                                                                                                                                                                Binding: ?? (preferred): The type(s) of task performers allowed.


                                                                                                                                                                  ... owner SΣ1..1Reference(US Core Organization Profile | US Core Practitioner Profile)Who is being asked for dataSΣ1..1Reference(US Core Organization Profile | US Core Practitioner Profile)Who is being asked for data
                                                                                                                                                                    .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                                                                                                      .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                                                                                                                                                      Slice: Unordered, Open by value:url
                                                                                                                                                                      0..*ExtensionAdditional content defined by implementations
                                                                                                                                                                      Slice: Unordered, Open by value:url
                                                                                                                                                                        .... reference ΣC0..1stringLiteral reference, Relative, internal or absolute URLΣC0..1stringLiteral reference, Relative, internal or absolute URL
                                                                                                                                                                          .... type Σ0..1uriType the reference refers to (e.g. "Patient")
                                                                                                                                                                          Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).

                                                                                                                                                                          Σ0..1uriType the reference refers to (e.g. "Patient")
                                                                                                                                                                          Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).

                                                                                                                                                                            .... identifier Σ0..1IdentifierLogical reference, when literal reference is not knownSΣ0..1IdentifierProvider ID
                                                                                                                                                                            • Elements differ in short: 'Logical reference, when literal reference is not known' vs 'Provider ID'
                                                                                                                                                                            • Elements differ in definition: 'An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.' vs 'business identifier representing the Provider'
                                                                                                                                                                            • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                                                                                                            .... display Σ0..1stringText alternative for the resourceΣ0..1stringText alternative for the resource
                                                                                                                                                                              ... location Σ0..1Reference(Location)Where task occursΣ0..1Reference(Location)Where task occurs
                                                                                                                                                                                ... reasonCode S0..1CodeableConceptWhy task is needed
                                                                                                                                                                                Binding: ?? (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital.

                                                                                                                                                                                S0..1CodeableConceptWhy task is needed
                                                                                                                                                                                Binding: ?? (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital.

                                                                                                                                                                                  .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                                                                                                                    .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                                                                                                                                                                    Slice: Unordered, Open by value:url
                                                                                                                                                                                    0..*ExtensionAdditional content defined by implementations
                                                                                                                                                                                    Slice: Unordered, Open by value:url
                                                                                                                                                                                      .... coding Σ0..*CodingCode defined by a terminology system
                                                                                                                                                                                      Σ0..*CodingCode defined by a terminology system
                                                                                                                                                                                        .... text SΣ1..1stringPlain text representation of the conceptSΣ1..1stringPlain text representation of the concept
                                                                                                                                                                                          ... reasonReference S0..1Reference(Claim | HRex Coverage Profile)Why task is neededS0..1Reference(Claim | HRex Coverage Profile)Why task is needed
                                                                                                                                                                                          • Elements differ in comments: 'Likely targets would be HRex Coverage, PCDE Claim (for prior authorization) or a bare Claim resource for referencing an actual Claim.' vs 'Example targets would be HRex Coverage, PCDE Claim (for prior authorization) or a bare Claim resource for referencing an actual Claim.'
                                                                                                                                                                                          .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                                                                                                                            .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                                                                                                                                                                            Slice: Unordered, Open by value:url
                                                                                                                                                                                            0..*ExtensionAdditional content defined by implementations
                                                                                                                                                                                            Slice: Unordered, Open by value:url
                                                                                                                                                                                              .... reference ΣC0..1stringLiteral reference, Relative, internal or absolute URLΣC0..1stringLiteral reference, Relative, internal or absolute URL
                                                                                                                                                                                                .... type Σ0..1uriType the reference refers to (e.g. "Patient")
                                                                                                                                                                                                Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).

                                                                                                                                                                                                Σ0..1uriType the reference refers to (e.g. "Patient")
                                                                                                                                                                                                Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).

                                                                                                                                                                                                  .... identifier Σ0..1IdentifierLogical reference, when literal reference is not knownSΣ0..1IdentifierCoverage or Claim ID
                                                                                                                                                                                                  • Elements differ in short: 'Logical reference, when literal reference is not known' vs 'Coverage or Claim ID'
                                                                                                                                                                                                  • Elements differ in definition: 'An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.' vs 'business identifier representing the coverage, claim, or prior-authorization ID'
                                                                                                                                                                                                  • Elements differ in comments: 'When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).' vs 'Most payer systems will not expose their claim and prior authorization records as a FHIR resource. They will provide a unique business identifier for the claim or prior authorization using `Task.reasonReference.identifier`. This could be a payer-assigned or provider-assigned identifier which **SHOULD** be communicated in `Task.reasonReference.identifier.type` using the "FILL" for the payer and "PLAC" for the provider.'
                                                                                                                                                                                                  • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                                                                                                                                  .... display Σ0..1stringText alternative for the resourceΣ0..1stringText alternative for the resource
                                                                                                                                                                                                    ... insurance 0..*Reference(Coverage | ClaimResponse)Associated insurance coverage
                                                                                                                                                                                                    0..*Reference(Coverage | ClaimResponse)Associated insurance coverage
                                                                                                                                                                                                      ... note 0..*AnnotationComments made about the task
                                                                                                                                                                                                      0..*AnnotationComments made about the task
                                                                                                                                                                                                        ... relevantHistory 0..*Reference(Provenance)Key events in history of the Task
                                                                                                                                                                                                        0..*Reference(Provenance)Key events in history of the Task
                                                                                                                                                                                                          ... restriction 0..1BackboneElementConstraints on fulfillment tasks0..1BackboneElementConstraints on fulfillment tasks
                                                                                                                                                                                                            .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                                                                                                                                              .... extension 0..*ExtensionAdditional content defined by implementations
                                                                                                                                                                                                              0..*ExtensionAdditional content defined by implementations
                                                                                                                                                                                                                .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                                                                                                                                                ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                                                                                                                                                  .... repetitions 0..1positiveIntHow many times to repeat0..1positiveIntHow many times to repeat
                                                                                                                                                                                                                    .... period 0..1PeriodWhen fulfillment sought0..1PeriodWhen fulfillment sought
                                                                                                                                                                                                                      .... recipient 0..*Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Group | Organization)For whom is fulfillment sought?
                                                                                                                                                                                                                      0..*Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Group | Organization)For whom is fulfillment sought?
                                                                                                                                                                                                                        ... Slices for input S1..*BackboneElementInformation used to perform task
                                                                                                                                                                                                                        Slice: Unordered, Open by pattern:type
                                                                                                                                                                                                                        S1..*BackboneElementInformation used to perform task
                                                                                                                                                                                                                        Slice: Unordered, Open by pattern:type
                                                                                                                                                                                                                          .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                                                                                                                                                            .... extension 0..*ExtensionAdditional content defined by implementations
                                                                                                                                                                                                                            0..*ExtensionAdditional content defined by implementations
                                                                                                                                                                                                                              .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                                                                                                                                                              ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                                                                                                                                                                .... type 1..1CodeableConceptLabel for the input
                                                                                                                                                                                                                                Binding: ?? (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concomitent Medications", etc.

                                                                                                                                                                                                                                1..1CodeableConceptLabel for the input
                                                                                                                                                                                                                                Binding: ?? (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concomitent Medications", etc.

                                                                                                                                                                                                                                  .... value[x] 1..1base64Binary, boolean, canonical(), code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, url, uuid, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, Reference(), SampledData, Signature, Timing, ContactDetail, Contributor, DataRequirement, Expression, ParameterDefinition, RelatedArtifact, TriggerDefinition, UsageContext, Dosage, MetaContent to use in performing the task1..1base64Binary, boolean, canonical(), code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, url, uuid, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, Reference(), SampledData, Signature, Timing, ContactDetail, Contributor, DataRequirement, Expression, ParameterDefinition, RelatedArtifact, TriggerDefinition, UsageContext, Dosage, MetaContent to use in performing the task
                                                                                                                                                                                                                                    ... Slices for output S0..*BackboneElementInformation produced as part of task
                                                                                                                                                                                                                                    Slice: Unordered, Open by pattern:type
                                                                                                                                                                                                                                    SC0..*BackboneElementInformation produced as part of task
                                                                                                                                                                                                                                    Slice: Unordered, Open by pattern:type
                                                                                                                                                                                                                                      .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                                                                                                                                                                        .... extension 0..*ExtensionAdditional content defined by implementations
                                                                                                                                                                                                                                        0..*ExtensionAdditional content defined by implementations
                                                                                                                                                                                                                                          .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                                                                                                                                                                          ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                                                                                                                                                                            .... type 1..1CodeableConceptLabel for output
                                                                                                                                                                                                                                            Binding: ?? (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Identified issues", "Preliminary results", "Filler order", "Final results", etc.

                                                                                                                                                                                                                                            1..1CodeableConceptLabel for output
                                                                                                                                                                                                                                            Binding: ?? (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Identified issues", "Preliminary results", "Filler order", "Final results", etc.

                                                                                                                                                                                                                                              .... value[x] 1..1base64Binary, boolean, canonical(), code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, url, uuid, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, Reference(), SampledData, Signature, Timing, ContactDetail, Contributor, DataRequirement, Expression, ParameterDefinition, RelatedArtifact, TriggerDefinition, UsageContext, Dosage, MetaResult of output1..1base64Binary, boolean, canonical(), code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, url, uuid, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, Reference(), SampledData, Signature, Timing, ContactDetail, Contributor, DataRequirement, Expression, ParameterDefinition, RelatedArtifact, TriggerDefinition, UsageContext, Dosage, MetaResult of output

                                                                                                                                                                                                                                                doco Documentation for this format