Profile Comparison between http://hl7.org/fhir/us/bser/StructureDefinition/BSeR-ReferralTask vs http://hl7.org/fhir/us/bser/StructureDefinition/BSeR-ReferralTask

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/StructureDefinition/Task	http://hl7.org/fhir/us/bser/StructureDefinition/referral-task	Values Differ
copyright
date	2020-03-02T22:24:28+00:00	2023-07-31T02:26:57+00:00	Values Differ
description	A task resource describes an activity that can be performed and tracks the state of completion of that activity. It is used in BSeR to track the performance and state of completion of the referral service request.	This Task profile represents state of a task containing a BSeR referral service request.	Values Differ
experimental		false	Added the item 'false'
fhirVersion	4.0.1
jurisdiction
jurisdiction[0]		urn:iso:std:iso:3166#US	Added the item 'urn:iso:std:iso:3166#US'
kind	resource
name	BSeR_ReferralTask	BSeRReferralTask	Values Differ
publisher	HL7 International - Public Health Work Group	HL7 Public Health Working Group	Values Differ
purpose
status	active
title	BSeR Referral Task
type	Task
url	http://hl7.org/fhir/us/bser/StructureDefinition/BSeR-ReferralTask
version	1.0.0	2.0.0-ballot	Values Differ

Structure

