Profile Comparison between http://hl7.org/fhir/uv/order-catalog/StructureDefinition/LabServiceDefinition vs http://hl7.org/fhir/uv/order-catalog/StructureDefinition/LabServiceDefinition

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/StructureDefinition/PlanDefinition
copyright
date	2020-08-09T15:19:11+00:00	2023-07-08T20:53:25+00:00	Values Differ
description	The LabServiceDefinition profile constrains the PlanDefinition resource to represent a laboratory diagnostic service for the clinicians, potential consumers of such services. Clinicians typically order laboratory services and use the results thereof in the course of their delivery of clinical care. A laboratory diagnostic service is a kind of clinical artifact that falls within the scope of PlanDefinition. It involves preparation of the patient, collection and delivery to the lab of biological/digital specimens , tests and panels performed on these specimens, interpretation of the results by the pathologist, and delivery of the results and diagnostic report back to the ordering clinician and possibly other recipients, including the patient. PlanDefinition conveys the general properties of the lab service. It describes the usage of the service, the contexts and situations in which this service is useful, and may also detail the goals that the laboratory service contributes to, such as screening or diagnostic of a particular pathology, monitoring of a long course treatment ... PlanDefintion references one or more instances of ActivityDefinition, describing the service in terms of laboratory procedures. Such a definition of a laboratory diagnostic service can be used in a laboratory compendium/catalog as well as in other contexts.	The LabServiceDefinition profile constrains the PlanDefinition resource to represent a laboratory diagnostic service for the clinicians using such services. Clinicians typically order laboratory services and use the results thereof in the course of their delivery of clinical care. A laboratory diagnostic service is a kind of clinical artifact that falls within the scope of PlanDefinition. It involves preparation of the patient, collection and delivery to the lab of biological/digital specimens , tests and panels performed on these specimens, interpretation of the results by the pathologist, and delivery of the results and diagnostic report back to the ordering clinician and possibly other recipients, including the patient. PlanDefinition conveys the general properties of the lab service. It describes the usage of the service, the contexts and situations in which this service is useful, and may also detail the goals that the laboratory service contributes to, such as screening or diagnostic of a particular pathology, monitoring of a long course treatment ... An instance of PlanDefintion, thus, represents a laboratory service. It references one or more instances of ActivityDefinition, describing the service in terms of laboratory procedures, with their input and output observations. The PlanDefinition also references the instances of SpecimenDefinition representing the kinds of specimens needed to perform the service. A service may be a panel or super-panel grouping other laboratory services that may also be ordered independently. In that case, the PlanDefinition of the encompassing service references the PlanDefinition resources representing the included services (relatedArtifact, type composed-of). Reflex tests are represented as sub-actions grouped in a logical group with behavior any, meaning that any number of members of the group may be performed. Each sub-action is associated with a trigger conveying the named event, which reflexes it. A definition of a laboratory diagnostic service conforming to this profile can be used in a laboratory compendium/catalog as well as in other contexts. A laboratory service is fulfilled through the execution of one or more laboratory procedures. The logical combinations of these procedures may be conjunctions (execute each of them) or disjunctions (execute at most one of them), or a mixture of both logical structures. The closest resource that may represent a service as a set of activities logically combined with this flexibility is PlanDefinition. PlanDefinition is therefore selected to represent a laboratory service, and the laboratory procedures needed to achieve this service are represented by instances of ActivityDefinition referenced by PlanDefinition, from logical groups defined in PlanDefinition.	Values Differ
experimental
fhirVersion	4.0.1	5.0.0	Values Differ
jurisdiction
jurisdiction[0]	http://unstats.un.org/unsd/methods/m49/m49.htm#001
kind	resource
name	LabServiceDefinition
publisher	HL7 International - Orders and Observations Work Group
purpose	A laboratory service is fulfilled through the execution of one or more laboratory procedures. The logical combinations of these procedures may be conjunctions (execute each of them) or disjunctions (execute at most one of them), or a mixture of both logical structures. The closest resource that may represent a service as a set of activities logically combined with this flexibility is PlanDefinition. PlanDefinition is therefore selected to represent a laboratory service, and the laboratory procedures needed to achieve this service are represented by instances of ActivityDefinition referenced by PlanDefinition, from logical groups defined in PlanDefinition.		Removed the item 'A laboratory service is fulfilled through the execution of one or more laboratory procedures. The logical combinations of these procedures may be conjunctions (execute each of them) or disjunctions (execute at most one of them), or a mixture of both logical structures. The closest resource that may represent a service as a set of activities logically combined with this flexibility is PlanDefinition. PlanDefinition is therefore selected to represent a laboratory service, and the laboratory procedures needed to achieve this service are represented by instances of ActivityDefinition referenced by PlanDefinition, from logical groups defined in PlanDefinition.'
status	draft
title	Laboratory Service Definition
type	PlanDefinition
url	http://hl7.org/fhir/uv/order-catalog/StructureDefinition/LabServiceDefinition
version	0.1.0	current	Values Differ

