Profile Comparison between http://hl7.org/fhir/us/specialty-rx/StructureDefinition/specialty-rx-task-smart-launch vs http://hl7.org/fhir/us/specialty-rx/StructureDefinition/specialty-rx-task-smart-launch

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/StructureDefinition/Task
copyright
date	2020-10-02	2021-03-02T00:00:00-05:00	Values Differ
description	This profile defines Task content enabling a pharmacy or other external party to prompt clinic staff to launch a SMART app and answer prescription-related questions.
experimental	false
fhirVersion	4.0.1
jurisdiction
jurisdiction[0]	urn:iso:std:iso:3166#US
kind	resource
name	SpecialtyRxTaskSmartLaunch
publisher	HL7 International - Pharmacy
purpose
status	active
title	Specialty Rx Task - SMART Launch
type	Task
url	http://hl7.org/fhir/us/specialty-rx/StructureDefinition/specialty-rx-task-smart-launch
version	0.1.0	1.0.0	Values Differ

Structure

Name	L Flags	L Card.	L Type	L Description & Constraints	R Flags	R Card.	L Type	L Description & Constraints	Comments
Task	I				I
id	SΣ				SΣ
meta	Σ				Σ
implicitRules	?!Σ				?!Σ
language
text
contained
extension			Extension				Extension
modifierExtension	?!				?!
Slices for identifier	S				S				Elements differ in comments: "MAY contain multiple task identifiers, but one MUST be an application context ID to be passed in the appContext parameter while launching the SMART app specified in this Task." "MAY contain multiple task identifiers, but one SHALL be an application context ID to be passed in the appContext parameter while launching the SMART app specified in this Task."
instantiatesCanonical	Σ				Σ
instantiatesUri	Σ				Σ
basedOn	Σ				Σ
groupIdentifier	Σ				Σ
partOf	Σ				Σ
status	?!Σ				?!Σ
statusReason	Σ				Σ
businessStatus	Σ				Σ
intent	SΣ				SΣ
priority
code	Σ				SΣ				Elements differ in definition for mustSupport: "false" "true"
description	SΣ				SΣ
focus	SΣI				Σ				Elements differ in short: "Related Prescription" "What task is acting on" Elements differ in definition: "Related prescription order" "The request being actioned or the resource being manipulated by this task." Elements differ in comments: "The prescription to which the task pertains. Either a reference to a MedicationRequest resource or the prescription identifier set by the prescribing system MAY be present." "If multiple resources need to be manipulated, use sub-tasks. (This ensures that status can be tracked independently for each referenced resource.)." Elements differ in definition for mustSupport: "true" "false"
id
Slices for extension			Extension				Extension
reference	SΣI				ΣI				Elements differ in short: "Prescription Reference" "Literal reference, Relative, internal or absolute URL" Elements differ in definition: "Reference to the related MedicationRequest resource" "A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources." Elements differ in definition for mustSupport: "true" "false"
type	Σ				Σ
identifier	SΣ				Σ				Elements differ in short: "Placer Order Number" "Logical reference, when literal reference is not known" Elements differ in definition: "The prescription order number established by the ordering system" "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." Elements differ in comments: "Referred to as the Placer Order Number in HL7 v2 and Prescriber Order Number in NCPDP SCRIPT" "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)." Elements differ in definition for mustSupport: "true" "false"
display	SΣ				Σ				Elements differ in definition: "A human-readable description of the related prescription order" "Plain text narrative that identifies the resource in addition to the resource reference." Elements differ in comments: "A human-readable prescription description SHOULD be present. SHOULD contain the medication name and MAY contain the date written. MAY contain strength, dose form, or other specifics." "This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it." Elements differ in definition for mustSupport: "true" "false"
for	SΣ				SΣ				Elements differ in label: "Related Patient" "Related Patient in the Data Source system" Elements differ in short: "Related Patient" "Related Patient in Data Source" Elements differ in definition: "The patient for whom the related prescription was written" "The patient for whom the related prescription was written, as represented in the Data Source system"
id
Slices for extension			Extension				Extension
reference	SΣI				ΣI				Elements differ in short: "Patient Reference" "Literal reference, Relative, internal or absolute URL" Elements differ in definition: "Reference to a Patient resource" "A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources." Elements differ in definition for mustSupport: "true" "false"
type	Σ				Σ
identifier	Σ				Σ
display	Σ				Σ
encounter	Σ				Σ
executionPeriod	Σ				Σ
authoredOn	SI				SI				Elements differ in short: "Prescription Written Date" "Task Creation Date"
lastModified	ΣI				ΣI
requester	SΣI				SΣI
id
Slices for extension			Extension				Extension
reference	SΣI				SΣI
type	Σ				Σ
Slices for identifier	SΣ				SΣ
display	Σ				Σ
performerType
owner	SΣI				SΣI
id
Slices for extension			Extension				Extension
reference	SΣI				SΣI
type	Σ				Σ
identifier	SΣ				SΣ
id
Slices for extension			Extension				Extension
use	?!Σ				?!Σ
type	Σ				Σ
system	Σ				Σ
value	Σ				SΣ				Elements differ in definition for mustSupport: "false" "true"
period	Σ				Σ
assigner	Σ				Σ
display	Σ				Σ
location	Σ				Σ
reasonCode
reasonReference					SI				Elements differ in short: "Why task is needed" "Related Prescription" Elements differ in definition: "A resource reference indicating why this task needs to be performed." "Related prescription order" Elements differ in comments: "Tasks 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 `Task.reasonCode` if the data is free (uncoded) text." "The prescription to which the task pertains. Either a reference to a MedicationRequest resource or the prescription identifier set by the prescribing system MAY be present." Elements differ in definition for mustSupport: "false" "true"
id
Slices for extension			Extension				Extension
reference	ΣI				SΣI				Elements differ in short: "Literal reference, Relative, internal or absolute URL" "Prescription Reference" Elements differ in definition: "A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources." "Reference to the related MedicationRequest resource" Elements differ in definition for mustSupport: "false" "true"
type	Σ				Σ
identifier	Σ				SΣ				Elements differ in short: "Logical reference, when literal reference is not known" "Placer Order Number" 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." "The prescription order number established by the ordering system" 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)." "Referred to as the Placer Order Number in HL7 v2 and Prescriber Order Number in NCPDP SCRIPT" Elements differ in definition for mustSupport: "false" "true"
id
Slices for extension			Extension				Extension
use	?!Σ				?!Σ
type	Σ				Σ
system	Σ				Σ
value	Σ				SΣ				Elements differ in definition for mustSupport: "false" "true"
period	Σ				Σ
assigner	Σ				Σ
display	Σ				SΣ				Elements differ in definition: "Plain text narrative that identifies the resource in addition to the resource reference." "A human-readable description of the related prescription order" Elements differ in comments: "This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it." "A human-readable prescription description SHOULD be present. SHOULD contain the medication name and MAY contain the date written. MAY contain strength, dose form, or other specifics." Elements differ in definition for mustSupport: "false" "true"
insurance
note
relevantHistory
restriction
id
extension			Extension				Extension
modifierExtension	?!Σ				?!Σ
repetitions
period
recipient
Slices for input	S				S
id
extension			Extension				Extension
modifierExtension	?!Σ				?!Σ
type
value[x]
output
id
extension			Extension				Extension
modifierExtension	?!Σ				?!Σ
type
value[x]
Documentation for this format