Name	L Flags	L Card.	L Type	L Description & Constraints	R Flags	R Card.	L Type	L Description & Constraints	Comments
Task	C	0..*	Task	A task to be performed	C	0..*	ReferralTask	A task to be performed
id	Σ	0..1	string	Logical id of this artifact	Σ	0..1	id	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: ?? (preferred): A human language. Additional Bindings Purpose ?? Max Binding		0..1	code	Language of the resource content Binding: ?? (preferred): A human language. Additional Bindings Purpose ?? Max Binding
text		0..1	Narrative	Text summary of the resource, for human interpretation		0..1	Narrative	Text summary of the resource, for human interpretation
contained		0..*	Resource	Contained, inline Resources		0..*	Resource	Contained, inline Resources
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Additional content defined by implementations
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored	?!	0..*	Extension	Extensions that cannot be ignored
Slices for identifier		1..2	Identifier	Task Instance Identifier Slice: Unordered, Open by value:type	S	0..*	Identifier	Task Instance Identifier Slice: Unordered, Open by value:type	Elements differ in definition for mustSupport: 'false' vs 'true' Element minimum cardinalities differ: '1' vs '0' Element maximum cardinalities differ: '2' vs '2147483647'
instantiatesCanonical	Σ	0..1	canonical(ActivityDefinition)	Formal definition of task	Σ	0..1	canonical(ActivityDefinition)	Formal definition of task
instantiatesUri	Σ	0..1	uri	Formal definition of task	Σ	0..1	uri	Formal definition of task
basedOn	Σ	0..*	Reference(Resource)	Request fulfilled by this task	Σ	0..*	Reference(Resource)	Request fulfilled by this task
groupIdentifier	Σ	0..1	Identifier	Requisition or grouper id	Σ	0..1	Identifier	Requisition or grouper id
partOf	Σ	0..*	Reference(Task)	Composite task	SΣ	0..*	Reference(Task)	Composite task Slice: Unordered, Open by profile:resolve()	Elements differ in definition for mustSupport: 'false' vs 'true'
status	?!Σ	1..1	code	draft | requested | received | accepted | + Binding: ?? (required): The current status of the task.	?!SΣ	1..1	code	draft | requested | received | accepted | + Binding: ?? (required): The current status of the task.	Elements differ in definition for mustSupport: 'false' vs 'true'
statusReason	Σ	0..1	CodeableConcept	Reason for current status Binding: ?? (example): Codes to identify the reason for current status. These will typically be specific to a particular workflow.	SΣ	0..1	CodeableConcept	Reason for current status Binding: ?? (example): Codes to identify the reason for current status. These will typically be specific to a particular workflow.	Elements differ in definition for mustSupport: 'false' vs 'true'
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
Slices for extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
coding	Σ	0..*	Coding	Code defined by a terminology system	Σ	0..*	Coding	Code defined by a terminology system
text	Σ	0..1	string	Plain text representation of the concept	SΣ	1..1	string	Plain text representation of the concept	Elements differ in definition for mustSupport: 'false' vs 'true' Element minimum cardinalities differ: '0' vs '1'
businessStatus	Σ	1..1	CodeableConcept	E.g. "Specimen collected", "IV prepped" Binding: ?? (extensible)	SΣ	0..1	CodeableConcept	E.g. "Specimen collected", "IV prepped" Binding: ?? (extensible)	Elements differ in definition for mustSupport: 'false' vs 'true' Element minimum cardinalities differ: '1' vs '0'
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
Slices for extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
coding	Σ	0..*	Coding	Code defined by a terminology system	Σ	0..*	Coding	Code defined by a terminology system
text	Σ	0..1	string	Plain text representation of the concept	SΣ	0..1	string	Plain text representation of the concept	Elements differ in definition for mustSupport: 'false' vs 'true'
intent	Σ	1..1	code	unknown | 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.	SΣ	1..1	code	order Binding: ?? (required): Distinguishes whether the task is a proposal, plan or full order. Fixed Value: order	Elements differ in short: 'unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option' vs 'order' Elements differ in definition for mustSupport: 'false' vs 'true'
priority		0..1	code	routine | urgent | asap | stat Binding: ?? (required): The task's priority.		0..1	code	routine | urgent | asap | stat Binding: ?? (required): The task's priority.
code	Σ	0..1	CodeableConcept	Task Type Binding: ?? (example): Codes to identify what the task involves. These will typically be specific to a particular workflow.	SΣ	1..1	CodeableConcept	Fulfill the focal request 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/CodeSystem/task-code","code":"fulfill"}]}	Elements differ in short: 'Task Type' vs 'Fulfill the focal request' Elements differ in definition for mustSupport: 'false' vs 'true' Element minimum cardinalities differ: '0' vs '1'
description	Σ	0..1	string	Human-readable explanation of task	Σ	0..1	string	Human-readable explanation of task
focus	Σ	1..1	Reference(BSeR Referral Service Request)	What task is acting on	SΣ	1..1	Reference(BSeR Referral Service Request)	What task is acting on	Elements differ in definition for mustSupport: 'false' vs 'true'
for	Σ	0..1	Reference(Resource)	Beneficiary of the Task	SΣ	1..1	Reference(US Core Patient Profile)	Beneficiary of the Task	Elements differ in definition for mustSupport: 'false' vs 'true' Element minimum cardinalities differ: '0' vs '1'
encounter	Σ	0..1	Reference(Encounter)	Healthcare event during which this task originated	Σ	0..1	Reference(Encounter)	Healthcare event during which this task originated
executionPeriod	Σ	0..1	Period	Start and end time of execution	Σ	0..1	Period	Start and end time of execution
authoredOn	C	1..1	dateTime	Task Creation Date	SC	1..1	dateTime	Task Creation Date	Elements differ in definition for mustSupport: 'false' vs 'true'
lastModified	ΣC	0..1	dateTime	Task Last Modified Date	ΣC	0..1	dateTime	Task Last Modified Date
requester	Σ	1..1	Reference(BSeR Referral Initiator Practitioner Role)	Who is asking for task to be done	SΣ	1..1	Reference(US Core PractitionerRole Profile | US Core Practitioner Profile | US Core Organization Profile)	Referral Initiator	Elements differ in short: 'Who is asking for task to be done' vs 'Referral Initiator' Elements differ in definition for mustSupport: 'false' vs 'true'
performerType		0..*	CodeableConcept	Requested performer Binding: ?? (preferred): The type(s) of task performers allowed.		0..*	CodeableConcept	Requested performer Binding: ?? (preferred): The type(s) of task performers allowed.
owner	Σ	1..1	Reference(BSeR Referral Recipient Practitioner Role)	Responsible individual	SΣ	1..1	Reference(US Core PractitionerRole Profile)	Referral Recipient	Elements differ in short: 'Responsible individual' vs 'Referral Recipient' Elements differ in definition for mustSupport: 'false' vs 'true'
location	Σ	0..1	Reference(Location)	Where task occurs	Σ	0..1	Reference(Location)	Where task occurs
reasonCode		0..1	CodeableConcept	Why task is needed Binding: ?? (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital.		0..1	CodeableConcept	Why task is needed Binding: ?? (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital.
reasonReference		0..1	Reference(Resource)	Why task is needed		0..1	Reference(Resource)	Why task is needed
insurance		0..*	Reference(Coverage | ClaimResponse)	Associated insurance coverage		0..*	Reference(Coverage | ClaimResponse)	Associated insurance coverage
note		0..1	Annotation	Comments made about the task	S	0..*	Annotation	Comments made about the task	Elements differ in definition for mustSupport: 'false' vs 'true' Element maximum cardinalities differ: '1' vs '2147483647'
relevantHistory		0..*	Reference(Provenance)	Key events in history of the Task		0..*	Reference(Provenance)	Key events in history of the Task
restriction		0..1	BackboneElement	Constraints on fulfillment tasks		0..1	BackboneElement	Constraints on fulfillment tasks
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
repetitions		0..1	positiveInt	How many times to repeat		0..1	positiveInt	How many times to repeat
period		0..1	Period	When fulfillment sought		0..1	Period	When 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?
input		0..*	BackboneElement	Information used to perform task		0..*	BackboneElement	Information used to perform task
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label 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..1	CodeableConcept	Label 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..1	base64Binary, 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, Meta	Content to use in performing the task		1..1	base64Binary, 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, Meta	Content to use in performing the task
output		0..1	BackboneElement	Information produced as part of task	S	0..*	BackboneElement	Information produced as part of task	Elements differ in definition for mustSupport: 'false' vs 'true' Element maximum cardinalities differ: '1' vs '2147483647'
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label 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..1	CodeableConcept	Label 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..1	Reference(BSeR Referral Feedback Document Bundle)	Result of output	S	1..1	Reference(BSeR Referral Feedback Document Bundle)	Result of output	Elements differ in definition for mustSupport: 'false' vs 'true'
Documentation for this format