Structure

Name	L Flags	L Card.	L Type	L Description & Constraints	R Flags	R Card.	L Type	L Description & Constraints	Comments
PlanDefinition	C	0..*	PlanDefinition	The definition of a plan for a series of actions	C	0..*	PlanDefinition	The definition of a plan for a series of actions	Elements differ in definition: 'This resource allows for the definition of various types of plans as a sharable, consumable, and executable artifact. The resource is general enough to support the description of a broad range of clinical artifacts such as clinical decision support rules, order sets and protocols.' vs 'This resource allows for the definition of various types of plans as a sharable, consumable, and executable artifact. The resource is general enough to support the description of a broad range of clinical and non-clinical artifacts such as clinical decision support rules, order sets, protocols, and drug quality specifications.'
id	Σ	0..1	string	Logical id of this artifact	Σ	0..1	id	Logical id of this artifact	Elements differ in comments: 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation.' vs 'Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.'
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	Elements differ in comments: 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.' vs 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.'
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: ?? (required): IETF language tag for a human language	Elements differ in binding.description: 'A human language.' vs 'IETF language tag for a human language'
text		0..1	Narrative	Text summary of the resource, for human interpretation		0..1	Narrative	Text summary of the resource, for human interpretation	Elements differ in comments: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.' vs 'Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.'
contained		0..*	Resource	Contained, inline Resources		0..*	Resource	Contained, inline Resources	Elements differ in definition: 'These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.' vs 'These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.'
Slices for extension		0..*	Extension	Extension Slice: Unordered, Open by value:url		0..*	Extension	Extension Slice: Unordered, Open by value:url
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored	?!Σ	0..*	Extension	Extensions that cannot be ignored	Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
url	Σ	0..1	uri	Canonical identifier for this plan definition, represented as a URI (globally unique)	ΣC	0..1	uri	Canonical identifier for this plan definition, represented as a URI (globally unique)	Elements differ in definition: 'An absolute URI that is used to identify this plan definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this plan definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the plan definition is stored on different servers.' vs 'An absolute URI that is used to identify this plan definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which an authoritative instance of this plan definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the plan definition is stored on different servers.'
identifier	Σ	0..*	Identifier	Additional identifier for the plan definition	Σ	0..*	Identifier	Additional identifier for the plan definition
version	Σ	0..1	string	Business version of the plan definition	Σ	0..1	string	Business version of the plan definition	Elements differ in comments: 'There may be different plan definition instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the plan definition with the format [url]|[version].' vs 'There may be different plan definition instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the plan definition with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version].'
name	ΣC	0..1	string	Name for this plan definition (computer friendly)	ΣC	0..1	string	Name for this plan definition (computer friendly)
title	Σ	0..1	string	Name for this plan definition (human friendly)	Σ	0..1	string	Name for this plan definition (human friendly)
id		0..1	string	xml:id (or equivalent in JSON)		0..1	string	xml:id (or equivalent in JSON)
Slices for extension		0..*	Extension	Extension Slice: Unordered, Open by value:url		0..*	Extension	Extension Slice: Unordered, Open by value:url
value		0..1	string	Primitive value for string Max Length: 1048576		0..1	string	Primitive value for string Max Length: 1048576
subtitle		0..1	string	Subordinate title of the plan definition		0..1	string	Subordinate title of the plan definition
type	SΣ	0..1	CodeableConcept	panel | test Binding: ?? (extensible)	SΣ	0..1	CodeableConcept	panel | test Binding: ?? (extensible)
status	?!Σ	1..1	code	draft | active | retired | unknown Binding: ?? (required): The lifecycle status of an artifact.	?!Σ	1..1	code	draft | active | retired | unknown Binding: ?? (required): The lifecycle status of an artifact.	Elements differ in comments: 'Allows filtering of plan definitions that are appropriate for use versus not.' vs 'Allows filtering of plan definitions that are appropriate for use versus not. See guidance around (not) making local changes to elements [here].'
experimental	Σ	0..1	boolean	For testing purposes, not real usage	Σ	0..1	boolean	For testing purposes, not real usage
subject[x]		0..1	CodeableConcept, Reference(Group)	Type of individual the plan definition is focused on Binding: ?? (extensible): The possible types of subjects for a plan definition (E.g. Patient, Practitioner, Organization, Location, etc.).		0..1	CodeableConcept, Reference(Group | MedicinalProductDefinition | SubstanceDefinition | AdministrableProductDefinition | ManufacturedItemDefinition | PackagedProductDefinition), canonical(EvidenceVariable)	Type of individual the plan definition is focused on Binding: ?? (extensible): The possible types of subjects for a plan definition (E.g. Patient, Practitioner, Organization, Location, etc.).	Elements differ in definition: 'A code or group definition that describes the intended subject of the plan definition.' vs 'A code, group definition, or canonical reference that describes or identifies the intended subject of the plan definition. Canonical references are allowed to support the definition of protocols for drug and substance quality specifications, and is allowed to reference a MedicinalProductDefinition, SubstanceDefinition, AdministrableProductDefinition, ManufacturedItemDefinition, or PackagedProductDefinition resource.'
date	Σ	0..1	dateTime	Date last changed	Σ	0..1	dateTime	Date last changed	Elements differ in definition: 'The date (and optionally time) when the plan definition was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the plan definition changes.' vs 'The date (and optionally time) when the plan definition was last significantly changed. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the plan definition changes.' Elements differ in comments: 'Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the plan definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.' vs 'The date is often not tracked until the resource is published, but may be present on draft content. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the plan definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource. See guidance around (not) making local changes to elements [here].'
publisher	Σ	0..1	string	Name of the publisher (organization or individual)	Σ	0..1	string	Name of the publisher/steward (organization or individual)	Elements differ in short: 'Name of the publisher (organization or individual)' vs 'Name of the publisher/steward (organization or individual)' Elements differ in definition: 'The name of the organization or individual that published the plan definition.' vs 'The name of the organization or individual responsible for the release and ongoing maintenance of the plan definition.'
contact	Σ	0..*	ContactDetail	Contact details for the publisher	Σ	0..*	ContactDetail	Contact details for the publisher	Elements differ in comments: 'May be a web site, an email address, a telephone number, etc.' vs 'May be a web site, an email address, a telephone number, etc. See guidance around (not) making local changes to elements [here].'
description	Σ	0..1	markdown	Natural language description of the plan definition	Σ	0..1	markdown	Natural language description of the plan definition
id		0..1	string	xml:id (or equivalent in JSON)		0..1	string	xml:id (or equivalent in JSON)
Slices for extension		0..*	Extension	Extension Slice: Unordered, Open by value:url		0..*	Extension	Extension Slice: Unordered, Open by value:url
value		0..1	string	Primitive value for markdown		0..1	markdown	Primitive value for markdown
Slices for useContext	SΣ	0..*	UsageContext	The context that the content is intended to support Slice: Unordered, Open by pattern:code, type:value, pattern:value	SΣ	0..*	UsageContext	The context that the content is intended to support Slice: Unordered, Open by pattern:code, type:value, pattern:value
jurisdiction	Σ	0..*	CodeableConcept	Intended jurisdiction for plan definition (if applicable) Binding: ?? (extensible): Countries and regions within which this artifact is targeted for use.	ΣXD	0..*	CodeableConcept	Intended jurisdiction for plan definition (if applicable) Binding: ?? (extensible): Countries and regions within which this artifact is targeted for use.	Elements differ in comments: 'It may be possible for the plan definition to be used in jurisdictions other than those for which it was originally designed or intended.' vs 'It may be possible for the plan definition to be used in jurisdictions other than those for which it was originally designed or intended. DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)'
purpose		0..1	markdown	Why this plan definition is defined		0..1	markdown	Why this plan definition is defined
usage	S	0..1	string	Describes the clinical usage of the laboratory diagnostic service	S	0..1	markdown	Describes the clinical usage of the laboratory diagnostic service
copyright		0..1	markdown	Use and/or publishing restrictions		0..1	markdown	Use and/or publishing restrictions
approvalDate		0..1	date	When the plan definition was approved by publisher		0..1	date	When the plan definition was approved by publisher	Elements differ in comments: 'The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.' vs 'The 'date' element may be more recent than the approval date because of minor changes or editorial corrections. See guidance around (not) making local changes to elements [here].'
lastReviewDate		0..1	date	When the plan definition was last reviewed		0..1	date	When the plan definition was last reviewed by the publisher	Elements differ in short: 'When the plan definition was last reviewed' vs 'When the plan definition was last reviewed by the publisher' Elements differ in comments: 'If specified, this date follows the original approval date.' vs 'If specified, this date follows the original approval date. See guidance around (not) making local changes to elements [here].'
effectivePeriod	Σ	0..1	Period	When the plan definition is expected to be used	Σ	0..1	Period	When the plan definition is expected to be used	Elements differ in comments: 'The effective period for a plan definition determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.' vs 'The effective period for a plan definition determines when the content is applicable for usage and is independent of publication and review dates. For example, a plan definition intended to be used for the year 2016 might be published in 2015. See guidance around (not) making local changes to elements [here].'
topic	S	0..*	CodeableConcept	categorization of the laboratory service Binding: ?? (example): High-level categorization of the definition, used for searching, sorting, and filtering.	S	0..*	CodeableConcept	categorization of the laboratory service Binding: ?? (example): High-level categorization of the definition, used for searching, sorting, and filtering.
author		0..*	ContactDetail	Who authored the content		0..*	ContactDetail	Who authored the content
editor		0..*	ContactDetail	Who edited the content		0..*	ContactDetail	Who edited the content
reviewer		0..*	ContactDetail	Who reviewed the content		0..*	ContactDetail	Who reviewed the content	Elements differ in definition: 'An individual or organization primarily responsible for review of some aspect of the content.' vs 'An individual or organization asserted by the publisher to be primarily responsible for review of some aspect of the content.'
endorser		0..*	ContactDetail	Who endorsed the content		0..*	ContactDetail	Who endorsed the content	Elements differ in definition: 'An individual or organization responsible for officially endorsing the content for use in some setting.' vs 'An individual or organization asserted by the publisher to be responsible for officially endorsing the content for use in some setting.'
Slices for relatedArtifact	S	0..*	RelatedArtifact	Additional documentation, citations Slice: Unordered, Open by value:type	S	0..*	RelatedArtifact	Additional documentation, citations Slice: Unordered, Open by value:type
library		0..*	canonical(Library)	Logic used by the plan definition		0..*	canonical(Library)	Logic used by the plan definition
goal		0..*	BackboneElement	What the plan is trying to accomplish	C	0..*	BackboneElement	What the plan is trying to accomplish	Elements differ in definition: 'Goals that describe what the activities within the plan are intended to achieve. For example, weight loss, restoring an activity of daily living, obtaining herd immunity via immunization, meeting a process improvement objective, etc.' vs 'A goal describes an expected outcome that activities within the plan are intended to achieve. For example, weight loss, restoring an activity of daily living, obtaining herd immunity via immunization, meeting a process improvement objective, meeting the acceptance criteria for a test as specified by a quality specification, etc.'
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	Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
category		0..1	CodeableConcept	E.g. Treatment, dietary, behavioral Binding: ?? (example): Example codes for grouping goals for filtering or presentation.		0..1	CodeableConcept	E.g. Treatment, dietary, behavioral Binding: ?? (example): Example codes for grouping goals for filtering or presentation.
description		1..1	CodeableConcept	Code or text describing the goal Binding: ?? (example): Describes goals that can be achieved.		1..1	CodeableConcept	Code or text describing the goal Binding: ?? (example): Describes goals that can be achieved.
priority		0..1	CodeableConcept	high-priority | medium-priority | low-priority Binding: ?? (preferred): Indicates the level of importance associated with reaching or sustaining a goal.		0..1	CodeableConcept	high-priority | medium-priority | low-priority Binding: ?? (preferred): Indicates the level of importance associated with reaching or sustaining a goal.
start		0..1	CodeableConcept	When goal pursuit begins Binding: ?? (example): Identifies the types of events that might trigger the start of a goal.		0..1	CodeableConcept	When goal pursuit begins Binding: ?? (example): Identifies the types of events that might trigger the start of a goal.
addresses		0..*	CodeableConcept	What does the goal address Binding: ?? (example): Identifies problems, conditions, issues, or concerns that goals may address.		0..*	CodeableConcept	What does the goal address Binding: ?? (example): Identifies problems, conditions, issues, or concerns that goals may address.
documentation		0..*	RelatedArtifact	Supporting documentation for the goal		0..*	RelatedArtifact	Supporting documentation for the goal
target		0..*	BackboneElement	Target outcome for the goal		0..*	BackboneElement	Target outcome for the goal
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	Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
measure		0..1	CodeableConcept	The parameter whose value is to be tracked Binding: ?? (example): Identifies types of parameters that can be tracked to determine goal achievement.		0..1	CodeableConcept	The parameter whose value is to be tracked Binding: ?? (example): Identifies types of parameters that can be tracked to determine goal achievement.
detail[x]		0..1	Quantity, Range, CodeableConcept	The target value to be achieved		0..1	Quantity, Range, CodeableConcept, string, boolean, integer, Ratio	The target value to be achieved	Elements differ in definition: 'The target value of the measure to be achieved to signify fulfillment of the goal, e.g. 150 pounds or 7.0%. Either the high or low or both values of the range can be specified. When a low value is missing, it indicates that the goal is achieved at any value at or below the high value. Similarly, if the high value is missing, it indicates that the goal is achieved at any value at or above the low value.' vs 'The target value of the measure to be achieved to signify fulfillment of the goal, e.g. 150 pounds or 7.0%, or in the case of pharmaceutical quality - NMT 0.6%, Clear solution, etc. Either the high or low or both values of the range can be specified. When a low value is missing, it indicates that the goal is achieved at any value at or below the high value. Similarly, if the high value is missing, it indicates that the goal is achieved at any value at or above the low value.'
due		0..1	Duration	Reach goal within		0..1	Duration	Reach goal within
action		1..1	BackboneElement	Action defined by the plan	C	1..1	BackboneElement	Action defined by the plan
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
Slices for extension		0..*	Extension	Extension Slice: Unordered, Open by value:url		0..*	Extension	Extension Slice: Unordered, Open by value:url
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
prefix		0..1	string	User-visible prefix for the action (e.g. 1. or A.)		0..1	string	User-visible prefix for the action (e.g. 1. or A.)	Elements differ in definition: 'A user-visible prefix for the action.' vs 'A user-visible prefix for the action. For example a section or item numbering such as 1. or A.'
title		0..1	string	User-visible title		0..1	string	User-visible title	Elements differ in definition: 'The title of the action displayed to a user.' vs 'The textual description of the action displayed to a user. For example, when the action is a test to be performed, the title would be the title of the test such as Assay by HPLC.'
description		0..1	string	Brief description of the laboratory service and its method		0..1	markdown	Brief description of the laboratory service and its method
textEquivalent		0..1	string	Static text equivalent of the action, used if the dynamic aspects cannot be interpreted by the receiving system		0..1	markdown	Static text equivalent of the action, used if the dynamic aspects cannot be interpreted by the receiving system
priority		0..1	code	routine | urgent | asap | stat Binding: ?? (required): Identifies the level of importance to be assigned to actioning the request.		0..1	code	routine | urgent | asap | stat Binding: ?? (required): Identifies the level of importance to be assigned to actioning the request.
code	S	0..1	CodeableConcept	Code of the laboratory service	S	0..1	CodeableConcept	Code of the laboratory service Binding: ?? (example): Provides examples of actions to be performed.
id		0..1	string	Unique id for inter-element referencing		0..1	id	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	Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
Slices for coding	Σ	0..*	Coding	Code for the laboratory service Slice: Unordered, Open by value:system	Σ	0..*	Coding	Code for the laboratory service Slice: Unordered, Open by value:system
text	Σ	0..1	string	Plain text representation of the concept	Σ	0..1	string	Plain text representation of the concept
reason		0..*	CodeableConcept	Why the action should be performed		0..*	CodeableConcept	Why the action should be performed Binding: ?? (example): Provides examples of reasons for actions to be performed.
documentation		0..*	RelatedArtifact	Supporting documentation for the intended performer of the action		0..*	RelatedArtifact	Supporting documentation for the intended performer of the action
goalId		0..*	id	What goals this action supports	C	0..*	id	What goals this action supports	Elements differ in definition: 'Identifies goals that this action supports. The reference must be to a goal element defined within this plan definition.' vs 'Identifies goals that this action supports. The reference must be to a goal element defined within this plan definition. In pharmaceutical quality, a goal represents acceptance criteria (Goal) for a given action (Test), so the goalId would be the unique id of a defined goal element establishing the acceptance criteria for the action.'
subject[x]		0..1	CodeableConcept, Reference(Group)	Type of individual the action is focused on Binding: ?? (extensible): The possible types of subjects for a plan definition (E.g. Patient, Practitioner, Organization, Location, etc.).		0..1	CodeableConcept, Reference(Group), canonical()	Type of individual the action is focused on Binding: ?? (extensible): The possible types of subjects for a plan definition (E.g. Patient, Practitioner, Organization, Location, etc.).	Elements differ in definition: 'A code or group definition that describes the intended subject of the action and its children, if any.' vs 'A code, group definition, or canonical reference that describes the intended subject of the action and its children, if any. Canonical references are allowed to support the definition of protocols for drug and substance quality specifications, and is allowed to reference a MedicinalProductDefinition, SubstanceDefinition, AdministrableProductDefinition, ManufacturedItemDefinition, or PackagedProductDefinition resource.'
Slices for trigger	S	0..*	TriggerDefinition	When the action should be triggered Slice: Unordered, Open by value:type	S	0..*	TriggerDefinition	When the action should be triggered Slice: Unordered, Open by value:type	Elements differ in definition: 'A description of when the action should be triggered.' vs 'A description of when the action should be triggered. When multiple triggers are specified on an action, any triggering event invokes the action.'
condition		0..*	BackboneElement	Whether or not the action is applicable		0..*	BackboneElement	Whether or not the action is applicable
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	Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
kind		1..1	code	applicability | start | stop Binding: ?? (required): Defines the kinds of conditions that can appear on actions.		1..1	code	applicability | start | stop Binding: ?? (required): Defines the kinds of conditions that can appear on actions.
expression		0..1	Expression	Boolean-valued expression		0..1	Expression	Boolean-valued expression
input		0..*	DataRequirement	Input data requirements	C	0..*	BackboneElement	Input data requirements
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	Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
title						0..1	string	User-visible title	Added this element
requirement					C	0..1	DataRequirement	What data is provided	Added this element
relatedData					C	0..1	id	What data is provided	Added this element
output		0..*	DataRequirement	Output data definition	C	0..*	BackboneElement	Output data definition
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	Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
title						0..1	string	User-visible title	Added this element
requirement					C	0..1	DataRequirement	What data is provided	Added this element
relatedData					C	0..1	string	What data is provided	Added this element
relatedAction		0..*	BackboneElement	Relationship to another action	C	0..*	BackboneElement	Relationship to another action
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	Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
actionId		1..1	id	What action is this related to					Removed this element
relationship		1..1	code	before-start | before | before-end | concurrent-with-start | concurrent | concurrent-with-end | after-start | after | after-end Binding: ?? (required): Defines the types of relationships between actions.		1..1	code	before | before-start | before-end | concurrent | concurrent-with-start | concurrent-with-end | after | after-start | after-end Binding: ?? (required): Defines the types of relationships between actions.	Elements differ in short: 'before-start | before | before-end | concurrent-with-start | concurrent | concurrent-with-end | after-start | after | after-end' vs 'before | before-start | before-end | concurrent | concurrent-with-start | concurrent-with-end | after | after-start | after-end' Elements differ in definition: 'The relationship of this action to the related action.' vs 'The relationship of the start of this action to the related action.'
offset[x]		0..1	Duration, Range	Time offset for the relationship		0..1	Duration, Range	Time offset for the relationship
targetId					C	1..1	id	What action is this related to	Added this element
endRelationship						0..1	code	before | before-start | before-end | concurrent | concurrent-with-start | concurrent-with-end | after | after-start | after-end Binding: ?? (required): Defines the types of relationships between actions.	Added this element
timing[x]		0..1	dateTime, Age, Period, Duration, Range, Timing	When the action should take place		0..1	Age, Duration, Range, Timing	When the action should take place
participant		0..*	BackboneElement	Who should participate in the action		0..*	BackboneElement	Who should participate in the action
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	Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
type		1..1	code	patient | practitioner | related-person | device Binding: ?? (required): The type of participant for the action.		0..1	code	careteam | device | group | healthcareservice | location | organization | patient | practitioner | practitionerrole | relatedperson Binding: ?? (required): The type of participant in the activity.	Elements differ in short: 'patient | practitioner | related-person | device' vs 'careteam | device | group | healthcareservice | location | organization | patient | practitioner | practitionerrole | relatedperson' Element minimum cardinalities differ: '1' vs '0' Elements differ in description: 'The type of participant for the action.' vs 'The type of participant in the activity.' Elements differ in description: 'The type of participant for the action.' vs 'The type of participant in the activity.'
role		0..1	CodeableConcept	E.g. Nurse, Surgeon, Parent Binding: ?? (example): Defines roles played by participants for the action.		0..1	CodeableConcept	E.g. Nurse, Surgeon, Parent Binding: ?? (example): Defines roles played by participants for the action.
actorId						0..1	string	What actor	Added this element
typeCanonical						0..1	canonical(CapabilityStatement)	Who or what can participate	Added this element
typeReference						0..1	Reference(CareTeam | Device | DeviceDefinition | Endpoint | Group | HealthcareService | Location | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson)	Who or what can participate	Added this element
function						0..1	CodeableConcept	E.g. Author, Reviewer, Witness, etc Binding: ?? (example)	Added this element
type		0..1	CodeableConcept	create | update | remove | fire-event Binding: ?? (extensible): The type of action to be performed.		0..1	CodeableConcept	create | update | remove | fire-event Binding: ?? (extensible): The type of action to be performed.
groupingBehavior		0..1	code	visual-group | logical-group | sentence-group Binding: ?? (required): Defines organization behavior of a group. Fixed Value: logical-group		0..1	code	visual-group | logical-group | sentence-group Binding: ?? (required): Defines organization behavior of a group. Fixed Value: logical-group
selectionBehavior		0..1	code	any | all | all-or-none | exactly-one | at-most-one | one-or-more Binding: ?? (required): Defines selection behavior of a group.		0..1	code	any | all | all-or-none | exactly-one | at-most-one | one-or-more Binding: ?? (required): Defines selection behavior of a group.
requiredBehavior		0..1	code	must | could | must-unless-documented Binding: ?? (required): Defines expectations around whether an action or action group is required.		0..1	code	must | could | must-unless-documented Binding: ?? (required): Defines expectations around whether an action or action group is required.
precheckBehavior		0..1	code	yes | no Binding: ?? (required): Defines selection frequency behavior for an action or group.		0..1	code	yes | no Binding: ?? (required): Defines selection frequency behavior for an action or group.
cardinalityBehavior		0..1	code	single | multiple Binding: ?? (required): Defines behavior for an action or a group for how many times that item may be repeated.		0..1	code	single | multiple Binding: ?? (required): Defines behavior for an action or a group for how many times that item may be repeated.
definition[x]	S	0..1	canonical(Laboratory Procedure Definition) {r}	Description of the activity to be performed	S	0..1	canonical(Laboratory Procedure Definition)	Description of the activity to be performed
transform		0..1	canonical(StructureMap)	Transform to apply the template		0..1	canonical(StructureMap)	Transform to apply the template
dynamicValue		0..*	BackboneElement	Dynamic aspects of the definition		0..*	BackboneElement	Dynamic aspects of the definition
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	Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
path		0..1	string	The path to the element to be set dynamically		0..1	string	The path to the element to be set dynamically	Elements differ in definition: 'The path to the element to be customized. This is the path on the resource that will hold the result of the calculation defined by the expression. The specified path SHALL be a FHIRPath resolveable on the specified target type of the ActivityDefinition, and SHALL consist only of identifiers, constant indexers, and a restricted subset of functions. The path is allowed to contain qualifiers (.) to traverse sub-elements, as well as indexers ([x]) to traverse multiple-cardinality sub-elements (see the [Simple FHIRPath Profile] for full details).' vs 'The path to the element to be customized. This is the path on the resource that will hold the result of the calculation defined by the expression. The specified path SHALL be a FHIRPath resolvable on the specified target type of the ActivityDefinition, and SHALL consist only of identifiers, constant indexers, and a restricted subset of functions. The path is allowed to contain qualifiers (.) to traverse sub-elements, as well as indexers ([x]) to traverse multiple-cardinality sub-elements (see the [Simple FHIRPath Profile] for full details).'
expression		0..1	Expression	An expression that provides the dynamic value for the customization		0..1	Expression	An expression that provides the dynamic value for the customization
action		0..*	See action	A sub-action		0..*	See action (PlanDefinition)	A sub-action
linkId						0..1	string	Unique id for the action in the PlanDefinition	Added this element
location						0..1	CodeableReference(Location)	Where it should happen	Added this element
versionAlgorithm[x]					Σ	0..1	string, Coding	How to compare versions Binding: ?? (extensible)	Added this element
copyrightLabel						0..1	string	Copyright holder and year(s)	Added this element
actor						0..*	BackboneElement	Actors within the plan	Added this element
asNeeded[x]					Σ	0..1	boolean, CodeableConcept	Preconditions for service Binding: ?? (example): A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc.	Added this element
Documentation for this format