Generated Narrative: StructureDefinition praxis-billing-macro Name Flags Card. Type Description & Constraints<img src="[binary]" alt="doco" style="background-color: inherit"/> PlanDefinition <a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R4/conformance-rules.html#constraints" title="This element has or is affected by constraints ( billing-macro-topic-chain, billing-macro-no-action-description-binding, billing-macro-no-action-computability, billing-macro-canonical-targets, praxis-plan-specialty-system-qualified, praxis-plan-venue-organization-reference )">C 0..* PlanDefinition The definition of a plan for a series of actions, independent of any specific patient or context Constraints: billing-macro-topic-chain, billing-macro-no-action-description-binding, billing-macro-no-action-computability, billing-macro-canonical-targets, praxis-plan-specialty-system-qualified, praxis-plan-venue-organization-reference #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:stopfield 0..0 (Complex) BillingPattern Stopfield (deprecated) URL: https://fhir.cognovis.de/praxis/StructureDefinition/billingpattern-stopfield #xD; url S 1..1 uri Canonical identifier for this plan definition, represented as a URI (globally unique) #xD; Slices for identifier S 0..* Identifier Additional identifier for the plan definition Slice: Unordered, Open by value:system #xD; identifier:billingMacroId 0..1 Identifier Additional identifier for the plan definition #xD; system 1..1 uri The namespace for the identifier value Fixed Value: https://fhir.cognovis.de/praxis/sid/billing-macro-id #xD; value 1..1 string The value that is unique #xD; version S 1..1 string Business version of the plan definition #xD; title S 1..1 string Name for this plan definition (human friendly) #xD; type S 1..1 CodeableConcept order-set | clinical-protocol | eca-rule | workflow-definition Fixed Value: As shown (Order Set) #xD; coding 1..1 Coding Code defined by a terminology system Fixed Value: (Complex) #xD; system 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/plan-definition-type #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: order-set #xD; status S 1..1 code draft | active | retired | unknown Required Pattern: active #xD; description S 0..1 markdown Natural language description of the plan definition #xD; Slices for useContext S 0..* UsageContext The context that the content is intended to support Slice: Unordered, Open by pattern:code #xD; useContext:specialty 0..* UsageContext Eligible practitioner specialty (ADR-010) #xD; code 1..1 Coding Type of context being specified Required Pattern: At least the following #xD; system 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/usage-context-type #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: user #xD; value[x] 1..1 CodeableConcept Value that defines the context Binding: Praxis Healthcare Service Specialty (preferred) #xD; coding 1..* Coding Code defined by a terminology system #xD; system 1..1 uri Identity of the terminology system #xD; code 1..1 code Symbol in syntax defined by the system #xD; useContext:venue 0..* UsageContext Curated organization venue (ADR-010) #xD; code 1..1 Coding Type of context being specified Required Pattern: At least the following #xD; system 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/usage-context-type #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: venue #xD; value[x] 1..1 Reference(Organization) Value that defines the context #xD; effectivePeriod S 0..1 Period When the plan definition is expected to be used #xD; topic S 1..* CodeableConcept Discovery topic; macros use chain Binding: Praxis Plan Topic (extensible) #xD; library 0..0 Logic used by the plan definition #xD; action S 1..* BackboneElement Action defined by the plan #xD; title S 0..1 string User-visible title #xD; description 0..0 Forbidden as a binding channel (all nesting levels) #xD; condition 0..0 Whether or not the action is applicable #xD; Slices for definition[x] 0..1 canonical(ActivityDefinition | PlanDefinition | Questionnaire) Description of the activity to be performed Slice: Unordered, Open by type:$this #xD; definition[x]:definitionCanonical S 0..1 canonical(ActivityDefinition | PlanDefinition) Description of the activity to be performed #xD; definition[x]:definitionUri 0..0 Description of the activity to be performed #xD; dynamicValue 0..0 Dynamic aspects of the definition #xD; action 0..* BackboneElement A sub-action #xD; description 0..0 Brief description of the action #xD; condition 0..0 Whether or not the action is applicable #xD; Slices for definition[x] 0..1 canonical(ActivityDefinition | PlanDefinition | Questionnaire) Description of the activity to be performed Slice: Unordered, Open by type:$this #xD; definition[x]:definitionUri 0..0 Description of the activity to be performed #xD; dynamicValue 0..0 Dynamic aspects of the definition #xD; action 0..* BackboneElement A sub-action #xD; description 0..0 Brief description of the action #xD; condition 0..0 Whether or not the action is applicable #xD; Slices for definition[x] 0..1 canonical(ActivityDefinition | PlanDefinition | Questionnaire) Description of the activity to be performed Slice: Unordered, Open by type:$this #xD; definition[x]:definitionUri 0..0 Description of the activity to be performed #xD; dynamicValue 0..0 Dynamic aspects of the definition #xD; <img src="[binary]" alt="doco" style="background-color: inherit"/> Documentation for this format
Vendor-neutral PlanDefinition profile for a curated billing macro (Ziffernkette). Carries a practice-library recommendation of codes that are normally billed for a treatment situation and contract constellation. It does not prove performance or billability and must not be treated as authoritative contract membership. Distinct from: - ChargeItemDefinition catalog entries (individual billable codes) - Authoritative contract applicability evidence - PraxisWorkflowDefinition Jobs (multi-output workflows with typed inputs) Legacy PraxisBillingPattern remains readable and deprecated during migration. New macros MUST use this profile. Implements ADR-009 and ADR-010 (specialty/venue useContext). Specialty (`usage-context-type#user`) and venue (`usage-context-type#venue`) are distinct eligibility axes shared with PraxisWorkflowDefinition. Specialty matching is by Coding.system + Coding.code. Venue is an explicitly curated Organization reference. Specialty-to-organization resolution is advisory only and requires curator confirmation; source-system ownership/mandate/tenant fields are never venue authorization. Specialty evidence never replaces ADR-009 ChargeItemDefinition resolution.
The definition of a plan for a series of actions, independent of any specific patient or context
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.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
not(exists(for $id in f:contained/*/f:id/@value return $contained[not(parent::*/descendant::f:reference/@value=concat('#', $contained/*/id/@value) or descendant::f:reference[@value='#'])]))
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
Name should be usable as an identifier for the module by machine processing applications such as code generation
not(exists(f:name/@value)) or matches(f:name/@value, '[A-Z]([A-Za-z0-9_]){0,254}')
A PraxisBillingMacro MUST carry praxis-plan-topic code chain.
topic.coding.where(system = 'https://fhir.cognovis.de/praxis/CodeSystem/praxis-plan-topic' and code = 'chain').exists()
action.description MUST be absent at every nesting level; macros are not the Job binding channel.
(action | action.repeat(action)).where(description.exists()).empty()
condition, dynamicValue, and definitionUri MUST be absent at every action nesting level.
(action | action.repeat(action)).where(condition.exists() or dynamicValue.exists() or definition.ofType(uri).exists()).empty()
Every action definition canonical at every nesting depth MUST target ActivityDefinition or PlanDefinition only (never Questionnaire).
(action | action.repeat(action)).where(definition.ofType(canonical).exists()).all(definition.ofType(canonical).contains('/ActivityDefinition/') or definition.ofType(canonical).contains('/PlanDefinition/'))
Every usage-context-type#user specialty context MUST be a CodeableConcept with at least one Coding that carries both system and code. Matching is by system+code, never display text.
useContext.where(code.where(system = 'http://terminology.hl7.org/CodeSystem/usage-context-type' and code = 'user').exists()).all(value.as(CodeableConcept).exists() and value.as(CodeableConcept).coding.exists() and value.as(CodeableConcept).coding.all(system.exists() and code.exists()))
Every usage-context-type#venue context MUST be a Reference(Organization). Other value types are not a curated venue.
useContext.where(code.where(system = 'http://terminology.hl7.org/CodeSystem/usage-context-type' and code = 'venue').exists()).all(value.as(Reference).exists() and (value.as(Reference).type.empty() or value.as(Reference).type = 'Organization'))
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
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.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation
The base language in which the resource is written.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Text summary of the resource, for human interpretation
A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
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.
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.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
DEPRECATED for new authoring. Legacy stopfield (Stoppfeld) on PraxisBillingPattern chains. New Jobs MUST use PraxisWorkflowInputQuestionnaire linkIds. Retained for read compatibility during migration only.
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
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).
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
Canonical identifier for this plan definition, represented as a URI (globally unique)
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.
Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version. The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](http://hl7.org/fhir/R4/resource.html#versions). In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](http://hl7.org/fhir/R4/resource.html#meta) element to indicate where the current master source of the resource can be found.
Allows the plan definition to be referenced by a single globally unique identifier.
Additional identifier for the plan definition
A formal identifier that is used to identify this plan definition when it is represented in other formats, or referenced in a specification, model, design or an instance.
Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this plan definition outside of FHIR, where it is not possible to use the logical URI.
Allows externally provided and/or usable business identifiers to be easily associated with the module.
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
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.
usual | official | temp | secondary | old (If known)
Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.
Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.
This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one.
Identifies the purpose for this identifier, if known .
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
Allows users to make use of identifiers when the identifier system is not known.
A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
Identifier.system is always case sensitive.
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
Time period when id is/was valid for use
Time period during which identifier is/was valid for use.
Role.effectiveTime or implied by context
Organization that issued id (may be just text)
Organization that issued/manages the identifier.
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
The identifier that is used to identify this version of the plan definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the plan definition author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. To provide a version consistent with the Decision Support Service specification, use the format Major.Minor.Revision (e.g. 1.0.0). For more information on versioning knowledge assets, refer to the Decision Support Service specification. Note that a version is required for non-experimental active artifacts.
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].
Name for this plan definition (computer friendly)
A natural language name identifying the plan definition. This name should be usable as an identifier for the module by machine processing applications such as code generation.
The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.
Support human navigation and code generation.
Name for this plan definition (human friendly)
A short, descriptive, user-friendly title for the plan definition.
This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.
Subordinate title of the plan definition
An explanatory or alternate title for the plan definition giving additional information about its content.
order-set | clinical-protocol | eca-rule | workflow-definition
A high-level category for the plan definition that distinguishes the kinds of systems that would be interested in the plan definition.
The status of this plan definition. Enables tracking the life-cycle of the content.
Allows filtering of plan definitions that are appropriate for use versus not.
This is labeled as "Is Modifier" because applications should not use a retired {{title}} without due consideration
A Boolean value to indicate that this plan definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.
Enables experimental content to be developed following the same lifecycle that would be used for a production-level plan definition.
Type of individual the plan definition is focused on
A code or group definition that describes the intended subject of the plan definition.
The possible types of subjects for a plan definition (E.g. Patient, Practitioner, Organization, Location, etc.).
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.
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.
Name of the publisher (organization or individual)
The name of the organization or individual that published the plan definition.
Usually an organization but may be an individual. The publisher (or steward) of the plan definition is the organization or individual primarily responsible for the maintenance and upkeep of the plan definition. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the plan definition. This item SHOULD be populated unless the information is available from context.
Helps establish the "authority/credibility" of the plan definition. May also allow for contact.
Contact details to assist a user in finding and communicating with the publisher.
May be a web site, an email address, a telephone number, etc.
Natural language description of the plan definition
A free text natural language description of the plan definition from a consumer's perspective.
This description can be used to capture details such as why the plan definition was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the plan definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the plan definition is presumed to be the predominant language in the place the plan definition was created).
The context that the content is intended to support
The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate plan definition instances.
When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
Assist in searching for appropriate content.
Eligible practitioner specialty (ADR-010)
usage-context-type#user CodeableConcept for eligible specialty/specialties. Zero, one, or many slices are allowed. Matching is by Coding.system + Coding.code, never display. Absent specialty fails closed for specialty-based venue candidate generation.
A code that identifies the type of context being specified by this usage context.
A code that specifies a type of context being specified by a usage context.
A value that defines the context specified in this context of use. The interpretation of the value is defined by the code.
A reference to a code defined by a terminology system.
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
Allows for alternative encodings within a code system, and translations to other code systems.
fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
The identification of the code system that defines the meaning of the symbol in the code.
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
Need to be unambiguous about the source of the definition of the symbol.
fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
Need to refer to a particular code in the system.
fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
A representation of the meaning of the code in the system, following the rules of the system.
Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
C*E.2 - but note this is not well followed
fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
Plain text representation of the concept
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
Very often the text is the same as a displayName of one of the codings.
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
C*E.9. But note many systems use C*E.2 for this
fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
usage-context-type#venue Reference(Organization) for explicitly curated organization scope. Not derived from specialty alone or from source-system ownership/mandate/tenant fields. Advisory specialty-to-organization candidates require curator confirmation before publication.
Intended jurisdiction for plan definition (if applicable)
A legal or geographic region in which the plan definition is intended to be used.
It may be possible for the plan definition to be used in jurisdictions other than those for which it was originally designed or intended.
Countries and regions within which this artifact is targeted for use.
Explanation of why this plan definition is needed and why it has been designed as it has.
This element does not describe the usage of the plan definition. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this plan definition.
Describes the clinical usage of the plan
A detailed description of how the plan definition is used from a clinical perspective.
A copyright statement relating to the plan definition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the plan definition.
Consumers must be able to determine any legal restrictions on the use of the plan definition and/or its content.
When the plan definition was approved by publisher
The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage.
The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.
When the plan definition was last reviewed
The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date.
If specified, this date follows the original approval date.
Gives a sense of how "current" the content is. Resources that have not been reviewed in a long time may have a risk of being less appropriate/relevant.
When the plan definition is expected to be used
The period during which the plan definition content was or is planned to be in active use.
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.
Allows establishing a transition before a resource comes into effect and also allows for a sunsetting process when new versions of the plan definition are or are expected to be used instead.
At least one coding MUST be praxis-plan-topic#chain. Topic is a discovery aid; this profile is the semantic carrier for billing macros.
Repositories must be able to determine how to categorize the plan definition so that it can be found by topical searches.
An individiual or organization primarily involved in the creation and maintenance of the content.
An individual or organization primarily responsible for internal coherence of the content.
An individual or organization primarily responsible for review of some aspect of the content.
.participation[typeCode=VRF] {not clear whether VRF best corresponds to reviewer or endorser}
An individual or organization responsible for officially endorsing the content for use in some setting.
Related artifacts such as additional documentation, justification, or bibliographic references.
Each related artifact is either an attachment, or a reference to another resource, but not both.
Plan definitions must be able to provide enough information for consumers of the content (and/or interventions or results produced by the content) to be able to determine and understand the justification for and evidence in support of the content.
A reference to a Library resource containing any formal logic used by the plan 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.
Goal information needs to be captured for order sets, protocols, and care plan definitions to better describe the objectives of the protocol activities and to guide the creation of specific goals within the derived care plans and orders.
Extensions that cannot be ignored even if unrecognized
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).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Indicates a category the goal falls within.
Example codes for grouping goals for filtering or presentation.
Human-readable and/or coded description of a specific desired objective of care, such as "control blood pressure" or "negotiate an obstacle course" or "dance with child at wedding".
If no code is available, use CodeableConcept.text.
high-priority | medium-priority | low-priority
Identifies the expected level of importance associated with reaching/sustaining the defined goal.
Indicates the level of importance associated with reaching or sustaining a goal.
The event after which the goal should begin being pursued.
Identifies the types of events that might trigger the start of a goal.
Identifies problems, conditions, issues, or concerns the goal is intended to address.
Identifies problems, conditions, issues, or concerns that goals may address.
Didactic or other informational resources associated with the goal that provide further supporting information about the goal. Information resources can include inline text commentary and links to web resources.
Indicates what should be done and within what timeframe.
The parameter whose value is to be tracked
The parameter whose value is to be tracked, e.g. body weight, blood pressure, or hemoglobin A1c level.
Identifies types of parameters that can be tracked to determine goal achievement.
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.
Indicates the timeframe after the start of the goal in which the goal should be met.
An action or group of actions to be taken as part of the plan.
Note that there is overlap between many of the elements defined here and the ActivityDefinition resource. When an ActivityDefinition is referenced (using the definition element), the overlapping elements in the plan override the content of the referenced ActivityDefinition unless otherwise documented in the specific elements. See the PlanDefinition resource for more detailed information.
User-visible prefix for the action (e.g. 1. or A.)
The title of the action displayed to a user.
Forbidden as a binding channel (all nesting levels)
Plain description text MUST NOT carry input/output binding at any nesting depth. Binding belongs on PraxisWorkflowDefinition + Questionnaire + StructureMap.
Static text equivalent of the action, used if the dynamic aspects cannot be interpreted by the receiving system
A text equivalent of the action to be performed. This provides a human-interpretable description of the action when the definition is consumed by a system that might not be capable of interpreting it dynamically.
Indicates how quickly the action should be addressed with respect to other actions.
Identifies the level of importance to be assigned to actioning the request.
Code representing the meaning of the action or sub-actions
A code that provides meaning for the action or action group. For example, a section may have a LOINC code for the section of a documentation template.
A description of why this action is necessary or appropriate.
This is different than the clinical evidence documentation, it's an actual business description of the reason for performing the action.
Supporting documentation for the intended performer of the action
Didactic or other informational resources associated with the action that can be provided to the CDS recipient. Information resources can include inline text commentary and links to web resources.
Identifies goals that this action supports. The reference must be to a goal element defined within this plan definition.
Type of individual the action is focused on
A code or group definition that describes the intended subject of the action and its children, if any.
The subject of an action overrides the subject at a parent action or on the root of the PlanDefinition if specified. In addition, because the subject needs to be resolved during realization, use of subjects in actions (or in the ActivityDefinition referenced by the action) resolves based on the set of subjects supplied in context and by type (i.e. the patient subject would resolve to a resource of type Patient).
Multiple steps in a protocol often have different groups of steps that are focused on testing different things. The subject of an action specifies the focus of the action and any child actions.
A description of when the action should be triggered.
An expression that describes applicability criteria or start/stop conditions for the action.
When multiple conditions of the same kind are present, the effects are combined using AND semantics, so the overall condition is true only if all the conditions are true.
Applicability criteria are used to determine immediate applicability when a plan definition is applied to a given context. Start and stop criteria are carried through application and used to describe enter/exit criteria for an action.
Defines the kinds of conditions that can appear on actions.
An expression that returns true or false, indicating whether the condition is satisfied.
The expression may be inlined or may be a reference to a named expression within a logic library referenced by the library element.
Defines input data requirements for the action.
Defines the outputs of the action, if any.
A relationship to another action such as "before" or "30-60 minutes after start of".
When an action depends on multiple actions, the meaning is that all actions are dependencies, rather than that any of the actions are a dependency.
before-start | before | before-end | concurrent-with-start | concurrent | concurrent-with-end | after-start | after | after-end
The relationship of this action to the related action.
Defines the types of relationships between actions.
A duration or range of durations to apply to the relationship. For example, 30-60 minutes before.
An optional value describing when the action should be performed.
Indicates who should participate in performing the action described.
patient | practitioner | related-person | device
The role the participant should play in performing the described action.
Defines roles played by participants for the action.
The type of action to perform (create, update, remove).
visual-group | logical-group | sentence-group
Defines the grouping behavior for the action and its children.
Defines organization behavior of a group.
any | all | all-or-none | exactly-one | at-most-one | one-or-more
Defines the selection behavior for the action and its children.
Defines the required behavior for the action.
Defines expectations around whether an action or action group is required.
Defines whether the action should usually be preselected.
Defines selection frequency behavior for an action or group.
Defines whether the action can be selected multiple times.
Defines behavior for an action or a group for how many times that item may be repeated.
Description of the activity to be performed
A reference to an ActivityDefinition that describes the action to be taken in detail, or a PlanDefinition that describes a series of actions to be taken.
Note that the definition is optional, and if no definition is specified, a dynamicValue with a root ($this) path can be used to define the entire resource dynamically.
A reference to a StructureMap resource that defines a transform that can be executed to produce the intent resource using the ActivityDefinition instance as the input.
Note that when a referenced ActivityDefinition also defines a transform, the transform specified here generally takes precedence. In addition, if both a transform and dynamic values are specific, the dynamic values are applied to the result of the transform.
Customizations that should be applied to the statically defined resource. For example, if the dosage of a medication must be computed based on the patient's weight, a customization would be used to specify an expression that calculated the weight, and the path on the resource that would contain the result.
Dynamic values are applied in the order in which they are defined in the PlanDefinition resource. Note that when dynamic values are also specified by a referenced ActivityDefinition, the dynamicValues from the ActivityDefinition are applied first, followed by the dynamicValues specified here. In addition, if both a transform and dynamic values are specific, the dynamic values are applied to the result of the transform.
The path to the element to be set dynamically
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](http://hl7.org/fhir/R4/fhirpath.html#simple) for full details).
To specify the path to the current action being realized, the %action environment variable is available in this path. For example, to specify the description element of the target action, the path would be %action.description. The path attribute contains a [Simple FHIRPath Subset](http://hl7.org/fhir/R4/fhirpath.html#simple) that allows path traversal, but not calculation.
An expression that provides the dynamic value for the customization
An expression specifying the value of the customized element.
Sub actions that are contained within the action. The behavior of this action determines the functionality of the sub-actions. For example, a selection behavior of at-most-one indicates that of the sub-actions, at most one may be chosen as part of realizing the action definition.
{InverseRelationship of Definition.partOf}
A brief description of the action used to provide a summary to display to the user.