🔗 An ExtensionBillingSummary(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/order-catalog/StructureDefinition/BillingSummary; (xsd)url:string>
(<valueMarkdown:markdown>
|<valueString:string>){0,0}
< Summarizes in a human-readable manner the billing, claims and reimbursement dispositions defined for the laboratory service defined by the PlanDefinition; (xsd)textualSummary:BillingSummary.textualSummary>?
[]< code summarizing the reimbursability of the laboratory service; (xsd)reimbursabilitySummary:BillingSummary.reimbursabilitySummary>*🔗 code summarizing the reimbursability of the laboratory serviceBillingSummary.reimbursabilitySummary(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. reimbursabilitySummary; (xsd)url:string>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list). Binding: laboratory-service-reimbursability-vs (extensible, Coarse categories of reimbursement dispositions for a laboratory service); (xsd)value:code>?🔗 Summarizes in a human-readable manner the billing, claims and reimbursement dispositions defined for the laboratory service defined by the PlanDefinitionBillingSummary.textualSummary(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. textualSummary; (xsd)url:string>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).; (xsd)value:markdown>?🔗 A set of healthcare-related information that is assembled together into a single logical package that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.). While the focus of this specification is on patient-specific clinical statements, this resource can also apply to other healthcare-related statements such as study protocol designs, healthcare invoices and other activities that are not necessarily patient-specific or clinical.Catalog(xsd)(doc)=
<#base:Composition>
< The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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 its narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
< 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). Binding: all-languages (required, IETF language tag for a human language); (xsd)language:code>?
< 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 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.; (xsd)text:Narrative>?
[]< 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. 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.; (xsd)contained:Resource>*
[]< An Extension; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< An absolute URI that is used to identify this Composition 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 Composition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the Composition 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.; (xsd)url:uri>?
[]< A version-independent identifier for the Composition. This identifier stays constant as the composition is changed over time. Similar to ClinicalDocument/setId in CDA. See discussion in resource definition for how these relate.; (xsd)identifier:Identifier>*
< An explicitly assigned identifer of a variation of the content in the Composition. While each resource, including the composition itself, has its own version identifier, this is a formal identifier for the logical version of the Composition as a whole. It would remain constant if the resources were moved to a new server, and all got new individual resource versions, for example.; (xsd)version:string>?
< The workflow/clinical status of this composition. The status is a marker for the clinical standing of the document. If a composition is marked as withdrawn, the compositions/documents in the series, or data from the composition or document series, should never be displayed to a user without being clearly marked as untrustworthy. The flag "entered-in-error" is why this element is labeled as a modifier of other elements.
Some reporting work flows require that the original narrative of a final document never be altered; instead, only new narrative can be added. The composition resource has no explicit status for explicitly noting whether this business rule is in effect. This would be handled by an extension if required. Binding: composition-status (required, The workflow/clinical status of the composition.); (xsd)status:code>
< The type of document - a Catalog. For Composition type, LOINC is ubiquitous and strongly endorsed by HL7. Most implementation guides will require a specific LOINC code, or use LOINC as an extensible binding. Binding: doc-typecodes (preferred, Type of a composition.) Catalog; (xsd)type:CodeableConcept>
< The content (narrative and data) associated with the section. Binding: catalogType (example, The type of catalog.); (xsd)category:CodeableConcept>
< Who or what the composition is about. The composition can be about a person, (patient or healthcare practitioner), a device (e.g. a machine) or even a group of subjects (such as a document about a herd of livestock, or a set of patients that share a common exposure). For clinical documents, this is usually the patient.; (xsd)subject:Resource*>{0,0}
< Describes the clinical encounter or type of care this documentation is associated with.; (xsd)encounter:Encounter*>?
< When the Catalog was created. The Last Modified Date on the composition may be after the date of the document was attested without being changed. This means that the date on an amended document is the date of the amendment, not the date of original authorship.; (xsd)date:dateTime>
[]< 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 Composition instances. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:UsageContext>*
[]< Identifies who is responsible for the information in the composition, not necessarily who typed it in.; (xsd)author:(<Device>
|<Organization>
|<Patient>
|<Practitioner>
|<PractitionerRole>
|<RelatedPerson>)>+
< A natural language name identifying the {{title}}. 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.; (xsd)name:string>?
< Official human-readable label for the composition. For many compositions, the title is the same as the text or a display name of Composition.type (e.g. a "consultation" or "progress note"). Note that CDA does not make title mandatory, but there are no known cases where it is useful for title to be omitted, so it is mandatory here. Feedback on this requirement is welcome during the trial use period.; (xsd)title:string>
[]< For any additional notes. A comment, general note or annotation not coded elsewhere.; (xsd)note:Annotation>*
[]< A participant who has attested to the accuracy of the composition/document. Only list each attester once.; (xsd)attester:Catalog.attester>*
< Identifies the organization or group who is responsible for ongoing maintenance of and access to the composition/document information. This is useful when documents are derived from a composition - provides guidance for how to get the latest version of the document. This is optional because this is sometimes not known by the authoring system, and can be inferred by context. However, it is important that this information be known when working with a derived document, so providing a custodian is encouraged.; (xsd)custodian:Organization*>?
[]< Relationships that this composition has with other compositions or documents that already exist. To reference (using relatesTo) a Bundle of type "document" or another Composition where you only have the identifier, use a resourceReference with an identifier.\
When a Composition is an alternate representation of another type of document e.g. CDA, the other document could be referenced in a DocumentReference resource.
Here is an example of using relatesTo to reference another Bundle of type "document" or Composition where you only have the identifier:
```
"relatesTo": [{
"type": "replaces",
"resourceReference": {
"identifier": {
"system": "...",
"value": "..."
}
}
}]
```; (xsd)relatesTo:RelatedArtifact>*
[]< The clinical service, such as a colonoscopy or an appendectomy, being documented. The event needs to be consistent with the type element, though can provide further information if desired.; (xsd)event:Catalog.event>*
[]< The root of the sections that make up the composition.; (xsd)section:Catalog.section>*
< The period in which the Composition is valid (for Order Catalog profiles), with optional start and end dates.; (xsd)ValidityPeriod>?🔗 A participant who has attested to the accuracy of the composition/document. Only list each attester once.Catalog.attester(xsd)(doc)=
<#base:Composition.attester>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type of attestation the authenticator offers. Binding: composition-attestation-mode (preferred, The way in which a person authenticated a composition.); (xsd)mode:CodeableConcept>
< When the composition was attested by the party.; (xsd)time:dateTime>?
< Who attested the composition in the specified way.; (xsd)party:(<Organization>
|<Patient>
|<Practitioner>
|<PractitionerRole>
|<RelatedPerson>)>?🔗 The clinical service, such as a colonoscopy or an appendectomy, being documented. The event needs to be consistent with the type element, though can provide further information if desired.Catalog.event(xsd)(doc)=
<#base:Composition.event>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The period of time covered by the documentation. There is no assertion that the documentation is a complete representation for this period, only that it documents events during this time.; (xsd)period:Period>?
[]< Represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the typeCode, such as a "History and Physical Report" in which case the procedure being documented is necessarily a "History and Physical" act. The events may be included as a code or as a reference to an other resource. An event can further specialize the act inherent in the typeCode, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more events are included, they SHALL NOT conflict with the values inherent in the classCode, practiceSettingCode or typeCode, as such a conflict would create an ambiguous situation. This short list of codes is provided to be used as key words for certain types of queries. Binding: http://terminology.hl7.org/ValueSet/v3-ActCode (example, This list of codes represents the main clinical acts being documented.); (xsd)detail:Resource*>*🔗 The root of the sections that make up the composition.Catalog.section(xsd)(doc)=
<#base:Composition.section>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element.; (xsd)title:string>?
< A code identifying the kind of content contained within the section. This must be consistent with the section title. The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document.
If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. Binding: doc-section-codes (example, Classification of a section of a composition/document.); (xsd)code:CodeableConcept>?
[]< Identifies who is responsible for the information in this section, not necessarily who typed it in.; (xsd)author:(<Device>
|<Organization>
|<Patient>
|<Practitioner>
|<PractitionerRole>
|<RelatedPerson>)>*
< The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples.; (xsd)focus:Resource*>?
< A human-readable narrative that contains the attested content of the section, 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. Document profiles may define what content should be represented in the narrative to ensure clinical safety.; (xsd)text:Narrative>?
< Specifies the order applied to the items in the section entries. Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. Binding: list-order (preferred, What order applies to the items in the entry.); (xsd)orderedBy:CodeableConcept>?
[]< A reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided.; (xsd)entry:Resource*>*
< If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. Binding: list-empty-reason (preferred, If a section is empty, why it is empty.); (xsd)emptyReason:CodeableConcept>?
[]< A nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.; (xsd)section:Composition.section>*🔗 A set of healthcare-related information that is assembled together into a single logical package that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.). While the focus of this specification is on patient-specific clinical statements, this resource can also apply to other healthcare-related statements such as study protocol designs, healthcare invoices and other activities that are not necessarily patient-specific or clinical.CatalogHeader(xsd)(doc)=
<#base:Composition>
< The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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 its narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
< 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). Binding: all-languages (required, IETF language tag for a human language); (xsd)language:code>?
< 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 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.; (xsd)text:Narrative>?
[]< 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. 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.; (xsd)contained:Resource>*
[]< An Extension; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< An absolute URI that is used to identify this Composition 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 Composition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the Composition 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.; (xsd)url:uri>?
[]< A version-independent identifier for the Composition. This identifier stays constant as the composition is changed over time. Similar to ClinicalDocument/setId in CDA. See discussion in resource definition for how these relate.; (xsd)identifier:Identifier>*
< An explicitly assigned identifer of a variation of the content in the Composition. While each resource, including the composition itself, has its own version identifier, this is a formal identifier for the logical version of the Composition as a whole. It would remain constant if the resources were moved to a new server, and all got new individual resource versions, for example.; (xsd)version:string>?
< The workflow/clinical status of this composition. The status is a marker for the clinical standing of the document. If a composition is marked as withdrawn, the compositions/documents in the series, or data from the composition or document series, should never be displayed to a user without being clearly marked as untrustworthy. The flag "entered-in-error" is why this element is labeled as a modifier of other elements.
Some reporting work flows require that the original narrative of a final document never be altered; instead, only new narrative can be added. The composition resource has no explicit status for explicitly noting whether this business rule is in effect. This would be handled by an extension if required. Binding: composition-status (required, The workflow/clinical status of the composition.); (xsd)status:code>
< Specifies the particular kind of composition (e.g. History and Physical, Discharge Summary, Progress Note). This usually equates to the purpose of making the composition. For Composition type, LOINC is ubiquitous and strongly endorsed by HL7. Most implementation guides will require a specific LOINC code, or use LOINC as an extensible binding. Binding: doc-typecodes (preferred, Type of a composition.); (xsd)type:CatalogHeader.type>
[]< A categorization for the type of the composition - helps for indexing and searching. This may be implied by or derived from the code specified in the Composition Type. Binding: catalogType (example, Category of catalog content); (xsd)category:CodeableConcept>*
[]< The catalog may be set up to be used in the context of a particular plan or set of financial, organizational or legal dispositions For example the catalog may provide the details of reimbursement of its items within the context of an insurance plan handled by a payer; (xsd)subject:Resource*>*
< Describes the clinical encounter or type of care this documentation is associated with.; (xsd)encounter:Encounter*>{0,0}
< The composition editing time, when the composition was last logically changed by the author. The Last Modified Date on the composition may be after the date of the document was attested without being changed. This means that the date on an amended document is the date of the amendment, not the date of original authorship.; (xsd)date:dateTime>
[]< 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 Composition instances. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:UsageContext>*
[]< An organization authoring and owning the content of the catalog In general there is a single author for a catalog. However there may be use cases where multiple authors contribute to various parts of a catalog, each author owning one part and being responsible for its content.; (xsd)author:Organization*>+
< A natural language name identifying the {{title}}. 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.; (xsd)name:string>?
< Official human-readable label for the composition. For many compositions, the title is the same as the text or a display name of Composition.type (e.g. a "consultation" or "progress note"). Note that CDA does not make title mandatory, but there are no known cases where it is useful for title to be omitted, so it is mandatory here. Feedback on this requirement is welcome during the trial use period.; (xsd)title:CatalogHeader.title>
[]< For any additional notes. A comment, general note or annotation not coded elsewhere.; (xsd)note:Annotation>*
< A participant who has attested to the accuracy of the composition/document. Only list each attester once.; (xsd)attester:CatalogHeader.attester>?
< Identifies the organization or group who is responsible for ongoing maintenance of and access to the composition/document information. This is useful when documents are derived from a composition - provides guidance for how to get the latest version of the document. This is optional because this is sometimes not known by the authoring system, and can be inferred by context. However, it is important that this information be known when working with a derived document, so providing a custodian is encouraged.; (xsd)custodian:Organization*>
[]< Relationships that this composition has with other compositions or documents that already exist. To reference (using relatesTo) a Bundle of type "document" or another Composition where you only have the identifier, use a resourceReference with an identifier.\
When a Composition is an alternate representation of another type of document e.g. CDA, the other document could be referenced in a DocumentReference resource.
Here is an example of using relatesTo to reference another Bundle of type "document" or Composition where you only have the identifier:
```
"relatesTo": [{
"type": "replaces",
"resourceReference": {
"identifier": {
"system": "...",
"value": "..."
}
}
}]
```; (xsd)relatesTo:RelatedArtifact>*
< The clinical service, such as a colonoscopy or an appendectomy, being documented. The event needs to be consistent with the type element, though can provide further information if desired.; (xsd)event:CatalogHeader.event>{0,0}
< The root of the sections that make up the composition.; (xsd)section:CatalogHeader.section>{0,0}
< The period in which the Composition is valid (for Order Catalog profiles), with optional start and end dates.; (xsd)ValidityPeriod>?🔗 A participant who has attested to the accuracy of the composition/document. Only list each attester once.CatalogHeader.attester(xsd)(doc)=
<#base:Composition.attester>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type of attestation the authenticator offers. Binding: composition-attestation-mode (preferred, The way in which a person authenticated a composition.); (xsd)mode:CodeableConcept>
< When the composition was attested by the party.; (xsd)time:dateTime>
< Who attested the composition in the specified way.; (xsd)party:(<Organization>
|<Patient>
|<Practitioner>
|<PractitionerRole>
|<RelatedPerson>)>?🔗 The clinical service, such as a colonoscopy or an appendectomy, being documented. The event needs to be consistent with the type element, though can provide further information if desired.CatalogHeader.event(xsd)(doc)=
<#base:Composition.event>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The period of time covered by the documentation. There is no assertion that the documentation is a complete representation for this period, only that it documents events during this time.; (xsd)period:Period>?
[]< Represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the typeCode, such as a "History and Physical Report" in which case the procedure being documented is necessarily a "History and Physical" act. The events may be included as a code or as a reference to an other resource. An event can further specialize the act inherent in the typeCode, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more events are included, they SHALL NOT conflict with the values inherent in the classCode, practiceSettingCode or typeCode, as such a conflict would create an ambiguous situation. This short list of codes is provided to be used as key words for certain types of queries. Binding: http://terminology.hl7.org/ValueSet/v3-ActCode (example, This list of codes represents the main clinical acts being documented.); (xsd)detail:Resource*>*🔗 The root of the sections that make up the composition.CatalogHeader.section(xsd)(doc)=
<#base:Composition.section>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element.; (xsd)title:string>?
< A code identifying the kind of content contained within the section. This must be consistent with the section title. The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document.
If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. Binding: doc-section-codes (example, Classification of a section of a composition/document.); (xsd)code:CodeableConcept>?
[]< Identifies who is responsible for the information in this section, not necessarily who typed it in.; (xsd)author:(<Device>
|<Organization>
|<Patient>
|<Practitioner>
|<PractitionerRole>
|<RelatedPerson>)>*
< The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples.; (xsd)focus:Resource*>?
< A human-readable narrative that contains the attested content of the section, 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. Document profiles may define what content should be represented in the narrative to ensure clinical safety.; (xsd)text:Narrative>?
< Specifies the order applied to the items in the section entries. Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. Binding: list-order (preferred, What order applies to the items in the entry.); (xsd)orderedBy:CodeableConcept>?
[]< A reference to the actual resource from which the narrative in the section is derived. If there are no entries in the list, an emptyReason SHOULD be provided.; (xsd)entry:Resource*>*
< If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. Binding: list-empty-reason (preferred, If a section is empty, why it is empty.); (xsd)emptyReason:CodeableConcept>?
[]< A nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.; (xsd)section:Composition.section>*🔗 Official human-readable label for the composition. For many compositions, the title is the same as the text or a display name of Composition.type (e.g. a "consultation" or "progress note"). Note that CDA does not make title mandatory, but there are no known cases where it is useful for title to be omitted, so it is mandatory here. Feedback on this requirement is welcome during the trial use period.CatalogHeader.title(xsd)(doc)=
<#base:string>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< The actual value; (xsd)value:string>?
[]< Language translation from base language of resource to another language.; (xsd)OtherTitle:Extension>*🔗 Specifies the particular kind of composition (e.g. History and Physical, Discharge Summary, Progress Note). This usually equates to the purpose of making the composition. For Composition type, LOINC is ubiquitous and strongly endorsed by HL7. Most implementation guides will require a specific LOINC code, or use LOINC as an extensible binding. Binding: doc-typecodes (preferred, Type of a composition.)CatalogHeader.type(xsd)(doc)=
<#base:CodeableConcept>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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.; (xsd)coding:Coding>*
< 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. Catalog; (xsd)text:string>🔗 Defines the characteristics of a message that can be shared between systems, including the type of event that initiates the message, the content to be transmitted and what response(s), if any, are permitted. This would be a MIF-level artifact.CatalogMessageDefinition(xsd)(doc)=
<#base:MessageDefinition>
< The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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 its narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
< 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). Binding: all-languages (required, IETF language tag for a human language); (xsd)language:code>?
< 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 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.; (xsd)text:Narrative>?
[]< 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. 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.; (xsd)contained:Resource>*
[]< May be used to represent additional information that is not part of the basic definition of the resource. 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The business identifier that is used to reference the MessageDefinition and *is* expected to be consistent from server to server. 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/R5/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/R5/resource.html#meta) element to indicate where the current master source of the resource can be found.; (xsd)url:uri>?
[]< A formal identifier that is used to identify this message 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 message definition outside of FHIR, where it is not possible to use the logical URI.; (xsd)identifier:Identifier>*
< The identifier that is used to identify this version of the message definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the message 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. There may be different message 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 message definition with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](http://hl7.org/fhir/R5/resource.html#bv-format).; (xsd)version:string>?
< Indicates the mechanism used to compare versions to determine which is more current. If set as a string, this is a FHIRPath expression that has two additional context variables passed in - %version1 and %version2 and will return a negative number if version1 is newer, a positive number if version2 and a 0 if the version ordering can't be successfully be determined. Binding: version-algorithm (extensible, ); (xsd)versionAlgorithm:(<Coding>
|<string>)>?
< A natural language name identifying the message 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.; (xsd)name:string>?
< A short, descriptive, user-friendly title for the message definition. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; (xsd)title:string>?
[]< A MessageDefinition that is superseded by this definition.; (xsd)replaces:MessageDefinition*>*
< The status of this message definition. Enables tracking the life-cycle of the content. Allows filtering of message definitions that are appropriate for use versus not.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization). Binding: publication-status (required, The lifecycle status of an artifact.); (xsd)status:code>
< A Boolean value to indicate that this message definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Allows filtering of message definitions that are appropriate for use versus not.; (xsd)experimental:boolean>?
< The date (and optionally time) when the message 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 message definition changes. 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 message 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](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)date:dateTime>
< The name of the organization or individual responsible for the release and ongoing maintenance of the message definition. Usually an organization but may be an individual. The publisher (or steward) of the message definition is the organization or individual primarily responsible for the maintenance and upkeep of the message 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 message definition. This item SHOULD be populated unless the information is available from context.; (xsd)publisher:string>?
[]< 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.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)contact:ContactDetail>*
< A free text natural language description of the message definition from a consumer's perspective. This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the message 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 message definition is presumed to be the predominant language in the place the message definition was created).; (xsd)description:markdown>?
[]< 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 message definition instances. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:UsageContext>*
[]< A legal or geographic region in which the message definition is intended to be used. It may be possible for the message 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.) Binding: jurisdiction (extensible, Countries and regions within which this artifact is targeted for use.); (xsd)jurisdiction:CodeableConcept>*
< Explanation of why this message definition is needed and why it has been designed as it has. This element does not describe the usage of the message 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 message definition.; (xsd)purpose:markdown>?
< A copyright statement relating to the message definition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the message definition.; (xsd)copyright:markdown>?
< A short string (<50 characters), suitable for inclusion in a page footer that identifies the copyright holder, effective period, and optionally whether rights are resctricted. (e.g. 'All rights reserved', 'Some rights reserved'). The (c) symbol should NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general 'copyright' element.; (xsd)copyrightLabel:string>?
< The MessageDefinition that is the basis for the contents of this resource.; (xsd)base:MessageDefinition*>?
[]< Identifies a protocol or workflow that this MessageDefinition represents a step in. It should be possible to use MessageDefinition to describe a message to be used by certain steps in a particular protocol as part of a PlanDefinition or ActivityDefinition.; (xsd)parent:(<ActivityDefinition>
|<PlanDefinition>)>*
< Event code for messages conveying order-catalog content Binding: catalog-message-events-vs (extensible, message events for messages conveying order-catalog content); (xsd)event:Coding>
< The impact of the content of the message. Binding: message-significance-category (required, The impact of the content of a message.) consequence; (xsd)category:code>?
[]< Identifies the resource (or resources) that are being addressed by the event. For example, the Encounter for an admit message or two Account records for a merge.; (xsd)focus:CatalogMessageDefinition.focus>*
< Declare at a message definition level whether a response is required or only upon error or success, or never. This enables the capability currently available through MSH-16 (Application Level acknowledgement) in HL7 Version 2 to declare at a message instance level whether a response is required or only upon error or success, or never. Binding: messageheader-response-request (required, This enables the capability currently available through MSH-16 (Application Level acknowledgement) in HL7 Version 2 to declare at a message definition level whether a response is required or only upon error or success, or never.); (xsd)responseRequired:code>
[]< Indicates what types of messages may be sent as an application-level response to this message. This indicates an application level response to "close" a transaction implicit in a particular request message. To define a complete workflow scenario, look to the [[PlanDefinition]] resource which allows the definition of complex orchestrations, conditionality, etc.; (xsd)allowedResponse:CatalogMessageDefinition.allowedResponse>*
< Graph is Canonical reference to a GraphDefinition. If a URL is provided, it is the canonical reference to a GraphDefinition that it controls what additional resources are to be added to the Bundle when building the message. The GraphDefinition can also specify profiles that apply to the various resources.; (xsd)graph:GraphDefinition*>?🔗 Indicates what types of messages may be sent as an application-level response to this message. This indicates an application level response to "close" a transaction implicit in a particular request message. To define a complete workflow scenario, look to the [[PlanDefinition]] resource which allows the definition of complex orchestrations, conditionality, etc.CatalogMessageDefinition.allowedResponse(xsd)(doc)=
<#base:MessageDefinition.allowedResponse>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A reference to the message definition that must be adhered to by this supported response.; (xsd)message:MessageDefinition*>
< Provides a description of the circumstances in which this response should be used (as opposed to one of the alternative responses).; (xsd)situation:markdown>?🔗 Identifies the resource (or resources) that are being addressed by the event. For example, the Encounter for an admit message or two Account records for a merge.CatalogMessageDefinition.focus(xsd)(doc)=
<#base:MessageDefinition.focus>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The kind of resource that must be the focus for this message. Multiple focuses addressing different resources may occasionally occur. E.g. to link or unlink a resource from a particular account or encounter, etc. Binding: resource-types (required, One of the resource types defined as part of this version of FHIR.); (xsd)code>
< A profile that reflects constraints for the focal resource (and potentially for related resources). This should be present for most message definitions. However, if the message focus is only a single resource and there is no need to include referenced resources or otherwise enforce the presence of particular elements, it can be omitted.; (xsd)profile:StructureDefinition*>?
< Identifies the minimum number of resources of this type that must be pointed to by a message in order for it to be valid against this MessageDefinition.; (xsd)min:unsignedInt>
< Identifies the maximum number of resources of this type that must be pointed to by a message in order for it to be valid against this MessageDefinition.; (xsd)max:string>?🔗 This extension to PlanDefinition, MedicationKnowledge and DeviceDefinition conveys the reference to a catalog containing the extended resourceCatalogReference(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
< An Extension; (xsd)extension:Extension>{0,0}
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/order-catalog/StructureDefinition/CatalogReference; (xsd)url:string>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).; (xsd)value:CatalogHeader*>?🔗 A single issue - either an indication, contraindication, interaction or an undesirable effect for a medicinal product, medication, device or procedure.ContraindicationDefinition(xsd)(doc)=
<#base:ClinicalUseDefinition>
< The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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 its narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
< 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). Binding: all-languages (required, IETF language tag for a human language); (xsd)language:code>?
< 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 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.; (xsd)text:Narrative>?
[]< 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. 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.; (xsd)contained:Resource>*
[]< May be used to represent additional information that is not part of the basic definition of the resource. 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Business identifier for this issue.; (xsd)identifier:Identifier>*
< indication | contraindication | interaction | undesirable-effect | warning. Binding: clinical-use-definition-type (required, Overall defining type of this clinical use definition.) contraindication; (xsd)type:code>
[]< A categorisation of the issue, primarily for dividing warnings into subject heading areas such as "Pregnancy and Lactation", "Overdose", "Effects on Ability to Drive and Use Machines". Binding: clinical-use-definition-category (preferred, A categorisation for a clinical use information item.); (xsd)category:CodeableConcept>*
[]< The medication, product, substance, device, procedure etc. for which this is an indication.; (xsd)subject:(<ActivityDefinition>
|<BiologicallyDerivedProduct>
|<Device>
|<DeviceDefinition>
|<Medication>
|<MedicinalProductDefinition>
|<NutritionProduct>
|<PlanDefinition>
|<Substance>)>*
< Whether this is a current issue or one that has been retired etc. Binding: publication-status (preferred, The lifecycle status of an artifact.); (xsd)status:CodeableConcept>?
< Specifics for when this is a contraindication.; (xsd)contraindication:ContraindicationDefinition.contraindication>
< Specifics for when this is an indication.; (xsd)indication:ContraindicationDefinition.indication>{0,0}
< Specifics for when this is an interaction.; (xsd)interaction:ContraindicationDefinition.interaction>{0,0}
[]< The population group to which this applies.; (xsd)population:Group*>*
[]< Logic used by the clinical use definition.; (xsd)library:Library*>*
< Describe the possible undesirable effects (negative outcomes) from the use of the medicinal product as treatment.; (xsd)undesirableEffect:ContraindicationDefinition.undesirableEffect>{0,0}
< A critical piece of information about environmental, health or physical risks or hazards that serve as caution to the user. For example 'Do not operate heavy machinery', 'May cause drowsiness', or 'Get medical advice/attention if you feel unwell'.; (xsd)warning:ContraindicationDefinition.warning>{0,0}🔗 Specifics for when this is a contraindication.ContraindicationDefinition.contraindication(xsd)(doc)=
<#base:ClinicalUseDefinition.contraindication>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The situation that is being documented as contraindicating against this item. Binding: disease-symptom-procedure (example, A symptom, disease or procedure.); (xsd)diseaseSymptomProcedure:ObservationDefinition*>?
< The status of the disease or symptom for the contraindication, for example "chronic" or "metastatic". Binding: disease-status (example, The status of a disease or symptom.); (xsd)diseaseStatus:ObservationDefinition*>?
[]< A comorbidity (concurrent condition) or coinfection. Binding: disease-symptom-procedure (example, A symptom, disease or procedure.); (xsd)comorbidity:ObservationDefinition*>*
[]< The indication which this is a contraidication for.; (xsd)indication:ClinicalUseDefinition*>*
< An expression that returns true or false, indicating whether the indication is applicable or not, after having applied its other elements. The expression may be inlined or may be a reference to a named expression within a logic library referenced by the library element.; (xsd)applicability:Expression>?
[]< Information about the use of the medicinal product in relation to other therapies described as part of the contraindication.; (xsd)otherTherapy:ContraindicationDefinition.contraindication.otherTherapy>*🔗 Information about the use of the medicinal product in relation to other therapies described as part of the contraindication.ContraindicationDefinition.contraindication.otherTherapy(xsd)(doc)=
<#base:ClinicalUseDefinition.contraindication.otherTherapy>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type of relationship between the medicinal product indication or contraindication and another therapy. Binding: therapy-relationship-type (preferred, Classification of relationship between a therapy and a contraindication or an indication.); (xsd)relationshipType:CodeableConcept>
< Reference to a specific medication (active substance, medicinal product or class of products, biological, food etc.) as part of an indication or contraindication. Binding: therapy (example, A therapy.); (xsd)treatment:(<ActivityDefinition>
|<BiologicallyDerivedProduct>
|<Medication>
|<MedicinalProductDefinition>
|<NutritionProduct>
|<Substance>
|<SubstanceDefinition>)>🔗 Specifics for when this is an indication.ContraindicationDefinition.indication(xsd)(doc)=
<#base:ClinicalUseDefinition.indication>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The situation that is being documented as an indicaton for this item. Binding: disease-symptom-procedure (example, A symptom, disease or procedure.); (xsd)diseaseSymptomProcedure:ObservationDefinition*>?
< The status of the disease or symptom for the indication, for example "chronic" or "metastatic". Binding: disease-status (example, The status of a disease or symptom.); (xsd)diseaseStatus:ObservationDefinition*>?
[]< A comorbidity (concurrent condition) or coinfection as part of the indication. Binding: disease-symptom-procedure (example, A symptom, disease or procedure.); (xsd)comorbidity:ObservationDefinition*>*
< The intended effect, aim or strategy to be achieved. Binding: product-intended-use (preferred, The overall intended use of a product.); (xsd)intendedEffect:ObservationDefinition*>?
< Timing or duration information, that may be associated with use with the indicated condition e.g. Adult patients suffering from myocardial infarction (from a few days until less than 35 days), ischaemic stroke (from 7 days until less than 6 months).; (xsd)duration:(<Range>
|<string>)>?
[]< An unwanted side effect or negative outcome that may happen if you use the drug (or other subject of this resource) for this indication.; (xsd)undesirableEffect:ClinicalUseDefinition*>*
< An expression that returns true or false, indicating whether the indication is applicable or not, after having applied its other elements. The expression may be inlined or may be a reference to a named expression within a logic library referenced by the library element.; (xsd)applicability:Expression>?
[]< Information about the use of the medicinal product in relation to other therapies described as part of the indication.; (xsd)otherTherapy:ClinicalUseDefinition.contraindication.otherTherapy>*🔗 Specifics for when this is an interaction.ContraindicationDefinition.interaction(xsd)(doc)=
<#base:ClinicalUseDefinition.interaction>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< The specific medication, product, food, substance etc. or laboratory test that interacts.; (xsd)interactant:ContraindicationDefinition.interaction.interactant>*
< The type of the interaction e.g. drug-drug interaction, drug-food interaction, drug-lab test interaction. Binding: interaction-type (example, A categorisation for an interaction between two substances.); (xsd)type:CodeableConcept>?
< The effect of the interaction, for example "reduced gastric absorption of primary medication". Binding: interaction-effect (example, A interaction effect of clinical use of a medication or other substance.); (xsd)effect:ObservationDefinition*>?
< The incidence of the interaction, e.g. theoretical, observed. Binding: interaction-incidence (example, A categorisation for incidence of occurence of an interaction.); (xsd)incidence:CodeableConcept>?
[]< Actions for managing the interaction. Binding: interaction-management (example, A type of management for an interaction of a medication or other substance.); (xsd)management:CodeableConcept>*🔗 The specific medication, product, food, substance etc. or laboratory test that interacts.ContraindicationDefinition.interaction.interactant(xsd)(doc)=
<#base:ClinicalUseDefinition.interaction.interactant>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The specific medication, product, food, substance etc. or laboratory test that interacts. Binding: interactant (example, An interactant - a substance that may have a clinically significant effect on another.); (xsd)item:(<BiologicallyDerivedProduct>
|<CodeableConcept>
|<Medication>
|<MedicinalProductDefinition>
|<NutritionProduct>
|<ObservationDefinition>
|<Substance>)>🔗 Describe the possible undesirable effects (negative outcomes) from the use of the medicinal product as treatment.ContraindicationDefinition.undesirableEffect(xsd)(doc)=
<#base:ClinicalUseDefinition.undesirableEffect>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The situation in which the undesirable effect may manifest. Binding: undesirable-effect-symptom (example, An undesirable effect of clinical use.); (xsd)symptomConditionEffect:ObservationDefinition*>?
< High level classification of the effect. Binding: undesirable-effect-classification (example, A categorisation for an undesirable effect.); (xsd)classification:CodeableConcept>?
< How often the effect is seen. Binding: undesirable-effect-frequency (example, A categorisation for a frequency of occurence of an undesirable effect.); (xsd)frequencyOfOccurrence:CodeableConcept>?🔗 A critical piece of information about environmental, health or physical risks or hazards that serve as caution to the user. For example 'Do not operate heavy machinery', 'May cause drowsiness', or 'Get medical advice/attention if you feel unwell'.ContraindicationDefinition.warning(xsd)(doc)=
<#base:ClinicalUseDefinition.warning>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A textual definition of this warning, with formatting.; (xsd)description:markdown>?
< A coded or unformatted textual definition of this warning. Binding: warning-type (example, Classification of warning type.); (xsd)code:CodeableConcept>?🔗 The characteristics, operational status and capabilities of a medical-related component of a medical device. For the initial scope, this DeviceDefinition resource is only applicable to describe a single node in the containment tree that is produced by the context scanner in any medical device that implements or derives from the ISO/IEEE 11073 standard and that does not represent a metric. Examples for such a node are MDS, VMD, or Channel.DeviceModel(xsd)(doc)=
<#base:DeviceDefinition>
< The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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 its narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
< 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). Binding: all-languages (required, IETF language tag for a human language); (xsd)language:code>?
< 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 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.; (xsd)text:Narrative>?
[]< 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. 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.; (xsd)contained:Resource>*
[]< An Extension; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Additional information to describe the device.; (xsd)description:markdown>?
[]< This repeatable element is used in catalogs of devices to convey any kind of identifier assigned to the model of device, other than the primary UDI DI.
identifier may convey for instance, the secondary UDI-DI, the direct-marking UDI-DI, the unit-of-use UDI-DI or any additional non-UDI identifier.; (xsd)identifier:Identifier>*
[]< Unique device identifier (UDI) assigned to device label or package. Note that the Device may include multiple udiCarriers as it either may include just the udiCarrier for the jurisdiction it is sold, or for multiple jurisdictions it could have been sold.; (xsd)udiDeviceIdentifier:DeviceModel.udiDeviceIdentifier>*
[]< Identifier associated with the regulatory documentation (certificates, technical documentation, post-market surveillance documentation and reports) of a set of device models sharing the same intended purpose, risk class and essential design and manufacturing characteristics. One example is the Basic UDI-DI in Europe. This should not be used for regulatory authorization numbers which are to be captured elsewhere.; (xsd)regulatoryIdentifier:DeviceModel.regulatoryIdentifier>*
< The part number or catalog number of the device. Alphanumeric Maximum 20.; (xsd)partNumber:string>?
< A name of the manufacturer or legal representative e.g. labeler. Whether this is the actual manufacturer or the labeler or responsible depends on implementation and jurisdiction.; (xsd)manufacturer:Organization*>?
[]< The name or names of the device as given by the manufacturer.; (xsd)deviceName:DeviceModel.deviceName>*
< The model number for the device for example as defined by the manufacturer or labeler, or other agency.; (xsd)modelNumber:string>?
[]< What kind of device or device system this is. In this element various classifications can be used, such as GMDN, EMDN, SNOMED CT, risk classes, national product codes.; (xsd)classification:DeviceModel.classification>*
[]< Identifies the standards, specifications, or formal guidances for the capabilities supported by the device. The device may be certified as conformant to these specifications e.g., communication, performance, process, measurement, or specialization standards.; (xsd)conformsTo:DeviceModel.conformsTo>*
[]< A device that is part (for example a component) of the present device.; (xsd)hasPart:DeviceModel.hasPart>*
[]< Information about the packaging of the device, i.e. how the device is packaged.; (xsd)packaging:DeviceModel.packaging>*
[]< The version of the device or software.; (xsd)version:DeviceModel.version>*
[]< Safety characteristics of the device. Binding: device-safety (example, ); (xsd)safety:CodeableConcept>*
[]< Shelf Life and storage information.; (xsd)shelfLifeStorage:ProductShelfLife>*
[]< Language code for the human-readable text strings produced by the device (all supported).; (xsd)languageCode:CodeableConcept>*
[]< Static or essentially fixed characteristics or features of this kind of device that are otherwise not captured in more specific attributes, e.g., time or timing attributes, resolution, accuracy, and physical attributes. Dynamic or current properties, such as settings, of an individual device are described using a Device instance-specific DeviceMetric and recorded using Observation. Static characteristics of an individual device could also be documented in a [Device] instance. The Device instance's properties, and their values, could be, but need not be, the same as in the associated DeviceDefinition.; (xsd)property:DeviceModel.property>*
< An organization that is responsible for the provision and ongoing maintenance of the device.; (xsd)owner:Organization*>?
[]< Contact details for an organization or a particular human that is responsible for the device. used for troubleshooting etc.; (xsd)contact:ContactPoint>*
[]< An associated device, attached to, used with, communicating with or linking a previous or new device model to the focal device.; (xsd)link:DeviceModel.link>*
[]< Descriptive information, usage information or implantation information that is not captured in an existing element.; (xsd)note:Annotation>*
[]< A substance used to create the material(s) of which the device is made.; (xsd)material:DeviceModel.material>*
[]< Indicates the production identifier(s) that are expected to appear in the UDI carrier on the device label. Binding: device-productidentifierinudi (required, The production identifier(s) that are expected to appear in the UDI carrier.); (xsd)productionIdentifierInUDI:code>*
< Information aimed at providing directions for the usage of this model of device. For more structured data, a ClinicalUseDefinition that points to the DeviceDefinition can be used.; (xsd)guideline:DeviceModel.guideline>?
< Tracking of latest field safety corrective action.; (xsd)correctiveAction:DeviceModel.correctiveAction>?
[]< Billing code or reference associated with the device.; (xsd)chargeItem:DeviceModel.chargeItem>*
[]< This extension to PlanDefinition, MedicationKnowledge and DeviceDefinition conveys the reference to a catalog containing the extended resource; (xsd)CatalogReference>*
[]< Global Medical Device Nomenclature classification In this element various classifications can be used, such as GMDN, EMDN, SNOMED CT, risk classes, national product codes.; (xsd)gmdn:DeviceModel.gmdn>*
< Systematized nomenclature of medicine - clinical terms In this element various classifications can be used, such as GMDN, EMDN, SNOMED CT, risk classes, national product codes.; (xsd)snomed:DeviceModel.snomed>?
< European Medical Device Nomenclature In this element various classifications can be used, such as GMDN, EMDN, SNOMED CT, risk classes, national product codes.; (xsd)emdn:DeviceModel.emdn>?🔗 What kind of device or device system this is. In this element various classifications can be used, such as GMDN, EMDN, SNOMED CT, risk classes, national product codes.DeviceModel.classification(xsd)(doc)=
<#base:DeviceDefinition.classification>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A classification or risk class of the device model. Binding: device-type (example, Type of device e.g. according to official classification.); (xsd)type:CodeableConcept>
[]< Further information qualifying this classification of the device model.; (xsd)justification:RelatedArtifact>*🔗 Identifies the standards, specifications, or formal guidances for the capabilities supported by the device. The device may be certified as conformant to these specifications e.g., communication, performance, process, measurement, or specialization standards.DeviceModel.conformsTo(xsd)(doc)=
<#base:DeviceDefinition.conformsTo>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Describes the type of the standard, specification, or formal guidance. Binding: device-specification-category (example, ); (xsd)category:CodeableConcept>?
< Code that identifies the specific standard, specification, protocol, formal guidance, regulation, legislation, or certification scheme to which the device adheres. Binding: device-specification-type (example, ); (xsd)specification:CodeableConcept>
[]< Identifies the specific form or variant of the standard, specification, or formal guidance. This may be a 'version number', release, document edition, publication year, or other label.; (xsd)version:string>*
[]< Standard, regulation, certification, or guidance website, document, or other publication, or similar, supporting the conformance.; (xsd)source:RelatedArtifact>*🔗 Tracking of latest field safety corrective action.DeviceModel.correctiveAction(xsd)(doc)=
<#base:DeviceDefinition.correctiveAction>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Whether the last corrective action known for this device was a recall. When a field safety action has been initiated but not yet resulted in a recall, this element will be set to 'false'.; (xsd)recall:boolean>
< The scope of the corrective action - whether the action targeted all units of a given device model, or only a specific set of batches identified by lot numbers, or individually identified devices identified by the serial name. Binding: device-correctiveactionscope (required, The type or scope of the corrective action.); (xsd)scope:code>?
< Start and end dates of the corrective action.; (xsd)period:Period>🔗 The name or names of the device as given by the manufacturer.DeviceModel.deviceName(xsd)(doc)=
<#base:DeviceDefinition.deviceName>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A human-friendly name that is used to refer to the device - depending on the type, it can be the brand name, the common name or alias, or other.; (xsd)name:string>
< The type of deviceName.
RegisteredName | UserFriendlyName | PatientReportedName. Binding: device-nametype (required, The type of name the device is referred by.); (xsd)type:code>🔗 European Medical Device Nomenclature In this element various classifications can be used, such as GMDN, EMDN, SNOMED CT, risk classes, national product codes.DeviceModel.emdn(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A classification or risk class of the device model. Binding: device-type (example, Type of device e.g. according to official classification.); (xsd)type:DeviceModel.emdn.type>
[]< Further information qualifying this classification of the device model.; (xsd)justification:RelatedArtifact>*🔗 A classification or risk class of the device model. Binding: device-type (example, Type of device e.g. according to official classification.)DeviceModel.emdn.type(xsd)(doc)=
<#base:CodeableConcept>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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.; (xsd)coding:DeviceModel.emdn.type.coding>*
< 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.; (xsd)text:string>?🔗 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.DeviceModel.emdn.type.coding(xsd)(doc)=
<#base:Coding>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< 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 be an absolute reference to some definition that establishes the system clearly and unambiguously.; (xsd)system:uri>
< 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.; (xsd)version:string>?
< 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).; (xsd)code>?
< A representation of the meaning of the code in the system, following the rules of the system.; (xsd)display:string>?
< 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.; (xsd)userSelected:boolean>?🔗 Global Medical Device Nomenclature classification In this element various classifications can be used, such as GMDN, EMDN, SNOMED CT, risk classes, national product codes.DeviceModel.gmdn(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A classification or risk class of the device model. Binding: device-type (example, Type of device e.g. according to official classification.); (xsd)type:DeviceModel.gmdn.type>
[]< Further information qualifying this classification of the device model.; (xsd)justification:RelatedArtifact>*🔗 A classification or risk class of the device model. Binding: device-type (example, Type of device e.g. according to official classification.)DeviceModel.gmdn.type(xsd)(doc)=
<#base:CodeableConcept>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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.; (xsd)coding:DeviceModel.gmdn.type.coding>*
< 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.; (xsd)text:string>?🔗 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.DeviceModel.gmdn.type.coding(xsd)(doc)=
<#base:Coding>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< 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 be an absolute reference to some definition that establishes the system clearly and unambiguously.; (xsd)system:uri>
< 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.; (xsd)version:string>?
< 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).; (xsd)code>?
< A representation of the meaning of the code in the system, following the rules of the system.; (xsd)display:string>?
< 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.; (xsd)userSelected:boolean>?🔗 Information aimed at providing directions for the usage of this model of device. For more structured data, a ClinicalUseDefinition that points to the DeviceDefinition can be used.DeviceModel.guideline(xsd)(doc)=
<#base:DeviceDefinition.guideline>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< The circumstances that form the setting for using the device.; (xsd)useContext:UsageContext>*
< Detailed written and visual directions for the user on how to use the device.; (xsd)usageInstruction:markdown>?
[]< A source of information or reference for this guideline.; (xsd)relatedArtifact:RelatedArtifact>*
[]< A clinical condition for which the device was designed to be used. A ClinicalUseDefinition that points to the DeviceDefinition can be used if more structured data is needed.; (xsd)indication:CodeableConcept>*
[]< A specific situation when a device should not be used because it may cause harm. A ClinicalUseDefinition that points to the DeviceDefinition can be used if more structured data is needed.; (xsd)contraindication:CodeableConcept>*
[]< Specific hazard alert information that a user needs to know before using the device. A ClinicalUseDefinition that points to the DeviceDefinition can be used if more structured data is needed.; (xsd)warning:CodeableConcept>*
< A description of the general purpose or medical use of the device or its function.; (xsd)intendedUse:string>?🔗 A device that is part (for example a component) of the present device.DeviceModel.hasPart(xsd)(doc)=
<#base:DeviceDefinition.hasPart>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Reference to the device that is part of the current device.; (xsd)reference:DeviceDefinition*>
< Number of instances of the component device in the current device.; (xsd)count:integer>?🔗 Billing code or reference associated with the device.DeviceModel.chargeItem(xsd)(doc)=
<#base:DeviceDefinition.chargeItem>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The code or reference for the charge item.; (xsd)chargeItemCode:ChargeItemDefinition*>
< Coefficient applicable to the billing code.; (xsd)count:Quantity>
< A specific time period in which this charge item applies.; (xsd)effectivePeriod:Period>?
[]< The context to which this charge item applies.; (xsd)useContext:UsageContext>*🔗 An associated device, attached to, used with, communicating with or linking a previous or new device model to the focal device.DeviceModel.link(xsd)(doc)=
<#base:DeviceDefinition.link>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type indicates the relationship of the related device to the device instance. Binding: devicedefinition-relationtype (extensible, The type of relation between this and the linked device.); (xsd)relation:Coding>
< A reference to the linked device.; (xsd)relatedDevice:DeviceDefinition*>🔗 A substance used to create the material(s) of which the device is made.DeviceModel.material(xsd)(doc)=
<#base:DeviceDefinition.material>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A substance that the device contains, may contain, or is made of - for example latex - to be used to determine patient compatibility. This is not intended to represent the composition of the device, only the clinically relevant materials.; (xsd)substance:CodeableConcept>
< Indicates an alternative material of the device.; (xsd)alternate:boolean>?
< Whether the substance is a known or suspected allergen.; (xsd)allergenicIndicator:boolean>?🔗 Information about the packaging of the device, i.e. how the device is packaged.DeviceModel.packaging(xsd)(doc)=
<#base:DeviceDefinition.packaging>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The business identifier of the packaged medication.; (xsd)identifier:Identifier>?
< A code that defines the specific type of packaging.; (xsd)type:CodeableConcept>?
< The number of items contained in the package (devices or sub-packages).; (xsd)count:integer>?
[]< An organization that distributes the packaged device.; (xsd)distributor:DeviceModel.packaging.distributor>*
[]< Unique Device Identifier (UDI) Barcode string on the packaging.; (xsd)udiDeviceIdentifier:DeviceModel.packaging.udiDeviceIdentifier>*
[]< Allows packages within packages.; (xsd)packaging:DeviceDefinition.packaging>*🔗 An organization that distributes the packaged device.DeviceModel.packaging.distributor(xsd)(doc)=
<#base:DeviceDefinition.packaging.distributor>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Distributor's human-readable name.; (xsd)name:string>?
[]< Distributor as an Organization resource.; (xsd)organizationReference:Organization*>*🔗 Unique Device Identifier (UDI) Barcode string on the packaging.DeviceModel.packaging.udiDeviceIdentifier(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The identifier that is to be associated with every Device that references this DeviceDefintiion for the issuer and jurisdiction provided in the DeviceDefinition.udiDeviceIdentifier.; (xsd)deviceIdentifier:string>
< Organization accredited by the jurisdictional authority to operate a system for the issuance of UDIs. Main issuers referenced in the US and/or in EU include:
1. GS1 GTIN: urn:oid:1.3.160,
2. HIBCC: urn:oid:2.16.840.1.113883.6.40,
3. ICCBBA Information Standard for Blood and Transplant (ISBT) 128: urn:oid:2.16.840.1.113883.6.18,
4. ICCBBA for other devices: to be found,
5. IFA (Europe Union only): to be found; (xsd)issuer:uri>
< The jurisdiction to which the deviceIdentifier applies.; (xsd)jurisdiction:uri>
[]< Indicates where and when the device is available on the market.; (xsd)marketDistribution:DeviceModel.packaging.udiDeviceIdentifier.marketDistribution>*🔗 Indicates where and when the device is available on the market.DeviceModel.packaging.udiDeviceIdentifier.marketDistribution(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Begin and end dates for the commercial distribution of the device.; (xsd)marketPeriod:DeviceModel.packaging.udiDeviceIdentifier.marketDistribution.marketPeriod>
< National state or territory to which the marketDistribution recers, typically where the device is commercialized.; (xsd)subJurisdiction:uri>🔗 Begin and end dates for the commercial distribution of the device.DeviceModel.packaging.udiDeviceIdentifier.marketDistribution.marketPeriod(xsd)(doc)=
<#base:Period>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The start of the period. The boundary is inclusive. If the low element is missing, the meaning is that the low boundary is not known.; (xsd)start:dateTime>?
< The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. The end value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.; (xsd)end:dateTime>?🔗 Static or essentially fixed characteristics or features of this kind of device that are otherwise not captured in more specific attributes, e.g., time or timing attributes, resolution, accuracy, and physical attributes. Dynamic or current properties, such as settings, of an individual device are described using a Device instance-specific DeviceMetric and recorded using Observation. Static characteristics of an individual device could also be documented in a [Device] instance. The Device instance's properties, and their values, could be, but need not be, the same as in the associated DeviceDefinition.DeviceModel.property(xsd)(doc)=
<#base:DeviceDefinition.property>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Code that specifies the property such as a resolution or color being represented. Binding: device-property-type (example, Device property type.); (xsd)type:CodeableConcept>
(<valueAttachment:Attachment>
|<valueBoolean:boolean>
|<valueCodeableConcept:CodeableConcept>
|<valueInteger:integer>
|<valueQuantity:Quantity>
|<valueRange:Range>
|<valueString:string>)🔗 Identifier associated with the regulatory documentation (certificates, technical documentation, post-market surveillance documentation and reports) of a set of device models sharing the same intended purpose, risk class and essential design and manufacturing characteristics. One example is the Basic UDI-DI in Europe. This should not be used for regulatory authorization numbers which are to be captured elsewhere.DeviceModel.regulatoryIdentifier(xsd)(doc)=
<#base:DeviceDefinition.regulatoryIdentifier>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type of identifier itself. Binding: devicedefinition-regulatory-identifier-type (required, Device regulatory identifier type.); (xsd)type:code>
< The identifier itself.; (xsd)deviceIdentifier:string>
< The organization that issued this identifier.; (xsd)issuer:uri>
< The jurisdiction to which the deviceIdentifier applies.; (xsd)jurisdiction:uri>🔗 Systematized nomenclature of medicine - clinical terms In this element various classifications can be used, such as GMDN, EMDN, SNOMED CT, risk classes, national product codes.DeviceModel.snomed(xsd)(doc)=
<#base:BackboneElement>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A classification or risk class of the device model. Binding: device-type (example, Type of device e.g. according to official classification.); (xsd)type:DeviceModel.snomed.type>
[]< Further information qualifying this classification of the device model.; (xsd)justification:RelatedArtifact>*🔗 A classification or risk class of the device model. Binding: device-type (example, Type of device e.g. according to official classification.)DeviceModel.snomed.type(xsd)(doc)=
<#base:CodeableConcept>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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.; (xsd)coding:DeviceModel.snomed.type.coding>*
< 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.; (xsd)text:string>?🔗 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.DeviceModel.snomed.type.coding(xsd)(doc)=
<#base:Coding>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< 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 be an absolute reference to some definition that establishes the system clearly and unambiguously.; (xsd)system:uri>
< 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.; (xsd)version:string>?
< 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).; (xsd)code>?
< A representation of the meaning of the code in the system, following the rules of the system.; (xsd)display:string>?
< 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.; (xsd)userSelected:boolean>?🔗 Unique device identifier (UDI) assigned to device label or package. Note that the Device may include multiple udiCarriers as it either may include just the udiCarrier for the jurisdiction it is sold, or for multiple jurisdictions it could have been sold.DeviceModel.udiDeviceIdentifier(xsd)(doc)=
<#base:DeviceDefinition.udiDeviceIdentifier>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The identifier that is to be associated with every Device that references this DeviceDefintiion for the issuer and jurisdiction provided in the DeviceDefinition.udiDeviceIdentifier.; (xsd)deviceIdentifier:string>
< Organization accredited by the jurisdictional authority to operate a system for the issuance of UDIs. Main issuers referenced in the US and/or in EU include:
1. GS1 GTIN: urn:oid:1.3.160,
2. HIBCC: urn:oid:2.16.840.1.113883.6.40,
3. ICCBBA Information Standard for Blood and Transplant (ISBT) 128: urn:oid:2.16.840.1.113883.6.18,
4. ICCBBA for other devices: to be found,
5. IFA (Europe Union only): to be found; (xsd)issuer:uri>
< The jurisdiction to which the deviceIdentifier applies. Known jurisdictions are:
1. US Food & Drug Administration (FDA): urn:oid:2.16.840.1.113883.3.150,
2. Europe Union EUDAMED: https://ec.europa.eu/health/medical-devices-sector_en; (xsd)jurisdiction:uri>
[]< Indicates where and when the device is available on the market.; (xsd)marketDistribution:DeviceModel.udiDeviceIdentifier.marketDistribution>*🔗 Indicates where and when the device is available on the market.DeviceModel.udiDeviceIdentifier.marketDistribution(xsd)(doc)=
<#base:DeviceDefinition.udiDeviceIdentifier.marketDistribution>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Begin and end dates for the commercial distribution of the device.; (xsd)marketPeriod:DeviceModel.udiDeviceIdentifier.marketDistribution.marketPeriod>
< National state or territory to which the marketDistribution recers, typically where the device is commercialized.; (xsd)subJurisdiction:uri>🔗 Begin and end dates for the commercial distribution of the device.DeviceModel.udiDeviceIdentifier.marketDistribution.marketPeriod(xsd)(doc)=
<#base:Period>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The start of the period. The boundary is inclusive. If the low element is missing, the meaning is that the low boundary is not known.; (xsd)start:dateTime>?
< The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. The end value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.; (xsd)end:dateTime>?🔗 The version of the device or software.DeviceModel.version(xsd)(doc)=
<#base:DeviceDefinition.version>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type of the device version, e.g. manufacturer, approved, internal.; (xsd)type:CodeableConcept>?
< The hardware or software module of the device to which the version applies. Note that the module of the device would not need to be tracked as a separate device, e.g., using different UDI, thus would typically involve one or more software modules. For example, a device may involve two software modules each on a different version.; (xsd)component:Identifier>?
< The version text.; (xsd)value:string>🔗 Information about a medication that is used to support knowledge.DrugKnowledge(xsd)(doc)=
<#base:MedicationKnowledge>
< The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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 its narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
< 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). Binding: all-languages (required, IETF language tag for a human language); (xsd)language:code>?
< 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 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.; (xsd)text:Narrative>?
[]< 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. 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.; (xsd)contained:Resource>*
[]< An Extension; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Business identifier for this medication. This is a business identifier, not a resource identifier (see discussion).; (xsd)identifier:Identifier>*
< A code that specifies this medication, or a textual description if no code is available. Usage note: This could be a standard medication code such as a code from RxNorm, SNOMED CT, IDMP etc. It could also be a national or local formulary code, optionally with translations to other code systems. Depending on the context of use, the code that was actually selected by the user (prescriber, dispenser, etc.) will have the coding.userSelected set to true. As described in the coding datatype: "A coding may be marked as a "userSelected" if a user selected the particular coded value in a user interface (e.g. the user selects an item in a pick-list). If a user selected coding exists, it is the preferred choice for performing translations etc. Other codes can only be literal translations to alternative code systems, or codes at a lower level of granularity (e.g. a generic code for a vendor-specific primary one). Binding: medication-codes (example, A coded concept that defines the type of a medication.); (xsd)code:CodeableConcept>
< A code to indicate if the medication referred to by this MedicationKnowledge is in active use within the drug database or inventory system. The status refers to the validity about the information of the medication and not to its medicinal properties. This status is intended to identify if the medication in a local system is in active use within a drug database or inventory. For example, a pharmacy system may create a new drug file record for a compounded product "ABC Hospital Special Cream" with an active status. At some point in the future, it may be determined that the drug record was created with an error and the status is changed to "entered in error". This status is not intended to specify if a medication is part of a particular formulary. It is possible that the drug record may be referenced by multiple formularies or catalogues and each of those entries would have a separate status. Binding: medicationknowledge-status (required, A coded concept defining if the medication is in active use.); (xsd)status:code>?
< The creator or owner of the knowledge or information about the medication.; (xsd)author:Organization*>?
[]< Lists the jurisdictions that this medication knowledge was written for. The codes could have varying granularity from a country or group of countries down to a specific district.; (xsd)intendedJurisdiction:CodeableConcept>*
[]< All of the names for a medication, for example, the name(s) given to a medication in different countries. For example, acetaminophen and paracetamol or salbutamol and albuterol.; (xsd)name:string>*
[]< Associated or related medications. For example, if the medication is a branded product (e.g. Crestor), this is the Therapeutic Moeity (e.g. Rosuvastatin) or if this is a generic medication (e.g. Rosuvastatin), this would link to a branded product (e.g. Crestor.; (xsd)relatedMedicationKnowledge:DrugKnowledge.relatedMedicationKnowledge>*
[]< Links to associated medications that could be prescribed, dispensed or administered.; (xsd)associatedMedication:Medication*>*
[]< Category of the medication or product (e.g. branded product, therapeutic moeity, generic product, innovator product, etc.).; (xsd)productType:CodeableConcept>*
[]< Associated documentation about the medication.; (xsd)monograph:DrugKnowledge.monograph>*
< The instructions for preparing the medication.; (xsd)preparationInstruction:markdown>?
[]< The price of the medication.; (xsd)cost:DrugKnowledge.cost>*
[]< The program under which the medication is reviewed.; (xsd)monitoringProgram:DrugKnowledge.monitoringProgram>*
[]< Guidelines or protocols that are applicable for the administration of the medication based on indication.; (xsd)indicationGuideline:DrugKnowledge.indicationGuideline>*
[]< Categorization of the medication within a formulary or classification system.; (xsd)medicineClassification:DrugKnowledge.medicineClassification>*
[]< Information that only applies to packages (not products).; (xsd)packaging:DrugKnowledge.packaging>*
[]< Potential clinical issue with or between medication(s) (for example, drug-drug interaction, drug-disease contraindication, drug-allergy interaction, etc.).; (xsd)clinicalUseIssue:ClinicalUseDefinition*>*
[]< Information on how the medication should be stored, for example, refrigeration temperatures and length of stability at a given temperature.; (xsd)storageGuideline:DrugKnowledge.storageGuideline>*
[]< Regulatory information about a medication.; (xsd)regulatory:DrugKnowledge.regulatory>*
< Along with the link to a Medicinal Product Definition resource, this information provides common definitional elements that are needed to understand the specific medication that is being described.; (xsd)definitional:DrugKnowledge.definitional>?
[]< This extension to PlanDefinition, MedicationKnowledge and DeviceDefinition conveys the reference to a catalog containing the extended resource; (xsd)CatalogReference>*🔗 The price of the medication.DrugKnowledge.cost(xsd)(doc)=
<#base:MedicationKnowledge.cost>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< The date range for which the cost information of the medication is effective.; (xsd)effectiveDate:Period>*
< The category of the cost information. For example, manufacturers' cost, patient cost, claim reimbursement cost, actual acquisition cost.; (xsd)type:CodeableConcept>
< The source or owner that assigns the price to the medication.; (xsd)source:string>?
< The price or representation of the cost (for example, Band A, Band B or $, $$) of the medication. Binding: medication-cost-category (example, A coded concept defining the category of a medication.); (xsd)cost:(<CodeableConcept>
|<Money>)>🔗 Along with the link to a Medicinal Product Definition resource, this information provides common definitional elements that are needed to understand the specific medication that is being described.DrugKnowledge.definitional(xsd)(doc)=
<#base:MedicationKnowledge.definitional>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Associated definitions for this medication.; (xsd)definition:MedicinalProductDefinition*>*
< Describes the form of the item. Powder; tablets; capsule. When Medication is referenced from MedicationRequest, this is the ordered form. When Medication is referenced within MedicationDispense, this is the dispensed form. When Medication is referenced within MedicationAdministration, this is administered form. Binding: medication-form-codes (example, ); (xsd)doseForm:CodeableConcept>?
[]< The intended or approved route of administration. Binding: route-codes (example, ); (xsd)intendedRoute:CodeableConcept>*
[]< Identifies a particular constituent of interest in the product.; (xsd)ingredient:DrugKnowledge.definitional.ingredient>*
[]< Specifies descriptive properties of the medicine, such as color, shape, imprints, etc.; (xsd)drugCharacteristic:DrugKnowledge.definitional.drugCharacteristic>*🔗 Specifies descriptive properties of the medicine, such as color, shape, imprints, etc.DrugKnowledge.definitional.drugCharacteristic(xsd)(doc)=
<#base:MedicationKnowledge.definitional.drugCharacteristic>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A code specifying which characteristic of the medicine is being described (for example, colour, shape, imprint). Binding: medicationknowledge-characteristic (example, ); (xsd)type:CodeableConcept>?
(<valueAttachment:Attachment>
|<valueBase64Binary:base64Binary>
|<valueCodeableConcept:CodeableConcept>
|<valueSimpleQuantity:SimpleQuantity>
|<valueString:string>)🔗 Identifies a particular constituent of interest in the product.DrugKnowledge.definitional.ingredient(xsd)(doc)=
<#base:MedicationKnowledge.definitional.ingredient>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A reference to the resource that provides information about the ingredient.; (xsd)item:Substance*>
< Indication of whether this ingredient affects the therapeutic action of the drug. Binding: http://terminology.hl7.org/ValueSet/v3-RoleClassIngredientEntity (example, ); (xsd)type:CodeableConcept>?
< Specifies how many (or how much) of the items there are in this Medication. For example, 250 mg per tablet. This is expressed as a ratio where the numerator is 250mg and the denominator is 1 tablet but can also be expressed a quantity when the denominator is assumed to be 1 tablet. Binding: medication-ingredientstrength (example, ); (xsd)strength:(<CodeableConcept>
|<Quantity>
|<Ratio>)>?🔗 Guidelines or protocols that are applicable for the administration of the medication based on indication.DrugKnowledge.indicationGuideline(xsd)(doc)=
<#base:MedicationKnowledge.indicationGuideline>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Indication or reason for use of the medication that applies to the specific administration guideline.; (xsd)indication:ClinicalUseDefinition*>*
[]< The guidelines for the dosage of the medication for the indication.; (xsd)dosingGuideline:DrugKnowledge.indicationGuideline.dosingGuideline>*🔗 The guidelines for the dosage of the medication for the indication.DrugKnowledge.indicationGuideline.dosingGuideline(xsd)(doc)=
<#base:MedicationKnowledge.indicationGuideline.dosingGuideline>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The overall intention of the treatment, for example, prophylactic, supporative, curative, etc.; (xsd)treatmentIntent:CodeableConcept>?
[]< Dosage for the medication for the specific guidelines.; (xsd)dosage:DrugKnowledge.indicationGuideline.dosingGuideline.dosage>*
< The type of the treatment that the guideline applies to, for example, long term therapy, first line treatment, etc.; (xsd)administrationTreatment:CodeableConcept>?
[]< Characteristics of the patient that are relevant to the administration guidelines (for example, height, weight, gender, etc.).; (xsd)patientCharacteristic:DrugKnowledge.indicationGuideline.dosingGuideline.patientCharacteristic>*🔗 Dosage for the medication for the specific guidelines.DrugKnowledge.indicationGuideline.dosingGuideline.dosage(xsd)(doc)=
<#base:MedicationKnowledge.indicationGuideline.dosingGuideline.dosage>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type or category of dosage for a given medication (for example, prophylaxis, maintenance, therapeutic, etc.).; (xsd)type:CodeableConcept>
[]< Dosage for the medication for the specific guidelines.; (xsd)dosage:Dosage>+🔗 Characteristics of the patient that are relevant to the administration guidelines (for example, height, weight, gender, etc.).DrugKnowledge.indicationGuideline.dosingGuideline.patientCharacteristic(xsd)(doc)=
<#base:MedicationKnowledge.indicationGuideline.dosingGuideline.patientCharacteristic>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The categorization of the specific characteristic that is relevant to the administration guideline (e.g. height, weight, gender).; (xsd)type:CodeableConcept>
(<valueCodeableConcept:CodeableConcept>
|<valueQuantity:Quantity>
|<valueRange:Range>)?🔗 Categorization of the medication within a formulary or classification system.DrugKnowledge.medicineClassification(xsd)(doc)=
<#base:MedicationKnowledge.medicineClassification>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type of category for the medication (for example, therapeutic classification, therapeutic sub-classification).; (xsd)type:CodeableConcept>
< Either a textual source of the classification or a reference to an online source.; (xsd)source:(<string>
|<uri>)>?
[]< Specific category assigned to the medication (e.g. anti-infective, anti-hypertensive, antibiotic, etc.).; (xsd)classification:CodeableConcept>*🔗 The program under which the medication is reviewed.DrugKnowledge.monitoringProgram(xsd)(doc)=
<#base:MedicationKnowledge.monitoringProgram>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Type of program under which the medication is monitored.; (xsd)type:CodeableConcept>?
< Name of the reviewing program.; (xsd)name:string>?🔗 Associated documentation about the medication.DrugKnowledge.monograph(xsd)(doc)=
<#base:MedicationKnowledge.monograph>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The category of documentation about the medication. (e.g. professional monograph, patient education monograph).; (xsd)type:CodeableConcept>?
< Associated documentation about the medication.; (xsd)source:DocumentReference*>?🔗 Information that only applies to packages (not products).DrugKnowledge.packaging(xsd)(doc)=
<#base:MedicationKnowledge.packaging>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< The cost of the packaged medication.; (xsd)cost:MedicationKnowledge.cost>*
< A reference to a PackagedProductDefinition that provides the details of the product that is in the packaging and is being priced.; (xsd)packagedProduct:PackagedProductDefinition*>?🔗 Regulatory information about a medication.DrugKnowledge.regulatory(xsd)(doc)=
<#base:MedicationKnowledge.regulatory>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The authority that is specifying the regulations.; (xsd)regulatoryAuthority:Organization*>
[]< Specifies if changes are allowed when dispensing a medication from a regulatory perspective.; (xsd)substitution:DrugKnowledge.regulatory.substitution>*
[]< Specifies the schedule of a medication in jurisdiction.; (xsd)schedule:CodeableConcept>*
< The maximum number of units of the medication that can be dispensed in a period.; (xsd)maxDispense:DrugKnowledge.regulatory.maxDispense>?🔗 The maximum number of units of the medication that can be dispensed in a period.DrugKnowledge.regulatory.maxDispense(xsd)(doc)=
<#base:MedicationKnowledge.regulatory.maxDispense>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The maximum number of units of the medication that can be dispensed.; (xsd)quantity:SimpleQuantity>
< The period that applies to the maximum number of units.; (xsd)period:Duration>?🔗 Specifies if changes are allowed when dispensing a medication from a regulatory perspective.DrugKnowledge.regulatory.substitution(xsd)(doc)=
<#base:MedicationKnowledge.regulatory.substitution>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Specifies the type of substitution allowed.; (xsd)type:CodeableConcept>
< Specifies if regulation allows for changes in the medication when dispensing.; (xsd)allowed:boolean>🔗 Associated or related medications. For example, if the medication is a branded product (e.g. Crestor), this is the Therapeutic Moeity (e.g. Rosuvastatin) or if this is a generic medication (e.g. Rosuvastatin), this would link to a branded product (e.g. Crestor.DrugKnowledge.relatedMedicationKnowledge(xsd)(doc)=
<#base:MedicationKnowledge.relatedMedicationKnowledge>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The category of the associated medication knowledge reference.; (xsd)type:CodeableConcept>
[]< Associated documentation about the associated medication knowledge.; (xsd)reference:MedicationKnowledge*>+🔗 Information on how the medication should be stored, for example, refrigeration temperatures and length of stability at a given temperature.DrugKnowledge.storageGuideline(xsd)(doc)=
<#base:MedicationKnowledge.storageGuideline>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Reference to additional information about the storage guidelines.; (xsd)reference:uri>?
[]< Additional notes about the storage.; (xsd)note:Annotation>*
< Duration that the medication remains stable if the environmentalSetting is respected.; (xsd)stabilityDuration:Duration>?
[]< Describes a setting/value on the environment for the adequate storage of the medication and other substances. Environment settings may involve temperature, humidity, or exposure to light.; (xsd)environmentalSetting:DrugKnowledge.storageGuideline.environmentalSetting>*🔗 Describes a setting/value on the environment for the adequate storage of the medication and other substances. Environment settings may involve temperature, humidity, or exposure to light.DrugKnowledge.storageGuideline.environmentalSetting(xsd)(doc)=
<#base:MedicationKnowledge.storageGuideline.environmentalSetting>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Identifies the category or type of setting (e.g., type of location, temperature, humidity).; (xsd)type:CodeableConcept>
(<valueCodeableConcept:CodeableConcept>
|<valueQuantity:Quantity>
|<valueRange:Range>)🔗 A medically related item or items, in a container or package.DrugPackage(xsd)(doc)=
<#base:PackagedProductDefinition>
< The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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 its narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
< 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). Binding: all-languages (required, IETF language tag for a human language); (xsd)language:code>?
< 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 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.; (xsd)text:Narrative>?
[]< 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. 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.; (xsd)contained:Resource>*
[]< May be used to represent additional information that is not part of the basic definition of the resource. 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A unique identifier for this package as whole - not the the content of the package. Unique instance identifiers assigned to a package by manufacturers, regulators, drug catalogue custodians or other organizations.; (xsd)identifier:Identifier>*
< A name for this package. Typically what it would be listed as in a drug formulary or catalogue, inventory etc.; (xsd)name:string>?
< A high level category e.g. medicinal product, raw material, shipping/transport container, etc. Binding: package-type (example, A high level categorisation of a package.); (xsd)type:CodeableConcept>
[]< The product this package model relates to, not the contents of the package (for which see package.containedItem).; (xsd)packageFor:MedicinalProductDefinition*>*
< The status within the lifecycle of this item. A high level status, this is not intended to duplicate details carried elsewhere such as legal status, or authorization or marketing status. Binding: publication-status (preferred, The lifecycle status of an artifact.); (xsd)status:CodeableConcept>?
< The date at which the given status became applicable.; (xsd)statusDate:dateTime>?
[]< A total of the complete count of contained items of a particular type/form, independent of sub-packaging or organization. This can be considered as the pack size. This attribute differs from containedItem.amount in that it can give a single aggregated count of all tablet types in a pack, even when these are different manufactured items. For example a pill pack of 21 tablets plus 7 sugar tablets, can be denoted here as '28 tablets'. This attribute is repeatable so that the different item types in one pack type can be counted (e.g. a count of vials and count of syringes). Each repeat must have different units, so that it is clear what the different sets of counted items are, and it is not intended to allow different counts of similar items (e.g. not '2 tubes and 3 tubes'). Repeats are not to be used to represent different pack sizes (e.g. 20 pack vs. 50 pack) - which would be different instances of this resource.; (xsd)containedItemQuantity:Quantity>*
< Textual description. Note that this is not the name of the package or product.; (xsd)description:markdown>?
[]< The legal status of supply of the packaged item as classified by the regulator.; (xsd)legalStatusOfSupply:DrugPackage.legalStatusOfSupply>*
[]< Allows specifying that an item is on the market for sale, or that it is not available, and the dates and locations associated.; (xsd)marketingStatus:MarketingStatus>*
< Identifies if the package contains different items, such as when a drug product is supplied with another item e.g. a diluent or adjuvant.; (xsd)copackagedIndicator:boolean>?
[]< Manufacturer of this package type. When there are multiple it means these are all possible manufacturers.; (xsd)manufacturer:Organization*>*
[]< Additional information or supporting documentation about the packaged product.; (xsd)attachedDocument:DocumentReference*>*
< A packaging item, as a container for medically related items, possibly with other packaging items within, or a packaging component, such as bottle cap (which is not a device or a medication manufactured item).; (xsd)packaging:DrugPackage.packaging>?
[]< Allows the key features to be recorded, such as "hospital pack", "nurse prescribable", "calendar pack".; (xsd)characteristic:PackagedProductDefinition.packaging.property>*🔗 The legal status of supply of the packaged item as classified by the regulator.DrugPackage.legalStatusOfSupply(xsd)(doc)=
<#base:PackagedProductDefinition.legalStatusOfSupply>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The actual status of supply. Conveys in what situation this package type may be supplied for use. Binding: legal-status-of-supply (example, The prescription supply types appropriate to a medicinal product); (xsd)code:CodeableConcept>?
< The place where the legal status of supply applies. When not specified, this indicates it is unknown in this context. Binding: jurisdiction (example, Jurisdiction codes); (xsd)jurisdiction:CodeableConcept>?🔗 A packaging item, as a container for medically related items, possibly with other packaging items within, or a packaging component, such as bottle cap (which is not a device or a medication manufactured item).DrugPackage.packaging(xsd)(doc)=
<#base:PackagedProductDefinition.packaging>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A business identifier that is specific to this particular part of the packaging, often assigned by the manufacturer. Including possibly Data Carrier Identifier (a GS1 barcode).; (xsd)identifier:Identifier>*
< The physical type of the container of the items. Binding: packaging-type (example, A high level categorisation of a package.); (xsd)type:CodeableConcept>?
< Is this a part of the packaging (e.g. a cap or bottle stopper), rather than the packaging itself (e.g. a bottle or vial). The latter type are designed be a container, but the former are not.; (xsd)componentPart:boolean>?
< The quantity of packaging items contained at this layer of the package. This does not relate to the number of contained items but relates solely to the number of packaging items. When looking at the outermost layer it is always 1. If there are two boxes within, at the next layer it would be 2.; (xsd)quantity:integer>?
[]< Material type of the package item. Binding: package-material (example, A material used in the construction of packages and their components.); (xsd)material:CodeableConcept>*
[]< A possible alternate material for this part of the packaging, that is allowed to be used instead of the usual material (e.g. different types of plastic for a blister sleeve). Binding: package-material (example, A material used in the construction of packages and their components.); (xsd)alternateMaterial:CodeableConcept>*
[]< Shelf Life and storage information.; (xsd)shelfLifeStorage:ProductShelfLife>*
[]< Manufacturer of this packaging item. When there are multiple values each one is a potential manufacturer of this packaging item.; (xsd)manufacturer:Organization*>*
[]< General characteristics of this item.; (xsd)property:DrugPackage.packaging.property>*
[]< The item(s) within the packaging.; (xsd)containedItem:DrugPackage.packaging.containedItem>*
[]< Allows containers (and parts of containers) within containers, still as a part of a single packaged product. See also PackagedProductDefinition.packaging.containedItem.item(PackagedProductDefinition).; (xsd)packaging:PackagedProductDefinition.packaging>*🔗 The item(s) within the packaging.DrugPackage.packaging.containedItem(xsd)(doc)=
<#base:PackagedProductDefinition.packaging.containedItem>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The actual item(s) of medication, as manufactured, or a device (typically, but not necessarily, a co-packaged one), or other medically related item (such as food, biologicals, raw materials, medical fluids, gases etc.), as contained in the package. This also allows another whole packaged product to be included, which is solely for the case where a package of other entire packages is wanted - such as a wholesale or distribution pack (for layers within one package, use PackagedProductDefinition.packaging.packaging).; (xsd)item:(<BiologicallyDerivedProduct>
|<DeviceDefinition>
|<ManufacturedItemDefinition>
|<NutritionProduct>
|<PackagedProductDefinition>)>
< The number of this type of item within this packaging or for continuous items such as liquids it is the quantity (for example 25ml). See also PackagedProductDefinition.containedItemQuantity (especially the long definition).; (xsd)amount:Quantity>?🔗 General characteristics of this item.DrugPackage.packaging.property(xsd)(doc)=
<#base:PackagedProductDefinition.packaging.property>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A code expressing the type of characteristic. Binding: product-characteristic-codes (example, This value set includes all observable entity codes from SNOMED CT - provided as an exemplar value set.); (xsd)type:CodeableConcept>
(<valueAttachment:Attachment>
|<valueBoolean:boolean>
|<valueCodeableConcept:CodeableConcept>
|<valueDate:date>
|<valueQuantity:Quantity>)?🔗 A single issue - either an indication, contraindication, interaction or an undesirable effect for a medicinal product, medication, device or procedure.IndicationDefinition(xsd)(doc)=
<#base:ClinicalUseDefinition>
< The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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 its narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
< 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). Binding: all-languages (required, IETF language tag for a human language); (xsd)language:code>?
< 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 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.; (xsd)text:Narrative>?
[]< 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. 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.; (xsd)contained:Resource>*
[]< May be used to represent additional information that is not part of the basic definition of the resource. 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Business identifier for this issue.; (xsd)identifier:Identifier>*
< indication | contraindication | interaction | undesirable-effect | warning. Binding: clinical-use-definition-type (required, Overall defining type of this clinical use definition.) indication; (xsd)type:code>
[]< A categorisation of the issue, primarily for dividing warnings into subject heading areas such as "Pregnancy and Lactation", "Overdose", "Effects on Ability to Drive and Use Machines". Binding: clinical-use-definition-category (preferred, A categorisation for a clinical use information item.); (xsd)category:CodeableConcept>*
[]< The medication, product, substance, device, procedure etc. for which this is an indication.; (xsd)subject:(<ActivityDefinition>
|<BiologicallyDerivedProduct>
|<Device>
|<DeviceDefinition>
|<Medication>
|<MedicinalProductDefinition>
|<NutritionProduct>
|<PlanDefinition>
|<Substance>)>*
< Whether this is a current issue or one that has been retired etc. Binding: publication-status (preferred, The lifecycle status of an artifact.); (xsd)status:CodeableConcept>?
< Specifics for when this is a contraindication.; (xsd)contraindication:IndicationDefinition.contraindication>{0,0}
< Specifics for when this is an indication.; (xsd)indication:IndicationDefinition.indication>
< Specifics for when this is an interaction.; (xsd)interaction:IndicationDefinition.interaction>{0,0}
[]< The population group to which this applies.; (xsd)population:Group*>*
[]< Logic used by the clinical use definition.; (xsd)library:Library*>*
< Describe the possible undesirable effects (negative outcomes) from the use of the medicinal product as treatment.; (xsd)undesirableEffect:IndicationDefinition.undesirableEffect>{0,0}
< A critical piece of information about environmental, health or physical risks or hazards that serve as caution to the user. For example 'Do not operate heavy machinery', 'May cause drowsiness', or 'Get medical advice/attention if you feel unwell'.; (xsd)warning:IndicationDefinition.warning>{0,0}🔗 Specifics for when this is a contraindication.IndicationDefinition.contraindication(xsd)(doc)=
<#base:ClinicalUseDefinition.contraindication>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The situation that is being documented as contraindicating against this item. Binding: disease-symptom-procedure (example, A symptom, disease or procedure.); (xsd)diseaseSymptomProcedure:ObservationDefinition*>?
< The status of the disease or symptom for the contraindication, for example "chronic" or "metastatic". Binding: disease-status (example, The status of a disease or symptom.); (xsd)diseaseStatus:ObservationDefinition*>?
[]< A comorbidity (concurrent condition) or coinfection. Binding: disease-symptom-procedure (example, A symptom, disease or procedure.); (xsd)comorbidity:ObservationDefinition*>*
[]< The indication which this is a contraidication for.; (xsd)indication:ClinicalUseDefinition*>*
< An expression that returns true or false, indicating whether the indication is applicable or not, after having applied its other elements. The expression may be inlined or may be a reference to a named expression within a logic library referenced by the library element.; (xsd)applicability:Expression>?
[]< Information about the use of the medicinal product in relation to other therapies described as part of the contraindication.; (xsd)otherTherapy:IndicationDefinition.contraindication.otherTherapy>*🔗 Information about the use of the medicinal product in relation to other therapies described as part of the contraindication.IndicationDefinition.contraindication.otherTherapy(xsd)(doc)=
<#base:ClinicalUseDefinition.contraindication.otherTherapy>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type of relationship between the medicinal product indication or contraindication and another therapy. Binding: therapy-relationship-type (preferred, Classification of relationship between a therapy and a contraindication or an indication.); (xsd)relationshipType:CodeableConcept>
< Reference to a specific medication (active substance, medicinal product or class of products, biological, food etc.) as part of an indication or contraindication. Binding: therapy (example, A therapy.); (xsd)treatment:(<ActivityDefinition>
|<BiologicallyDerivedProduct>
|<Medication>
|<MedicinalProductDefinition>
|<NutritionProduct>
|<Substance>
|<SubstanceDefinition>)>🔗 Specifics for when this is an indication.IndicationDefinition.indication(xsd)(doc)=
<#base:ClinicalUseDefinition.indication>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The situation that is being documented as an indicaton for this item. Binding: disease-symptom-procedure (example, A symptom, disease or procedure.); (xsd)diseaseSymptomProcedure:ObservationDefinition*>?
< The status of the disease or symptom for the indication, for example "chronic" or "metastatic". Binding: disease-status (example, The status of a disease or symptom.); (xsd)diseaseStatus:ObservationDefinition*>?
[]< A comorbidity (concurrent condition) or coinfection as part of the indication. Binding: disease-symptom-procedure (example, A symptom, disease or procedure.); (xsd)comorbidity:ObservationDefinition*>*
< The intended effect, aim or strategy to be achieved. Binding: product-intended-use (preferred, The overall intended use of a product.); (xsd)intendedEffect:ObservationDefinition*>?
< Timing or duration information, that may be associated with use with the indicated condition e.g. Adult patients suffering from myocardial infarction (from a few days until less than 35 days), ischaemic stroke (from 7 days until less than 6 months).; (xsd)duration:(<Range>
|<string>)>?
[]< An unwanted side effect or negative outcome that may happen if you use the drug (or other subject of this resource) for this indication.; (xsd)undesirableEffect:ClinicalUseDefinition*>*
< An expression that returns true or false, indicating whether the indication is applicable or not, after having applied its other elements. The expression may be inlined or may be a reference to a named expression within a logic library referenced by the library element.; (xsd)applicability:Expression>?
[]< Information about the use of the medicinal product in relation to other therapies described as part of the indication.; (xsd)otherTherapy:ClinicalUseDefinition.contraindication.otherTherapy>*🔗 Specifics for when this is an interaction.IndicationDefinition.interaction(xsd)(doc)=
<#base:ClinicalUseDefinition.interaction>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< The specific medication, product, food, substance etc. or laboratory test that interacts.; (xsd)interactant:IndicationDefinition.interaction.interactant>*
< The type of the interaction e.g. drug-drug interaction, drug-food interaction, drug-lab test interaction. Binding: interaction-type (example, A categorisation for an interaction between two substances.); (xsd)type:CodeableConcept>?
< The effect of the interaction, for example "reduced gastric absorption of primary medication". Binding: interaction-effect (example, A interaction effect of clinical use of a medication or other substance.); (xsd)effect:ObservationDefinition*>?
< The incidence of the interaction, e.g. theoretical, observed. Binding: interaction-incidence (example, A categorisation for incidence of occurence of an interaction.); (xsd)incidence:CodeableConcept>?
[]< Actions for managing the interaction. Binding: interaction-management (example, A type of management for an interaction of a medication or other substance.); (xsd)management:CodeableConcept>*🔗 The specific medication, product, food, substance etc. or laboratory test that interacts.IndicationDefinition.interaction.interactant(xsd)(doc)=
<#base:ClinicalUseDefinition.interaction.interactant>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The specific medication, product, food, substance etc. or laboratory test that interacts. Binding: interactant (example, An interactant - a substance that may have a clinically significant effect on another.); (xsd)item:(<BiologicallyDerivedProduct>
|<CodeableConcept>
|<Medication>
|<MedicinalProductDefinition>
|<NutritionProduct>
|<ObservationDefinition>
|<Substance>)>🔗 Describe the possible undesirable effects (negative outcomes) from the use of the medicinal product as treatment.IndicationDefinition.undesirableEffect(xsd)(doc)=
<#base:ClinicalUseDefinition.undesirableEffect>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The situation in which the undesirable effect may manifest. Binding: undesirable-effect-symptom (example, An undesirable effect of clinical use.); (xsd)symptomConditionEffect:ObservationDefinition*>?
< High level classification of the effect. Binding: undesirable-effect-classification (example, A categorisation for an undesirable effect.); (xsd)classification:CodeableConcept>?
< How often the effect is seen. Binding: undesirable-effect-frequency (example, A categorisation for a frequency of occurence of an undesirable effect.); (xsd)frequencyOfOccurrence:CodeableConcept>?🔗 A critical piece of information about environmental, health or physical risks or hazards that serve as caution to the user. For example 'Do not operate heavy machinery', 'May cause drowsiness', or 'Get medical advice/attention if you feel unwell'.IndicationDefinition.warning(xsd)(doc)=
<#base:ClinicalUseDefinition.warning>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A textual definition of this warning, with formatting.; (xsd)description:markdown>?
< A coded or unformatted textual definition of this warning. Binding: warning-type (example, Classification of warning type.); (xsd)code:CodeableConcept>?🔗 Set of definitional characteristics for a kind of observation or measurement produced or consumed by an orderable health care service. An instance of this resource informs the consumer of a health-related service (such as a lab diagnostic test or panel) about how the observations used or produced by this service will look like.InputObservationDefinition(xsd)(doc)=
<#base:ObservationDefinition>
< The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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 its narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
< 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). Binding: all-languages (required, IETF language tag for a human language); (xsd)language:code>?
< 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 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.; (xsd)text:Narrative>?
[]< 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. 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.; (xsd)contained:Resource>*
[]< May be used to represent additional information that is not part of the basic definition of the resource. 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< An absolute URL that is used to identify this ObservationDefinition when it is referenced in a specification, model, design or an instance. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this ObservationDefinition is (or will be) published. The URL SHOULD include the major version of the ObservationDefinition. For more information see Technical and Business Versions. Can be a urn:uuid: or a urn:oid:, but real http: addresses are preferred. This is the URI that will be used when making canonical references to this resource.; (xsd)url:uri>?
< Business identifiers assigned to this ObservationDefinition. by the performer and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server. This is a business identifier, not a resource identifier. It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types.; (xsd)identifier:Identifier>?
< The identifier that is used to identify this version of the ObservationDefinition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the ObservationDefinition 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 are orderable. There may be multiple different instances of an observationDefinition that have the same identifier but different versions.; (xsd)version:string>?
< Indicates the mechanism used to compare versions to determine which is more current. If set as a string, this is a FHIRPath expression that has two additional context variables passed in - %version1 and %version2 and will return a negative number if version1 is newer, a positive number if version2 and a 0 if the version ordering can't be successfully be determined. Binding: version-algorithm (extensible, ); (xsd)versionAlgorithm:(<Coding>
|<string>)>?
< A natural language name identifying the ObservationDefinition. 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.; (xsd)name:string>?
< A short, descriptive, user-friendly title for the ObservationDefinition.; (xsd)title:string>?
< The current state of the ObservationDefinition. A nominal state-transition diagram can be found in the [Definition pattern](http://hl7.org/fhir/R5/definition.html#statemachine) documentation
Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization). Binding: publication-status (required, Codes identifying the state of an ObservationDefinition.); (xsd)status:code>
< A flag to indicate that this ObservationDefinition is authored for testing purposes (or education/evaluation/marketing), and is not intended to be used for genuine usage. Allows filtering of ObservationDefinition that are appropriate for use vs. not.; (xsd)experimental:boolean>?
< The date (and optionally time) when the ObservationDefinition 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 ObservationDefinition changes. 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 ObservationDefinition. 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](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)date:dateTime>?
< Helps establish the "authority/credibility" of the ObservationDefinition. May also allow for contact.; (xsd)publisher:string>?
[]< 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.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)contact:ContactDetail>*
< A free text natural language description of the ObservationDefinition from the consumer's perspective. This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the module as conveyed in the text field of the resource itself. This item SHOULD be populated unless the information is available from context.; (xsd)description:markdown>?
[]< 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 ObservationDefinition instances. When multiple usageContexts are specified, there is no expectation for whether all or any of the contexts apply.; (xsd)useContext:UsageContext>*
[]< A jurisdiction in which the ObservationDefinition is intended to be used. It may be possible for the ObservationDefinition 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.) Binding: jurisdiction (extensible, Codes for country, country subdivision and region for indicating where a resource is intended to be used.); (xsd)jurisdiction:CodeableConcept>*
< Explains why this ObservationDefinition is needed and why it has been designed as it has. This element does not describe the usage of the ObservationDefinition. Rather it is for 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 ObservationDefinition.; (xsd)purpose:markdown>?
< Copyright statement relating to the ObservationDefinition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the ObservationDefinition.; (xsd)copyright:markdown>?
< A short string (<50 characters), suitable for inclusion in a page footer that identifies the copyright holder, effective period, and optionally whether rights are resctricted. (e.g. 'All rights reserved', 'Some rights reserved'). The (c) symbol should NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general 'copyright' element.; (xsd)copyrightLabel:string>?
< The date on which the asset content was approved by the publisher. Approval happens once when the content is officially approved for usage. The date may be more recent than the approval date because of minor changes / editorial corrections.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)approvalDate:date>?
< The date on which the asset content was last reviewed. Review happens periodically after that, but doesn't change the original approval date. If specified, this is usually after the approval date.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)lastReviewDate:date>?
< The period during which the ObservationDefinition content was or is planned to be effective. The effective period for an ObservationDefinition determines when the content is applicable for usage and is independent of publication and review dates. For example, an observation definition intended to be used for the year 2021 might be published in 2020.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)effectivePeriod:Period>?
[]< The canonical URL pointing to another FHIR-defined ObservationDefinition that is adhered to in whole or in part by this definition.; (xsd)derivedFromCanonical:ObservationDefinition*>*
[]< The URL pointing to an externally-defined observation definition, guideline or other definition that is adhered to in whole or in part by this definition.; (xsd)derivedFromUri:uri>*
[]< A code that describes the intended kind of subject of Observation instances conforming to this ObservationDefinition. Examples: person, animal, device, air, surface ….; (xsd)subject:CodeableConcept>*
< The type of individual/organization/device that is expected to act upon instances of this definition.; (xsd)performerType:CodeableConcept>?
[]< A code that classifies the general type of observation. This element allows various categorization schemes based on the owner’s definition of the category and effectively multiple categories can be used for one instance of ObservationDefinition. The level of granularity is defined by the category concepts in the value set. Binding: observation-category (example, Codes for high level observation categories.); (xsd)category:CodeableConcept>*
< Describes what will be observed. Sometimes this is called the observation "name". Binding: observation-codes (example, Codes identifying names of simple observations.); (xsd)code:InputObservationDefinition.code>
[]< The data types allowed for the value element of the instance observations conforming to this ObservationDefinition. Binding: permitted-data-type (required, Permitted data type for observation value.); (xsd)permittedDataType:code>*
< Multiple results allowed for observations conforming to this ObservationDefinition. An example of observation allowing multiple results is "bacteria identified by culture". Conversely, the measurement of a potassium level allows a single result.; (xsd)multipleResultsAllowed:boolean>?
< The site on the subject's body where the observation is to be made. Only used if the defined observation is to be made directly on a body part and if this body part is not implied by code found in ObservationDefinition.code. Not used for in vitro diagnostic observations.
Example: 14975008 |Forearm structure|. Binding: body-site (example, SNOMED CT body structures.); (xsd)bodySite:CodeableConcept>?
< The method or technique used to perform the observation. Only used if not implicit in observation code
Example: 702659008 |Automated count technique|. Binding: observation-methods (example, Methods for simple observations.); (xsd)method:CodeableConcept>?
[]< The kind of specimen that this type of observation is produced on. Only used for in vitro observations. When multiple occurrences of specimen are present, they are to be combined with a logical AND: all specified specimens are needed for the observation.; (xsd)specimen:SpecimenDefinition*>*
[]< The measurement model of device or actual device used to produce observations of this type. When multiple occurrences of device are present, they are to be combined with a logical OR: at least one of the specified devices is used to produce the observation.; (xsd)device:(<Device>
|<DeviceDefinition>)>*
< The preferred name to be used when reporting the results of observations conforming to this ObservationDefinition.; (xsd)preferredReportName:string>?
[]< Units allowed for the valueQuantity element in the instance observations conforming to this ObservationDefinition. Binding: ucum-units (preferred, Codes identifying units of measure.); (xsd)permittedUnit:Coding>*
[]< A set of qualified values associated with a context and a set of conditions - provides a range for quantitative and ordinal observations and a collection of value sets for qualitative observations.; (xsd)qualifiedValue:InputObservationDefinition.qualifiedValue>*
[]< This ObservationDefinition defines a group observation (e.g. a battery, a panel of tests, a set of vital sign measurements) that includes the target as a member of the group.; (xsd)hasMember:(<ObservationDefinition>
|<Questionnaire>)>*
[]< Some observations have multiple component observations, expressed as separate code value pairs.; (xsd)component:InputObservationDefinition.component>*🔗 Describes what will be observed. Sometimes this is called the observation "name". Binding: observation-codes (example, Codes identifying names of simple observations.)InputObservationDefinition.code(xsd)(doc)=
<#base:CodeableConcept>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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.; (xsd)coding:Coding>*
< 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.; (xsd)text:string>?
[]< 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.; (xsd)LOINC:InputObservationDefinition.code.LOINC>*🔗 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.InputObservationDefinition.code.LOINC(xsd)(doc)=
<#base:Coding>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< 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 be an absolute reference to some definition that establishes the system clearly and unambiguously. http://loinc.org; (xsd)system:uri>?
< 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.; (xsd)version:string>?
< 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).; (xsd)code>?
< A representation of the meaning of the code in the system, following the rules of the system.; (xsd)display:string>?
< 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.; (xsd)userSelected:boolean>?🔗 Some observations have multiple component observations, expressed as separate code value pairs.InputObservationDefinition.component(xsd)(doc)=
<#base:ObservationDefinition.component>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Describes what will be observed. Binding: observation-codes (example, Codes identifying names of simple observations.); (xsd)code:CodeableConcept>
[]< The data types allowed for the value element of the instance of this component observations. Binding: permitted-data-type (required, Permitted data type for observation value.); (xsd)permittedDataType:code>*
[]< Units allowed for the valueQuantity element in the instance observations conforming to this ObservationDefinition. Binding: ucum-units (preferred, Codes identifying units of measure.); (xsd)permittedUnit:Coding>*
[]< A set of qualified values associated with a context and a set of conditions - provides a range for quantitative and ordinal observations and a collection of value sets for qualitative observations.; (xsd)qualifiedValue:ObservationDefinition.qualifiedValue>*🔗 A set of qualified values associated with a context and a set of conditions - provides a range for quantitative and ordinal observations and a collection of value sets for qualitative observations.InputObservationDefinition.qualifiedValue(xsd)(doc)=
<#base:ObservationDefinition.qualifiedValue>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A concept defining the context for this set of qualified values. Binding: referencerange-meaning (extensible, ); (xsd)context:CodeableConcept>?
[]< The target population this set of qualified values applies to. If this element is not present then the global population is assumed. Binding: referencerange-appliesto (example, ); (xsd)appliesTo:CodeableConcept>*
< The gender this set of qualified values applies to. Binding: administrative-gender (required, ); (xsd)gender:code>?
< The age range this set of qualified values applies to. Some analytes vary greatly over age.; (xsd)age:Range>?
< The gestational age this set of qualified values applies to.; (xsd)gestationalAge:Range>?
< Text based condition for which the the set of qualified values is valid.; (xsd)condition:string>?
< The category of range of values for continuous or ordinal observations that match the criteria of this set of qualified values. Binding: observation-range-category (required, ); (xsd)rangeCategory:code>?
< The range of values defined for continuous or ordinal observations that match the criteria of this set of qualified values.; (xsd)range:Range>?
< The set of valid coded results for qualitative observations that match the criteria of this set of qualified values.; (xsd)validCodedValueSet:ValueSet*>?
< The set of normal coded results for qualitative observations that match the criteria of this set of qualified values.; (xsd)normalCodedValueSet:ValueSet*>?
< The set of abnormal coded results for qualitative observations that match the criteria of this set of qualified values.; (xsd)abnormalCodedValueSet:ValueSet*>?
< The set of critical coded results for qualitative observations that match the criteria of this set of qualified values.; (xsd)criticalCodedValueSet:ValueSet*>?🔗 A single issue - either an indication, contraindication, interaction or an undesirable effect for a medicinal product, medication, device or procedure.InteractionDefinition(xsd)(doc)=
<#base:ClinicalUseDefinition>
< The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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 its narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
< 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). Binding: all-languages (required, IETF language tag for a human language); (xsd)language:code>?
< 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 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.; (xsd)text:Narrative>?
[]< 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. 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.; (xsd)contained:Resource>*
[]< May be used to represent additional information that is not part of the basic definition of the resource. 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Business identifier for this issue.; (xsd)identifier:Identifier>*
< indication | contraindication | interaction | undesirable-effect | warning. Binding: clinical-use-definition-type (required, Overall defining type of this clinical use definition.) interaction; (xsd)type:code>
[]< A categorisation of the issue, primarily for dividing warnings into subject heading areas such as "Pregnancy and Lactation", "Overdose", "Effects on Ability to Drive and Use Machines". Binding: clinical-use-definition-category (preferred, A categorisation for a clinical use information item.); (xsd)category:CodeableConcept>*
[]< The medication, product, substance, device, procedure etc. for which this is an indication.; (xsd)subject:(<ActivityDefinition>
|<BiologicallyDerivedProduct>
|<Device>
|<DeviceDefinition>
|<Medication>
|<MedicinalProductDefinition>
|<NutritionProduct>
|<PlanDefinition>
|<Substance>)>*
< Whether this is a current issue or one that has been retired etc. Binding: publication-status (preferred, The lifecycle status of an artifact.); (xsd)status:CodeableConcept>?
< Specifics for when this is a contraindication.; (xsd)contraindication:InteractionDefinition.contraindication>{0,0}
< Specifics for when this is an indication.; (xsd)indication:InteractionDefinition.indication>{0,0}
< Specifics for when this is an interaction.; (xsd)interaction:InteractionDefinition.interaction>
[]< The population group to which this applies.; (xsd)population:Group*>*
[]< Logic used by the clinical use definition.; (xsd)library:Library*>*
< Describe the possible undesirable effects (negative outcomes) from the use of the medicinal product as treatment.; (xsd)undesirableEffect:InteractionDefinition.undesirableEffect>{0,0}
< A critical piece of information about environmental, health or physical risks or hazards that serve as caution to the user. For example 'Do not operate heavy machinery', 'May cause drowsiness', or 'Get medical advice/attention if you feel unwell'.; (xsd)warning:InteractionDefinition.warning>{0,0}🔗 Specifics for when this is a contraindication.InteractionDefinition.contraindication(xsd)(doc)=
<#base:ClinicalUseDefinition.contraindication>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The situation that is being documented as contraindicating against this item. Binding: disease-symptom-procedure (example, A symptom, disease or procedure.); (xsd)diseaseSymptomProcedure:ObservationDefinition*>?
< The status of the disease or symptom for the contraindication, for example "chronic" or "metastatic". Binding: disease-status (example, The status of a disease or symptom.); (xsd)diseaseStatus:ObservationDefinition*>?
[]< A comorbidity (concurrent condition) or coinfection. Binding: disease-symptom-procedure (example, A symptom, disease or procedure.); (xsd)comorbidity:ObservationDefinition*>*
[]< The indication which this is a contraidication for.; (xsd)indication:ClinicalUseDefinition*>*
< An expression that returns true or false, indicating whether the indication is applicable or not, after having applied its other elements. The expression may be inlined or may be a reference to a named expression within a logic library referenced by the library element.; (xsd)applicability:Expression>?
[]< Information about the use of the medicinal product in relation to other therapies described as part of the contraindication.; (xsd)otherTherapy:InteractionDefinition.contraindication.otherTherapy>*🔗 Information about the use of the medicinal product in relation to other therapies described as part of the contraindication.InteractionDefinition.contraindication.otherTherapy(xsd)(doc)=
<#base:ClinicalUseDefinition.contraindication.otherTherapy>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type of relationship between the medicinal product indication or contraindication and another therapy. Binding: therapy-relationship-type (preferred, Classification of relationship between a therapy and a contraindication or an indication.); (xsd)relationshipType:CodeableConcept>
< Reference to a specific medication (active substance, medicinal product or class of products, biological, food etc.) as part of an indication or contraindication. Binding: therapy (example, A therapy.); (xsd)treatment:(<ActivityDefinition>
|<BiologicallyDerivedProduct>
|<Medication>
|<MedicinalProductDefinition>
|<NutritionProduct>
|<Substance>
|<SubstanceDefinition>)>🔗 Specifics for when this is an indication.InteractionDefinition.indication(xsd)(doc)=
<#base:ClinicalUseDefinition.indication>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The situation that is being documented as an indicaton for this item. Binding: disease-symptom-procedure (example, A symptom, disease or procedure.); (xsd)diseaseSymptomProcedure:ObservationDefinition*>?
< The status of the disease or symptom for the indication, for example "chronic" or "metastatic". Binding: disease-status (example, The status of a disease or symptom.); (xsd)diseaseStatus:ObservationDefinition*>?
[]< A comorbidity (concurrent condition) or coinfection as part of the indication. Binding: disease-symptom-procedure (example, A symptom, disease or procedure.); (xsd)comorbidity:ObservationDefinition*>*
< The intended effect, aim or strategy to be achieved. Binding: product-intended-use (preferred, The overall intended use of a product.); (xsd)intendedEffect:ObservationDefinition*>?
< Timing or duration information, that may be associated with use with the indicated condition e.g. Adult patients suffering from myocardial infarction (from a few days until less than 35 days), ischaemic stroke (from 7 days until less than 6 months).; (xsd)duration:(<Range>
|<string>)>?
[]< An unwanted side effect or negative outcome that may happen if you use the drug (or other subject of this resource) for this indication.; (xsd)undesirableEffect:ClinicalUseDefinition*>*
< An expression that returns true or false, indicating whether the indication is applicable or not, after having applied its other elements. The expression may be inlined or may be a reference to a named expression within a logic library referenced by the library element.; (xsd)applicability:Expression>?
[]< Information about the use of the medicinal product in relation to other therapies described as part of the indication.; (xsd)otherTherapy:ClinicalUseDefinition.contraindication.otherTherapy>*🔗 Specifics for when this is an interaction.InteractionDefinition.interaction(xsd)(doc)=
<#base:ClinicalUseDefinition.interaction>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< The specific medication, product, food, substance etc. or laboratory test that interacts.; (xsd)interactant:InteractionDefinition.interaction.interactant>*
< The type of the interaction e.g. drug-drug interaction, drug-food interaction, drug-lab test interaction. Binding: interaction-type (example, A categorisation for an interaction between two substances.); (xsd)type:CodeableConcept>?
< The effect of the interaction, for example "reduced gastric absorption of primary medication". Binding: interaction-effect (example, A interaction effect of clinical use of a medication or other substance.); (xsd)effect:ObservationDefinition*>?
< The incidence of the interaction, e.g. theoretical, observed. Binding: interaction-incidence (example, A categorisation for incidence of occurence of an interaction.); (xsd)incidence:CodeableConcept>?
[]< Actions for managing the interaction. Binding: interaction-management (example, A type of management for an interaction of a medication or other substance.); (xsd)management:CodeableConcept>*🔗 The specific medication, product, food, substance etc. or laboratory test that interacts.InteractionDefinition.interaction.interactant(xsd)(doc)=
<#base:ClinicalUseDefinition.interaction.interactant>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The specific medication, product, food, substance etc. or laboratory test that interacts. Binding: interactant (example, An interactant - a substance that may have a clinically significant effect on another.); (xsd)item:(<BiologicallyDerivedProduct>
|<CodeableConcept>
|<Medication>
|<MedicinalProductDefinition>
|<NutritionProduct>
|<ObservationDefinition>
|<Substance>)>🔗 Describe the possible undesirable effects (negative outcomes) from the use of the medicinal product as treatment.InteractionDefinition.undesirableEffect(xsd)(doc)=
<#base:ClinicalUseDefinition.undesirableEffect>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The situation in which the undesirable effect may manifest. Binding: undesirable-effect-symptom (example, An undesirable effect of clinical use.); (xsd)symptomConditionEffect:ObservationDefinition*>?
< High level classification of the effect. Binding: undesirable-effect-classification (example, A categorisation for an undesirable effect.); (xsd)classification:CodeableConcept>?
< How often the effect is seen. Binding: undesirable-effect-frequency (example, A categorisation for a frequency of occurence of an undesirable effect.); (xsd)frequencyOfOccurrence:CodeableConcept>?🔗 A critical piece of information about environmental, health or physical risks or hazards that serve as caution to the user. For example 'Do not operate heavy machinery', 'May cause drowsiness', or 'Get medical advice/attention if you feel unwell'.InteractionDefinition.warning(xsd)(doc)=
<#base:ClinicalUseDefinition.warning>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A textual definition of this warning, with formatting.; (xsd)description:markdown>?
< A coded or unformatted textual definition of this warning. Binding: warning-type (example, Classification of warning type.); (xsd)code:CodeableConcept>?🔗 A container for a collection of resources.ItemTransactionRequest(xsd)(doc)=
<#base:Bundle>
< The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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 its narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
< 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). Binding: all-languages (required, IETF language tag for a human language); (xsd)language:code>?
< A persistent identifier for the bundle that won't change as a bundle is copied from server to server. Persistent identity generally only matters for batches of type Document, Message, and Collection. It would not normally be populated for search and history results and servers ignore Bundle.identifier when processing batches and transactions. For Documents the .identifier SHALL be populated such that the .identifier is globally unique.; (xsd)identifier:Identifier>?
< This transaction Bundle is to convey the request to create/update/delete/patch content of a catalog, from the Catalog Owner to the Catalog Custodian This transaction Bundle is usable with any kind of catalog (laboratory compendium, drug formulary, order sets, devices ...) Binding: bundle-type (required, Indicates the purpose of a bundle - how it is intended to be used.) transaction; (xsd)type:code>
< The date/time that the bundle was assembled - i.e. when the resources were placed in the bundle. For many bundles, the timestamp is equal to .meta.lastUpdated, because they are not stored (e.g. search results). When a bundle is placed in a persistent store, .meta.lastUpdated will be usually be changed by the server. When the bundle is a message, a middleware agent altering the message (even if not stored) SHOULD update .meta.lastUpdated. .timestamp is used to track the original time of the Bundle, and SHOULD be populated.
Usage:
* document : the date the document was created. Note: the composition may predate the document, or be associated with multiple documents. The date of the composition - the authoring time - may be earlier than the document assembly time
* message : the date that the content of the message was assembled. This date is not changed by middleware engines unless they add additional data that changes the meaning of the time of the message
* history : the date that the history was assembled. This time would be used as the _since time to ask for subsequent updates
* searchset : the time that the search set was assembled. Note that different pages MAY have different timestamps but need not. Having different timestamps does not imply that subsequent pages will represent or include changes made since the initial query
* transaction | transaction-response | batch | batch-response | collection : no particular assigned meaning
The timestamp value should be greater than the lastUpdated and other timestamps in the resources in the bundle, and it should be equal or earlier than the .meta.lastUpdated on the Bundle itself.; (xsd)timestamp:instant>?
< If a set of search matches, this is the (potentially estimated) total number of entries of type 'match' across all pages in the search. It does not include search.mode = 'include' or 'outcome' entries and it does not provide a count of the number of entries in the Bundle. Only used if the bundle is a search result set. The total does not include resources such as OperationOutcome and included resources, only the total number of matching resources.; (xsd)total:unsignedInt>?
[]< A series of links that provide context to this bundle. Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. [HATEOAS](http://en.wikipedia.org/wiki/HATEOAS)).
Bundle.entry.link corresponds to links found in the HTTP header if the resource in the entry was [read](http://hl7.org/fhir/R5/http.html#read) directly.
This specification defines some specific uses of Bundle.link for [searching](http://hl7.org/fhir/R5/search.html#conformance) and [paging](http://hl7.org/fhir/R5/http.html#paging), but no specific uses for Bundle.entry.link, and no defined function in a transaction - the meaning is implementation specific. The behavior of navigation link types (next/prev/first/last) are well defined for searchset and history Bundles but are not currently defined for other types. Implementers who choose to use such link relationships for other bundle types will need to negotiate behavior with their interoperability partners.; (xsd)link:ItemTransactionRequest.link>*
[]< Each entry will contain a resource representing a catalog item or one of the supporting resources of a catalog item.
The resource will be followed by a request instructing the Catalog Custodian what action (create/update/delete/patch) to perform on this resource; (xsd)entry:ItemTransactionRequest.entry>+
< Digital Signature - base64 encoded. XML-DSig or a JWS. The signature could be created by the "author" of the bundle or by the originating device. Requirements around inclusion of a signature, verification of signatures and treatment of signed/non-signed bundles is implementation-environment specific.; (xsd)signature:Signature>?
< Captures issues and warnings that relate to the construction of the Bundle and the content within it. Usage notes: These issues and warnings must apply to the Bundle as a whole, not to individual entries.Messages relating to the processing of individual entries (e.g. in a batch or transaction) SHALL be reported in the entry.response.outcome for that entry. If there are errors that arise in the creation of the Bundle, then that should be handled by an OperationOutcome being returned instead of the Bundle.; (xsd)issues:OperationOutcome>?🔗 Each entry will contain a resource representing a catalog item or one of the supporting resources of a catalog item.
The resource will be followed by a request instructing the Catalog Custodian what action (create/update/delete/patch) to perform on this resourceItemTransactionRequest.entry(xsd)(doc)=
<#base:Bundle.entry>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. Except for transactions and batches, each entry in a Bundle must have a fullUrl. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. Even when not required, fullUrl MAY be set to a urn:uuid to allow referencing entries in a transaction. The fullUrl can be an arbitrary URI and is not limited to urn:uuid, urn:oid, http, and https. The fullUrl element SHALL have a value except when:
* invoking a create
* invoking or responding to an operation where the body is not a single identified resource
* invoking or returning the results of a search or history operation. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R5/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R5/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R5/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>
< The Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type. This is allowed to be a Parameters resource if and only if it is referenced by something else within the Bundle that provides context/meaning.; (xsd)resource:Resource>
< Information about the search process that lead to the creation of this entry.; (xsd)search:ItemTransactionRequest.entry.search>{0,0}
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ItemTransactionRequest.entry.request>
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ItemTransactionRequest.entry.response>{0,0}🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ItemTransactionRequest.entry.request(xsd)(doc)=
<#base:Bundle.entry.request>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred. Binding: http-verb (required, HTTP verbs (in the HTTP command line). See [HTTP rfc](https://tools.ietf.org/html/rfc7231) for details.); (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R5/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R5/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R5/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R5/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ItemTransactionRequest.entry.response(xsd)(doc)=
<#base:Bundle.entry.response>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R5/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R5/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ItemTransactionRequest.entry.search(xsd)(doc)=
<#base:Bundle.entry.search>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence. Binding: search-entry-mode (required, Why an entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process.); (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R5/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 A series of links that provide context to this bundle. Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. [HATEOAS](http://en.wikipedia.org/wiki/HATEOAS)).
Bundle.entry.link corresponds to links found in the HTTP header if the resource in the entry was [read](http://hl7.org/fhir/R5/http.html#read) directly.
This specification defines some specific uses of Bundle.link for [searching](http://hl7.org/fhir/R5/search.html#conformance) and [paging](http://hl7.org/fhir/R5/http.html#paging), but no specific uses for Bundle.entry.link, and no defined function in a transaction - the meaning is implementation specific. The behavior of navigation link types (next/prev/first/last) are well defined for searchset and history Bundles but are not currently defined for other types. Implementers who choose to use such link relationships for other bundle types will need to negotiate behavior with their interoperability partners.ItemTransactionRequest.link(xsd)(doc)=
<#base:Bundle.link>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A name which details the functional use for this link - see [http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1](http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1). Binding: iana-link-relations (required, ); (xsd)relation:code>
< The reference details for the link.; (xsd)url:uri>🔗 A container for a collection of resources.ItemTransactionResponse(xsd)(doc)=
<#base:Bundle>
< The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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 its narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
< 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). Binding: all-languages (required, IETF language tag for a human language); (xsd)language:code>?
< A persistent identifier for the bundle that won't change as a bundle is copied from server to server. Persistent identity generally only matters for batches of type Document, Message, and Collection. It would not normally be populated for search and history results and servers ignore Bundle.identifier when processing batches and transactions. For Documents the .identifier SHALL be populated such that the .identifier is globally unique.; (xsd)identifier:Identifier>?
< This transaction Bundle is to convey the response to a transaction request to create/update/delete/patch content of a catalog, from the Catalog Owner to the Catalog Custodian This transaction Bundle is usable with any kind of catalog (laboratory compendium, drug formulary, order sets, devices ...) Binding: bundle-type (required, Indicates the purpose of a bundle - how it is intended to be used.) transaction-response; (xsd)type:code>
< The date/time that the bundle was assembled - i.e. when the resources were placed in the bundle. For many bundles, the timestamp is equal to .meta.lastUpdated, because they are not stored (e.g. search results). When a bundle is placed in a persistent store, .meta.lastUpdated will be usually be changed by the server. When the bundle is a message, a middleware agent altering the message (even if not stored) SHOULD update .meta.lastUpdated. .timestamp is used to track the original time of the Bundle, and SHOULD be populated.
Usage:
* document : the date the document was created. Note: the composition may predate the document, or be associated with multiple documents. The date of the composition - the authoring time - may be earlier than the document assembly time
* message : the date that the content of the message was assembled. This date is not changed by middleware engines unless they add additional data that changes the meaning of the time of the message
* history : the date that the history was assembled. This time would be used as the _since time to ask for subsequent updates
* searchset : the time that the search set was assembled. Note that different pages MAY have different timestamps but need not. Having different timestamps does not imply that subsequent pages will represent or include changes made since the initial query
* transaction | transaction-response | batch | batch-response | collection : no particular assigned meaning
The timestamp value should be greater than the lastUpdated and other timestamps in the resources in the bundle, and it should be equal or earlier than the .meta.lastUpdated on the Bundle itself.; (xsd)timestamp:instant>?
< If a set of search matches, this is the (potentially estimated) total number of entries of type 'match' across all pages in the search. It does not include search.mode = 'include' or 'outcome' entries and it does not provide a count of the number of entries in the Bundle. Only used if the bundle is a search result set. The total does not include resources such as OperationOutcome and included resources, only the total number of matching resources.; (xsd)total:unsignedInt>?
[]< A series of links that provide context to this bundle. Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. [HATEOAS](http://en.wikipedia.org/wiki/HATEOAS)).
Bundle.entry.link corresponds to links found in the HTTP header if the resource in the entry was [read](http://hl7.org/fhir/R5/http.html#read) directly.
This specification defines some specific uses of Bundle.link for [searching](http://hl7.org/fhir/R5/search.html#conformance) and [paging](http://hl7.org/fhir/R5/http.html#paging), but no specific uses for Bundle.entry.link, and no defined function in a transaction - the meaning is implementation specific. The behavior of navigation link types (next/prev/first/last) are well defined for searchset and history Bundles but are not currently defined for other types. Implementers who choose to use such link relationships for other bundle types will need to negotiate behavior with their interoperability partners.; (xsd)link:ItemTransactionResponse.link>*
[]< Each entry will contain a resource representing a catalog item or one of the supporting resources of a catalog item.
The resource will be followed by a request instructing the Catalog Custodian what action (create/update/delete/patch) to perform on this resource; (xsd)entry:ItemTransactionResponse.entry>+
< Digital Signature - base64 encoded. XML-DSig or a JWS. The signature could be created by the "author" of the bundle or by the originating device. Requirements around inclusion of a signature, verification of signatures and treatment of signed/non-signed bundles is implementation-environment specific.; (xsd)signature:Signature>?
< Captures issues and warnings that relate to the construction of the Bundle and the content within it. Usage notes: These issues and warnings must apply to the Bundle as a whole, not to individual entries.Messages relating to the processing of individual entries (e.g. in a batch or transaction) SHALL be reported in the entry.response.outcome for that entry. If there are errors that arise in the creation of the Bundle, then that should be handled by an OperationOutcome being returned instead of the Bundle.; (xsd)issues:OperationOutcome>?🔗 Each entry will contain a resource representing a catalog item or one of the supporting resources of a catalog item.
The resource will be followed by a request instructing the Catalog Custodian what action (create/update/delete/patch) to perform on this resourceItemTransactionResponse.entry(xsd)(doc)=
<#base:Bundle.entry>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< A series of links that provide context to this entry.; (xsd)link:Bundle.link>*
< The Absolute URL for the resource. Except for transactions and batches, each entry in a Bundle must have a fullUrl. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. Even when not required, fullUrl MAY be set to a urn:uuid to allow referencing entries in a transaction. The fullUrl can be an arbitrary URI and is not limited to urn:uuid, urn:oid, http, and https. The fullUrl element SHALL have a value except when:
* invoking a create
* invoking or responding to an operation where the body is not a single identified resource
* invoking or returning the results of a search or history operation. fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R5/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R5/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R5/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id.
Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).; (xsd)fullUrl:uri>
< The Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type. This is allowed to be a Parameters resource if and only if it is referenced by something else within the Bundle that provides context/meaning.; (xsd)resource:Resource>
< Information about the search process that lead to the creation of this entry.; (xsd)search:ItemTransactionResponse.entry.search>{0,0}
< Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.; (xsd)request:ItemTransactionResponse.entry.request>{0,0}
< Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.; (xsd)response:ItemTransactionResponse.entry.response>🔗 Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.ItemTransactionResponse.entry.request(xsd)(doc)=
<#base:Bundle.entry.request>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred. Binding: http-verb (required, HTTP verbs (in the HTTP command line). See [HTTP rfc](https://tools.ietf.org/html/rfc7231) for details.); (xsd)method:code>
< The URL for this entry, relative to the root (the address to which the request is posted). E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".; (xsd)url:uri>
< If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R5/http.html#cread).; (xsd)ifNoneMatch:string>?
< Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R5/http.html#cread).; (xsd)ifModifiedSince:instant>?
< Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R5/http.html#concurrency).; (xsd)ifMatch:string>?
< Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R5/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").; (xsd)ifNoneExist:string>?🔗 Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.ItemTransactionResponse.entry.response(xsd)(doc)=
<#base:Bundle.entry.response>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.; (xsd)status:string>
< The location header created by processing this operation, populated if the operation returns a location.; (xsd)location:uri>?
< The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R5/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R5/http.html#concurrency)). Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.; (xsd)etag:string>?
< The date/time that the resource was modified on the server. This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.; (xsd)lastModified:instant>?
< An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.
This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.; (xsd)outcome:Resource>?🔗 Information about the search process that lead to the creation of this entry.ItemTransactionResponse.entry.search(xsd)(doc)=
<#base:Bundle.entry.search>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence. Binding: search-entry-mode (required, Why an entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process.); (xsd)mode:code>?
< When searching, the server's search ranking score for the entry. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
See [Patient Match](http://hl7.org/fhir/R5/patient-operation-match.html) for the EMPI search which relates to this element.; (xsd)score:decimal>?🔗 A series of links that provide context to this bundle. Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. [HATEOAS](http://en.wikipedia.org/wiki/HATEOAS)).
Bundle.entry.link corresponds to links found in the HTTP header if the resource in the entry was [read](http://hl7.org/fhir/R5/http.html#read) directly.
This specification defines some specific uses of Bundle.link for [searching](http://hl7.org/fhir/R5/search.html#conformance) and [paging](http://hl7.org/fhir/R5/http.html#paging), but no specific uses for Bundle.entry.link, and no defined function in a transaction - the meaning is implementation specific. The behavior of navigation link types (next/prev/first/last) are well defined for searchset and history Bundles but are not currently defined for other types. Implementers who choose to use such link relationships for other bundle types will need to negotiate behavior with their interoperability partners.ItemTransactionResponse.link(xsd)(doc)=
<#base:Bundle.link>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A name which details the functional use for this link - see [http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1](http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1). Binding: iana-link-relations (required, ); (xsd)relation:code>
< The reference details for the link.; (xsd)url:uri>🔗 The ChargeItemDefinition resource provides the properties that apply to the (billing) codes necessary to calculate costs and prices. The properties may differ largely depending on type and realm, therefore this resource gives only a rough structure and requires profiling for each type of billing code system.LabChargeItemDefinition(xsd)(doc)=
<#base:ChargeItemDefinition>
< The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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 its narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
< 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). Binding: all-languages (required, IETF language tag for a human language); (xsd)language:code>?
< 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 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.; (xsd)text:Narrative>?
[]< 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. 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.; (xsd)contained:Resource>*
[]< May be used to represent additional information that is not part of the basic definition of the resource. 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< An absolute URI that is used to identify this charge item 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 charge item definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the charge item 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/R5/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/R5/resource.html#meta) element to indicate where the current master source of the resource can be found.; (xsd)url:uri>?
[]< A formal identifier that is used to identify this charge item 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 charge item definition outside of FHIR, where it is not possible to use the logical URI.; (xsd)identifier:Identifier>*
< The identifier that is used to identify this version of the charge item definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the charge item 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 assets. There may be different charge item 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 charge item definition with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](http://hl7.org/fhir/R5/resource.html#bv-format).; (xsd)version:string>?
< Indicates the mechanism used to compare versions to determine which is more current. If set as a string, this is a FHIRPath expression that has two additional context variables passed in - %version1 and %version2 and will return a negative number if version1 is newer, a positive number if version2 and a 0 if the version ordering can't be successfully be determined. Binding: version-algorithm (extensible, ); (xsd)versionAlgorithm:(<Coding>
|<string>)>?
< A natural language name identifying the ChargeItemDefinition. 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.; (xsd)name:string>?
< A short, descriptive, user-friendly title for the charge item definition. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; (xsd)title:LabChargeItemDefinition.title>?
[]< The URL pointing to an externally-defined charge item definition that is adhered to in whole or in part by this definition.; (xsd)derivedFromUri:uri>*
[]< A larger definition of which this particular definition is a component or step.; (xsd)partOf:ChargeItemDefinition*>*
[]< As new versions of a protocol or guideline are defined, allows identification of what versions are replaced by a new instance.; (xsd)replaces:ChargeItemDefinition*>*
< The current state of the ChargeItemDefinition. Allows filtering of charge item definitions that are appropriate for use versus not.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization). Binding: publication-status (required, The lifecycle status of an artifact.); (xsd)status:code>
< A Boolean value to indicate that this charge item definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Allows filtering of charge item definitions that are appropriate for use versus not.; (xsd)experimental:boolean>?
< The date (and optionally time) when the charge item 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 charge item definition changes. 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 charge item 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](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)date:dateTime>?
< The name of the organization or individual responsible for the release and ongoing maintenance of the charge item definition. Usually an organization but may be an individual. The publisher (or steward) of the charge item definition is the organization or individual primarily responsible for the maintenance and upkeep of the charge item 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 charge item definition. This item SHOULD be populated unless the information is available from context.; (xsd)publisher:string>?
[]< 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.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)contact:ContactDetail>*
< A free text natural language description of the charge item definition from a consumer's perspective. This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the charge item 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 charge item definition is presumed to be the predominant language in the place the charge item definition was created).; (xsd)description:markdown>?
[]< 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 charge item definition instances. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:UsageContext>*
[]< A legal or geographic region in which the charge item definition is intended to be used. It may be possible for the charge item 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.) Binding: jurisdiction (extensible, Countries and regions within which this artifact is targeted for use.); (xsd)jurisdiction:CodeableConcept>*
< Explanation of why this charge item definition is needed and why it has been designed as it has. This element does not describe the usage of the charge item 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 charge item definition.; (xsd)purpose:markdown>?
< A copyright statement relating to the charge item definition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the charge item definition.; (xsd)copyright:markdown>?
< A short string (<50 characters), suitable for inclusion in a page footer that identifies the copyright holder, effective period, and optionally whether rights are resctricted. (e.g. 'All rights reserved', 'Some rights reserved'). The (c) symbol should NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general 'copyright' element.; (xsd)copyrightLabel:string>?
< 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.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)approvalDate:date>?
< 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.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)lastReviewDate:date>?
< The defined billing details in this resource pertain to the given billing code. Binding: chargeitem-billingcodes (example, Billing Code defined by this ChargeItemDefinition.); (xsd)code:CodeableConcept>
[]< The defined billing details in this resource pertain to the given product instance(s). In case of highly customized, individually produced or fitted devices/substances, the pricing information may be different for each instance of the product. This reference links pricing details to specific product instances.; (xsd)instance:(<ActivityDefinition>
|<Device>
|<DeviceDefinition>
|<HealthcareService>
|<Medication>
|<PlanDefinition>
|<Substance>)>*
[]< Expressions that describe applicability criteria for the billing code. The applicability conditions can be used to ascertain whether a billing item is allowed in a specific context. E.g. some billing codes may only be applicable in out-patient settings, only to male/female patients or only to children.; (xsd)applicability:LabChargeItemDefinition.applicability>*
[]< Group of properties which are applicable under the same conditions. If no applicability rules are established for the group, then all properties always apply.; (xsd)propertyGroup:LabChargeItemDefinition.propertyGroup>*
[]< 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 charge item definition instances. When multiple clinical focus contexts are specified the billing code is applicable if at least one of these contexts is present in the instance; (xsd)ClinicalFocus:LabChargeItemDefinition.ClinicalFocus>*🔗 Expressions that describe applicability criteria for the billing code. The applicability conditions can be used to ascertain whether a billing item is allowed in a specific context. E.g. some billing codes may only be applicable in out-patient settings, only to male/female patients or only to children.LabChargeItemDefinition.applicability(xsd)(doc)=
<#base:ChargeItemDefinition.applicability>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< An expression that returns true or false, indicating whether the condition is satisfied. When using FHIRPath expressions, the %context environment variable must be replaced at runtime with the ChargeItem resource to which this definition is applied. Please note that FHIRPath Expressions can only be evaluated in the scope of the current ChargeItem resource to which this definition is being applied.
FHIRPath expressions can traverse into other resources linked from the ChargeItem resource, however, testing rules such as that a billing code may be billed only once per encounter need a wider scope. In such scenarios, CQL may be the appropriate choice.; (xsd)condition:Expression>?
< The period during which the charge item definition content was or is planned to be in active use. The effective period for a charge item 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.; (xsd)effectivePeriod:Period>?
< Reference to / quotation of the external source of the group of properties.; (xsd)relatedArtifact:RelatedArtifact>?🔗 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 charge item definition instances. When multiple clinical focus contexts are specified the billing code is applicable if at least one of these contexts is present in the instanceLabChargeItemDefinition.ClinicalFocus(xsd)(doc)=
<#base:UsageContext>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< A code that identifies the type of context being specified by this usage context. Binding: http://terminology.hl7.org/ValueSet/usage-context-type (extensible, A code that specifies a type of context being specified by a usage context.); (xsd)code:LabChargeItemDefinition.ClinicalFocus.code>
< A value that defines the context specified in this context of use. The interpretation of the value is defined by the code. Binding: use-context (example, A code that defines the specific value for the context being specified.); (xsd)value:LabChargeItemDefinition.ClinicalFocus.value[x]>🔗 A code that identifies the type of context being specified by this usage context. Binding: http://terminology.hl7.org/ValueSet/usage-context-type (extensible, A code that specifies a type of context being specified by a usage context.)LabChargeItemDefinition.ClinicalFocus.code(xsd)(doc)=
<#base:Coding>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< 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 be an absolute reference to some definition that establishes the system clearly and unambiguously. http://terminology.hl7.org/CodeSystem/usage-context-type; (xsd)system:uri>?
< 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.; (xsd)version:string>?
< 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). focus; (xsd)code>?
< A representation of the meaning of the code in the system, following the rules of the system.; (xsd)display:string>?
< 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.; (xsd)userSelected:boolean>?🔗 A value that defines the context specified in this context of use. The interpretation of the value is defined by the code. Binding: use-context (example, A code that defines the specific value for the context being specified.)LabChargeItemDefinition.ClinicalFocus.value[x](xsd)(doc)=
<#base:CodeableConcept>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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. Binding: example-clinical-focus (example, All contexts for any laboratory test); (xsd)coding:Coding>*
< 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.; (xsd)text:string>?🔗 Group of properties which are applicable under the same conditions. If no applicability rules are established for the group, then all properties always apply.LabChargeItemDefinition.propertyGroup(xsd)(doc)=
<#base:ChargeItemDefinition.propertyGroup>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Expressions that describe applicability criteria for the priceComponent. The applicability conditions can be used to ascertain whether a billing item is allowed in a specific context. E.g. some billing codes may only be applicable in out-patient settings, only to male/female patients or only to children.; (xsd)applicability:ChargeItemDefinition.applicability>*
[]< The price for a ChargeItem may be calculated as a base price with surcharges/deductions that apply in certain conditions. A ChargeItemDefinition resource that defines the prices, factors and conditions that apply to a billing code is currently under development. The priceComponent element can be used to offer transparency to the recipient of the Invoice of how the prices have been calculated.; (xsd)priceComponent:MonetaryComponent>*🔗 A short, descriptive, user-friendly title for the charge item definition. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.LabChargeItemDefinition.title(xsd)(doc)=
<#base:string>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< The actual value; (xsd)value:string>?
[]< Language translation from base language of resource to another language.; (xsd)LanguageSynonym:Extension>*🔗 Set of definitional characteristics for a kind of observation or measurement produced or consumed by an orderable health care service. An instance of this resource informs the consumer of a health-related service (such as a lab diagnostic test or panel) about how the observations used or produced by this service will look like.LabObservationDefinition(xsd)(doc)=
<#base:ObservationDefinition>
< The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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 its narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
< 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). Binding: all-languages (required, IETF language tag for a human language); (xsd)language:code>?
< 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 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.; (xsd)text:Narrative>?
[]< 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. 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.; (xsd)contained:Resource>*
[]< May be used to represent additional information that is not part of the basic definition of the resource. 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< An absolute URL that is used to identify this ObservationDefinition when it is referenced in a specification, model, design or an instance. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this ObservationDefinition is (or will be) published. The URL SHOULD include the major version of the ObservationDefinition. For more information see Technical and Business Versions. Can be a urn:uuid: or a urn:oid:, but real http: addresses are preferred. This is the URI that will be used when making canonical references to this resource.; (xsd)url:uri>?
< Business identifiers assigned to this ObservationDefinition. by the performer and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server. This is a business identifier, not a resource identifier. It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types.; (xsd)identifier:Identifier>?
< The identifier that is used to identify this version of the ObservationDefinition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the ObservationDefinition 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 are orderable. There may be multiple different instances of an observationDefinition that have the same identifier but different versions.; (xsd)version:string>?
< Indicates the mechanism used to compare versions to determine which is more current. If set as a string, this is a FHIRPath expression that has two additional context variables passed in - %version1 and %version2 and will return a negative number if version1 is newer, a positive number if version2 and a 0 if the version ordering can't be successfully be determined. Binding: version-algorithm (extensible, ); (xsd)versionAlgorithm:(<Coding>
|<string>)>?
< A natural language name identifying the ObservationDefinition. 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.; (xsd)name:string>?
< A short, descriptive, user-friendly title for the ObservationDefinition.; (xsd)title:string>?
< The current state of the ObservationDefinition. A nominal state-transition diagram can be found in the [Definition pattern](http://hl7.org/fhir/R5/definition.html#statemachine) documentation
Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization). Binding: publication-status (required, Codes identifying the state of an ObservationDefinition.); (xsd)status:code>
< A flag to indicate that this ObservationDefinition is authored for testing purposes (or education/evaluation/marketing), and is not intended to be used for genuine usage. Allows filtering of ObservationDefinition that are appropriate for use vs. not.; (xsd)experimental:boolean>?
< The date (and optionally time) when the ObservationDefinition 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 ObservationDefinition changes. 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 ObservationDefinition. 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](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)date:dateTime>?
< Helps establish the "authority/credibility" of the ObservationDefinition. May also allow for contact.; (xsd)publisher:string>?
[]< 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.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)contact:ContactDetail>*
< A free text natural language description of the ObservationDefinition from the consumer's perspective. This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the module as conveyed in the text field of the resource itself. This item SHOULD be populated unless the information is available from context.; (xsd)description:markdown>?
[]< 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 ObservationDefinition instances. When multiple usageContexts are specified, there is no expectation for whether all or any of the contexts apply.; (xsd)useContext:UsageContext>*
[]< A jurisdiction in which the ObservationDefinition is intended to be used. It may be possible for the ObservationDefinition 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.) Binding: jurisdiction (extensible, Codes for country, country subdivision and region for indicating where a resource is intended to be used.); (xsd)jurisdiction:CodeableConcept>*
< Explains why this ObservationDefinition is needed and why it has been designed as it has. This element does not describe the usage of the ObservationDefinition. Rather it is for 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 ObservationDefinition.; (xsd)purpose:markdown>?
< Copyright statement relating to the ObservationDefinition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the ObservationDefinition.; (xsd)copyright:markdown>?
< A short string (<50 characters), suitable for inclusion in a page footer that identifies the copyright holder, effective period, and optionally whether rights are resctricted. (e.g. 'All rights reserved', 'Some rights reserved'). The (c) symbol should NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general 'copyright' element.; (xsd)copyrightLabel:string>?
< The date on which the asset content was approved by the publisher. Approval happens once when the content is officially approved for usage. The date may be more recent than the approval date because of minor changes / editorial corrections.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)approvalDate:date>?
< The date on which the asset content was last reviewed. Review happens periodically after that, but doesn't change the original approval date. If specified, this is usually after the approval date.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)lastReviewDate:date>?
< The period during which the ObservationDefinition content was or is planned to be effective. The effective period for an ObservationDefinition determines when the content is applicable for usage and is independent of publication and review dates. For example, an observation definition intended to be used for the year 2021 might be published in 2020.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)effectivePeriod:Period>?
[]< The canonical URL pointing to another FHIR-defined ObservationDefinition that is adhered to in whole or in part by this definition.; (xsd)derivedFromCanonical:ObservationDefinition*>*
[]< The URL pointing to an externally-defined observation definition, guideline or other definition that is adhered to in whole or in part by this definition.; (xsd)derivedFromUri:uri>*
[]< A code that describes the intended kind of subject of Observation instances conforming to this ObservationDefinition. Examples: person, animal, device, air, surface ….; (xsd)subject:CodeableConcept>*
< The type of individual/organization/device that is expected to act upon instances of this definition.; (xsd)performerType:CodeableConcept>?
[]< A code that classifies the general type of observation. This element allows various categorization schemes based on the owner’s definition of the category and effectively multiple categories can be used for one instance of ObservationDefinition. The level of granularity is defined by the category concepts in the value set. Binding: observation-category (example, Codes for high level observation categories.); (xsd)category:CodeableConcept>*
< Describes what will be observed. Sometimes this is called the observation "name". Binding: observation-codes (example, Codes identifying names of simple observations.); (xsd)code:LabObservationDefinition.code>
[]< The data types allowed for the value element of the instance observations conforming to this ObservationDefinition. Binding: permitted-data-type (required, Permitted data type for observation value.); (xsd)permittedDataType:code>*
< Multiple results allowed for observations conforming to this ObservationDefinition. An example of observation allowing multiple results is "bacteria identified by culture". Conversely, the measurement of a potassium level allows a single result.; (xsd)multipleResultsAllowed:boolean>?
< The site on the subject's body where the observation is to be made. Only used if the defined observation is to be made directly on a body part and if this body part is not implied by code found in ObservationDefinition.code. Not used for in vitro diagnostic observations.
Example: 14975008 |Forearm structure|. Binding: body-site (example, SNOMED CT body structures.); (xsd)bodySite:CodeableConcept>?
< The method or technique used to perform the observation. Only used if not implicit in observation code
Example: 702659008 |Automated count technique|. Binding: observation-methods (example, Methods for simple observations.); (xsd)method:CodeableConcept>?
[]< The kind of specimen that this type of observation is produced on. Only used for in vitro observations. When multiple occurrences of specimen are present, they are to be combined with a logical AND: all specified specimens are needed for the observation.; (xsd)specimen:SpecimenDefinition*>*
[]< The measurement model of device or actual device used to produce observations of this type. When multiple occurrences of device are present, they are to be combined with a logical OR: at least one of the specified devices is used to produce the observation.; (xsd)device:(<Device>
|<DeviceDefinition>)>*
< The preferred name to be used when reporting the results of observations conforming to this ObservationDefinition.; (xsd)preferredReportName:string>?
[]< Units allowed for the valueQuantity element in the instance observations conforming to this ObservationDefinition. Binding: ucum-units (preferred, Codes identifying units of measure.); (xsd)permittedUnit:LabObservationDefinition.permittedUnit>*
[]< A set of qualified values associated with a context and a set of conditions - provides a range for quantitative and ordinal observations and a collection of value sets for qualitative observations.; (xsd)qualifiedValue:LabObservationDefinition.qualifiedValue>*
[]< This ObservationDefinition defines a group observation (e.g. a battery, a panel of tests, a set of vital sign measurements) that includes the target as a member of the group.; (xsd)hasMember:(<ObservationDefinition>
|<Questionnaire>)>*
[]< Some observations have multiple component observations, expressed as separate code value pairs.; (xsd)component:LabObservationDefinition.component>*🔗 Describes what will be observed. Sometimes this is called the observation "name". Binding: observation-codes (example, Codes identifying names of simple observations.)LabObservationDefinition.code(xsd)(doc)=
<#base:CodeableConcept>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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.; (xsd)coding:Coding>*
< 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.; (xsd)text:string>?
< 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.; (xsd)LOINC:LabObservationDefinition.code.LOINC>?🔗 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.LabObservationDefinition.code.LOINC(xsd)(doc)=
<#base:Coding>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< 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 be an absolute reference to some definition that establishes the system clearly and unambiguously. http://loinc.org; (xsd)system:uri>?
< 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.; (xsd)version:string>?
< 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).; (xsd)code>?
< A representation of the meaning of the code in the system, following the rules of the system.; (xsd)display:string>?
< 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.; (xsd)userSelected:boolean>?🔗 Some observations have multiple component observations, expressed as separate code value pairs.LabObservationDefinition.component(xsd)(doc)=
<#base:ObservationDefinition.component>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Describes what will be observed. Binding: observation-codes (example, Codes identifying names of simple observations.); (xsd)code:CodeableConcept>
[]< The data types allowed for the value element of the instance of this component observations. Binding: permitted-data-type (required, Permitted data type for observation value.); (xsd)permittedDataType:code>*
[]< Units allowed for the valueQuantity element in the instance observations conforming to this ObservationDefinition. Binding: ucum-units (preferred, Codes identifying units of measure.); (xsd)permittedUnit:Coding>*
[]< A set of qualified values associated with a context and a set of conditions - provides a range for quantitative and ordinal observations and a collection of value sets for qualitative observations.; (xsd)qualifiedValue:ObservationDefinition.qualifiedValue>*🔗 Units allowed for the valueQuantity element in the instance observations conforming to this ObservationDefinition. Binding: ucum-units (preferred, Codes identifying units of measure.)LabObservationDefinition.permittedUnit(xsd)(doc)=
<#base:Coding>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< 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 be an absolute reference to some definition that establishes the system clearly and unambiguously. http://unitsofmeasure.org; (xsd)system:uri>?
< 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.; (xsd)version:string>?
< 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).; (xsd)code>?
< A representation of the meaning of the code in the system, following the rules of the system.; (xsd)display:string>?
< 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.; (xsd)userSelected:boolean>?🔗 A set of qualified values associated with a context and a set of conditions - provides a range for quantitative and ordinal observations and a collection of value sets for qualitative observations.LabObservationDefinition.qualifiedValue(xsd)(doc)=
<#base:ObservationDefinition.qualifiedValue>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A concept defining the context for this set of qualified values. Binding: referencerange-meaning (extensible, ); (xsd)context:CodeableConcept>?
[]< The target population this set of qualified values applies to. If this element is not present then the global population is assumed. Binding: referencerange-appliesto (example, ); (xsd)appliesTo:CodeableConcept>*
< The gender this set of qualified values applies to. Binding: administrative-gender (required, ); (xsd)gender:code>?
< The age range this set of qualified values applies to. Some analytes vary greatly over age.; (xsd)age:Range>?
< The gestational age this set of qualified values applies to.; (xsd)gestationalAge:Range>?
< Text based condition for which the the set of qualified values is valid.; (xsd)condition:string>?
< The category of range of values for continuous or ordinal observations that match the criteria of this set of qualified values. Binding: observation-range-category (required, ); (xsd)rangeCategory:code>?
< The range of values defined for continuous or ordinal observations that match the criteria of this set of qualified values.; (xsd)range:Range>?
< The set of valid coded results for qualitative observations that match the criteria of this set of qualified values.; (xsd)validCodedValueSet:ValueSet*>?
< The set of normal coded results for qualitative observations that match the criteria of this set of qualified values.; (xsd)normalCodedValueSet:ValueSet*>?
< The set of abnormal coded results for qualitative observations that match the criteria of this set of qualified values.; (xsd)abnormalCodedValueSet:ValueSet*>?
< The set of critical coded results for qualitative observations that match the criteria of this set of qualified values.; (xsd)criticalCodedValueSet:ValueSet*>?🔗 This resource allows for the definition of some activity to be performed, independent of a particular patient, practitioner, or other performance context.LabProcedureDefinition(xsd)(doc)=
<#base:ActivityDefinition>
< The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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 its narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
< 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). Binding: all-languages (required, IETF language tag for a human language); (xsd)language:code>?
< 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 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.; (xsd)text:Narrative>?
[]< 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. 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.; (xsd)contained:Resource>*
[]< May be used to represent additional information that is not part of the basic definition of the resource. 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< An absolute URI that is used to identify this activity 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 activity definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the activity 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/R5/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/R5/resource.html#meta) element to indicate where the current master source of the resource can be found.; (xsd)url:uri>
[]< A formal identifier that is used to identify this activity 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 activity definition outside of FHIR, where it is not possible to use the logical URI.; (xsd)identifier:Identifier>*
< The identifier that is used to identify this version of the activity definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the activity 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 assets. There may be different activity 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 activity definition with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](http://hl7.org/fhir/R5/resource.html#bv-format).; (xsd)version:string>?
< Indicates the mechanism used to compare versions to determine which is more current. If set as a string, this is a FHIRPath expression that has two additional context variables passed in - %version1 and %version2 and will return a negative number if version1 is newer, a positive number if version2 and a 0 if the version ordering can't be successfully be determined. Binding: version-algorithm (extensible, ); (xsd)versionAlgorithm:(<Coding>
|<string>)>?
< A natural language name identifying the activity 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.; (xsd)name:string>?
< A short, descriptive, user-friendly title for the activity definition. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; (xsd)title:LabProcedureDefinition.title>?
< An explanatory or alternate title for the activity definition giving additional information about its content.; (xsd)subtitle:string>?
< The status of this activity definition. Enables tracking the life-cycle of the content. Allows filtering of activity definitions that are appropriate for use versus not.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization). Binding: publication-status (required, The lifecycle status of an artifact.); (xsd)status:code>
< A Boolean value to indicate that this activity definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Allows filtering of activity definitions that are appropriate for use versus not.; (xsd)experimental:boolean>?
< A code, group definition, or canonical reference that describes or identifies the intended subject of the activity being defined. 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. Note that the choice of canonical for the subject element was introduced in R4B to support pharmaceutical quality use cases. To ensure as much backwards-compatibility as possible, it is recommended to only use the new canonical type with these use cases. Binding: participant-resource-types (extensible, The possible types of subjects for an activity (E.g. Patient, Practitioner, Organization, Location, etc.).); (xsd)subject:(<AdministrableProductDefinition>
|<CodeableConcept>
|<EvidenceVariable>
|<Group>
|<ManufacturedItemDefinition>
|<MedicinalProductDefinition>
|<PackagedProductDefinition>
|<SubstanceDefinition>)>?
< The date (and optionally time) when the activity 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 activity definition changes. 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 activity 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](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)date:dateTime>?
< The name of the organization or individual responsible for the release and ongoing maintenance of the activity definition. Usually an organization but may be an individual. The publisher (or steward) of the activity definition is the organization or individual primarily responsible for the maintenance and upkeep of the activity 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 activity definition. This item SHOULD be populated unless the information is available from context.; (xsd)publisher:string>?
[]< 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.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)contact:LabProcedureDefinition.contact>*
< A free text natural language description of the laboratory procedure from a consumer's perspective. This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the activity 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 activity definition is presumed to be the predominant language in the place the activity definition was created).; (xsd)description:markdown>?
[]< 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 activity definition instances. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:UsageContext>*
[]< A legal or geographic region in which the activity definition is intended to be used. It may be possible for the activity 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.) Binding: jurisdiction (extensible, Countries and regions within which this artifact is targeted for use.); (xsd)jurisdiction:CodeableConcept>*
< Explanation of why this activity definition is needed and why it has been designed as it has. This element does not describe the usage of the activity 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 activity definition.; (xsd)purpose:markdown>?
< A detailed description of how the activity definition is used from a clinical perspective.; (xsd)usage:markdown>?
< A copyright statement relating to the activity definition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the activity definition. The short copyright declaration (e.g. (c) '2015+ xyz organization' should be sent in the copyrightLabel element.; (xsd)copyright:markdown>?
< A short string (<50 characters), suitable for inclusion in a page footer that identifies the copyright holder, effective period, and optionally whether rights are resctricted. (e.g. 'All rights reserved', 'Some rights reserved'). The (c) symbol should NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general 'copyright' element.; (xsd)copyrightLabel:string>?
< 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.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)approvalDate:date>?
< 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.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)lastReviewDate:date>?
< The period during which the activity definition content was or is planned to be in active use. The effective period for an activity definition determines when the content is applicable for usage and is independent of publication and review dates. For example, a activity intended to be used for the year 2016 might be published in 2015.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)effectivePeriod:LabProcedureDefinition.effectivePeriod>?
[]< Descriptive topics related to the content of the activity. Topics provide a high-level categorization of the activity that can be useful for filtering and searching. Examples could be lab specialties: chemistry, hormonology, hematology, bacteriology, virology ..
Other examples might list medical specialty of orderer: cardiology, dermatology, gastroenterology ... Binding: definition-topic (example, High-level categorization of the definition, used for searching, sorting, and filtering.); (xsd)topic:CodeableConcept>*
[]< An individiual or organization primarily involved in the creation and maintenance of the content.; (xsd)author:ContactDetail>*
[]< An individual or organization primarily responsible for internal coherence of the content.; (xsd)editor:ContactDetail>*
[]< An individual or organization asserted by the publisher to be primarily responsible for review of some aspect of the content. See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)reviewer:ContactDetail>*
[]< An individual or organization asserted by the publisher to be responsible for officially endorsing the content for use in some setting. See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)endorser:ContactDetail>*
[]< 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.; (xsd)relatedArtifact:RelatedArtifact>*
[]< A reference to a Library resource containing any formal logic used by the activity definition.; (xsd)library:Library*>*
< A description of the kind of resource the activity definition is representing. For example, a MedicationRequest, a ServiceRequest, or a CommunicationRequest. The kind element may only specify Request resource types to facilitate considering user input as part of processing the result of any automated clinical reasoning processes. To support creation of event resources, such as Observations, RiskAssessments, and DetectedIssues, use a Task resource with the focus of the task set to the event resource to be created. Note that the kind of resource to be created may determine what types of extensions are permitted. Binding: request-resource-types (required, The kind of activity the definition is describing.) ServiceRequest; (xsd)kind:code>
< A profile to which the target of the activity definition is expected to conform.; (xsd)profile:StructureDefinition*>?
< Detailed description of the type of activity; e.g. What lab test, what procedure, what kind of encounter. Tends to be less relevant for activities involving particular products. Binding: procedure-code (example, Detailed type of the activity; e.g. CBC.); (xsd)code:LabProcedureDefinition.code>?
< Indicates the level of authority/intentionality associated with the activity and where the request should fit into the workflow chain. Binding: request-intent (required, Codes indicating the degree of authority/intentionality associated with a request.); (xsd)intent:code>?
< Indicates how quickly the activity should be addressed with respect to other requests. Binding: request-priority (required, Identifies the level of importance to be assigned to actioning the request.); (xsd)priority:code>?
< Set this to true if the definition is to indicate that a particular activity should NOT be performed. If true, this element should be interpreted to reinforce a negative coding. For example NPO as a code with a doNotPerform of true would still indicate to NOT perform the action. This element is not intended to be used to communicate a decision support response to cancel an order in progress. That should be done with the "remove" type of a PlanDefinition or RequestOrchestration.; (xsd)doNotPerform:boolean>{0,0}
< The timing or frequency upon which the described activity is to occur. The intent of the timing element is to provide timing when the action should be performed. As a definitional resource, this timing is interpreted as part of an apply operation so that the timing of the result actions in a CarePlan or RequestOrchestration, for example, would be specified by evaluating the timing definition in the context of the apply and setting the resulting timing on the appropriate elements of the target resource. If the timing is an Age, the activity is expected to be performed when the subject is the given Age. When the timing is a Duration, the activity is expected to be performed within the specified duration from the apply. When the timing is a Range, it may be a range of Ages or Durations, providing a range for the expected timing of the resulting activity. When the timing is a Timing, it is establishing a schedule for the timing of the resulting activity.; (xsd)timing:(<Age>
|<Duration>
|<Range>
|<Timing>)>?
< If a CodeableConcept is present, it indicates the pre-condition for performing the service. For example "pain", "on flare-up", etc. Binding: medication-as-needed-reason (example, A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc.); (xsd)asNeeded:(<boolean>
|<CodeableConcept>)>?
< Identifies the facility where the laboratory procedure will occur, and where the specimens will be conveyed May be tha laboratory as a whole or its work area facility or a sector of it; (xsd)location:Location*>?
[]< Indicates who should participate in performing the action described.; (xsd)participant:LabProcedureDefinition.participant>*
< Identifies the food, drug or other product being consumed or supplied in the activity. Binding: medication-codes (example, Code describing the type of substance or medication.); (xsd)product:(<CodeableConcept>
|<Ingredient>
|<Medication>
|<Substance>
|<SubstanceDefinition>)>?
< Identifies the quantity expected to be consumed at once (per dose, per meal, etc.).; (xsd)quantity:SimpleQuantity>?
[]< Provides detailed dosage instructions in the same way that they are described for MedicationRequest resources. If a dosage instruction is used, the definition should not specify timing or quantity.; (xsd)dosage:Dosage>*
[]< Indicates the sites on the subject's body where the procedure should be performed (I.e. the target sites). Only used if not implicit in the code found in ServiceRequest.type. Binding: body-site (example, A code that identifies the anatomical location.); (xsd)bodySite:CodeableConcept>*
[]< Defines specimen requirements for the laboratory procedure (test or panel) to be performed.; (xsd)specimenRequirement:LabSpecimenDefinition*>*
[]< Defines observation requirements for the laboratory procedure (test or panel) to be performed, such as body weight or surface area.; (xsd)observationRequirement:InputObservationDefinition*>*
[]< Defines the observations that are expected to be produced by the laboratory procedure.; (xsd)observationResultRequirement:LabObservationDefinition*>*
< 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 if both a transform and dynamic values are specified, the dynamic values will be applied to the result of the transform.; (xsd)transform:StructureMap*>?
[]< Dynamic values that will be evaluated to produce values for elements of the resulting resource. For example, if the dosage of a medication must be computed based on the patient's weight, a dynamic value would be used to specify an expression that calculated the weight, and the path on the request resource that would contain the result. Dynamic values are applied in the order in which they are defined in the ActivityDefinition. Note that if both a transform and dynamic values are specified, the dynamic values will be applied to the result of the transform.; (xsd)dynamicValue:LabProcedureDefinition.dynamicValue>*🔗 Detailed description of the type of activity; e.g. What lab test, what procedure, what kind of encounter. Tends to be less relevant for activities involving particular products. Binding: procedure-code (example, Detailed type of the activity; e.g. CBC.)LabProcedureDefinition.code(xsd)(doc)=
<#base:CodeableConcept>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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.; (xsd)coding:Coding>*
< 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.; (xsd)text:string>?
< 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.; (xsd)orderCodeLOINC:LabProcedureDefinition.code.orderCodeLOINC>?🔗 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.LabProcedureDefinition.code.orderCodeLOINC(xsd)(doc)=
<#base:Coding>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< 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 be an absolute reference to some definition that establishes the system clearly and unambiguously. http://loinc.org; (xsd)system:uri>?
< 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.; (xsd)version:string>?
< 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).; (xsd)code>?
< A representation of the meaning of the code in the system, following the rules of the system.; (xsd)display:string>?
< 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.; (xsd)userSelected:boolean>?🔗 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.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).LabProcedureDefinition.contact(xsd)(doc)=
<#base:ContactDetail>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The name of an individual to contact. If there is no named individual, the telecom information is for the organization as a whole.; (xsd)name:string>?
[]< The contact details for the individual (if a name was provided) or the organization.; (xsd)telecom:ContactPoint>*🔗 Dynamic values that will be evaluated to produce values for elements of the resulting resource. For example, if the dosage of a medication must be computed based on the patient's weight, a dynamic value would be used to specify an expression that calculated the weight, and the path on the request resource that would contain the result. Dynamic values are applied in the order in which they are defined in the ActivityDefinition. Note that if both a transform and dynamic values are specified, the dynamic values will be applied to the result of the transform.LabProcedureDefinition.dynamicValue(xsd)(doc)=
<#base:ActivityDefinition.dynamicValue>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< 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](http://hl7.org/fhir/R5/fhirpath.html#simple) for full details). The path attribute contains a [Simple FHIRPath Subset](http://hl7.org/fhir/R5/fhirpath.html#simple) that allows path traversal, but not calculation.; (xsd)path:string>
< An expression specifying the value of the customized element. The expression may be inlined, or may be a reference to a named expression within a logic library referenced by the library element.; (xsd)expression:Expression>🔗 The period during which the activity definition content was or is planned to be in active use. The effective period for an activity definition determines when the content is applicable for usage and is independent of publication and review dates. For example, a activity intended to be used for the year 2016 might be published in 2015.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).LabProcedureDefinition.effectivePeriod(xsd)(doc)=
<#base:Period>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The start of the period. The boundary is inclusive. If the low element is missing, the meaning is that the low boundary is not known.; (xsd)start:dateTime>?
< The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. The end value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.; (xsd)end:dateTime>?🔗 Indicates who should participate in performing the action described.LabProcedureDefinition.participant(xsd)(doc)=
<#base:ActivityDefinition.participant>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type of participant in the action. Binding: action-participant-type (required, The type of participant in the activity.); (xsd)type:code>?
< The type of participant in the action.; (xsd)typeCanonical:CapabilityStatement*>?
< The type of participant in the action. When this element is a reference, it SHOULD be a reference to a definitional resource (for example, a location type, rather than a specific location).; (xsd)typeReference:(<CareTeam>
|<Device>
|<DeviceDefinition>
|<Endpoint>
|<Group>
|<HealthcareService>
|<Location>
|<Organization>
|<Patient>
|<Practitioner>
|<PractitionerRole>
|<RelatedPerson>)>?
< The role the participant should play in performing the described action. Binding: http://terminology.hl7.org/ValueSet/action-participant-role (example, Defines roles played by participants for the action.); (xsd)role:CodeableConcept>?
< Indicates how the actor will be involved in the action - author, reviewer, witness, etc. Binding: action-participant-function (example, ); (xsd)function:CodeableConcept>?🔗 A short, descriptive, user-friendly title for the activity definition. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.LabProcedureDefinition.title(xsd)(doc)=
<#base:string>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< The actual value; (xsd)value:string>?
[]< Language translation from base language of resource to another language.; (xsd)OtherTitle:Extension>*🔗 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. The LabServiceDefinition profile constrains the resource PlanDefinition to represent a laboratory diagnostic service made visible to clinicians: the potential consumers of this service.LabServiceDefinition(xsd)(doc)=
<#base:PlanDefinition>
< The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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 its narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
< 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). Binding: all-languages (required, IETF language tag for a human language); (xsd)language:code>?
< 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 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.; (xsd)text:Narrative>?
[]< 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. 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.; (xsd)contained:Resource>*
[]< An Extension; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< 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. 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/R5/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/R5/resource.html#meta) element to indicate where the current master source of the resource can be found.; (xsd)url:uri>?
[]< 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.; (xsd)identifier:Identifier>*
< 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]. The version SHOULD NOT contain a '#' - see [Business Version](http://hl7.org/fhir/R5/resource.html#bv-format).; (xsd)version:string>?
< Indicates the mechanism used to compare versions to determine which is more current. If set as a string, this is a FHIRPath expression that has two additional context variables passed in - %version1 and %version2 and will return a negative number if version1 is newer, a positive number if version2 and a 0 if the version ordering can't be successfully be determined. Binding: version-algorithm (extensible, ); (xsd)versionAlgorithm:(<Coding>
|<string>)>?
< 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.; (xsd)name:string>?
< 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.; (xsd)title:LabServiceDefinition.title>?
< An explanatory or alternate title for the plan definition giving additional information about its content.; (xsd)subtitle:string>?
< A high-level category for the plan definition that distinguishes the kinds of systems that would be interested in the plan definition. In this LabServiceDefiniton profile, PlanDefinition represents a laboratory service, which can be either a test or a panel.
A test is a single measurement performed on a material/digital specimen, producing generally one result (sometimes zero, sometime more).
A panel is a collection of tests and panels, performed on one or more material/digital specimens, and producing a collection of results.
Therefore, the type is bound to a value set {"test", "panel"}. The original value bound to this element with binding strength "extensible" does not contain appropriate values for laboratory diagnostic services. Binding: laboratory-service-type (extensible, ); (xsd)type:CodeableConcept>?
< 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.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization). Binding: publication-status (required, The lifecycle status of an artifact.); (xsd)status:code>
< 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. Allows filtering of plan definitions that are appropriate for use versus not.; (xsd)experimental:boolean>?
< 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. Note that the choice of canonical for the subject element was introduced in R4B to support pharmaceutical quality use cases. To ensure as much backwards-compatibility as possible, it is recommended to only use the new canonical type with these use cases. Binding: participant-resource-types (extensible, The possible types of subjects for a plan definition (E.g. Patient, Practitioner, Organization, Location, etc.).); (xsd)subject:(<AdministrableProductDefinition>
|<CodeableConcept>
|<EvidenceVariable>
|<Group>
|<ManufacturedItemDefinition>
|<MedicinalProductDefinition>
|<PackagedProductDefinition>
|<SubstanceDefinition>)>?
< 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. 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](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)date:dateTime>?
< The name of the organization or individual responsible for the release and ongoing maintenance of 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.; (xsd)publisher:string>?
[]< 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.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)contact:ContactDetail>*
< A free text natural language description of the plan definition from a consumer's perspective. This description provides details such as when this laboratory diagnostic service can be ordered, 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).; (xsd)description:LabServiceDefinition.description>?
[]< 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, in this LabServiceDefinition profile, all contexts apply to the defined laboratory service.; (xsd)useContext:UsageContext>*
[]< 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.
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.) Binding: jurisdiction (extensible, Countries and regions within which this artifact is targeted for use.); (xsd)jurisdiction:CodeableConcept>*
< 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.; (xsd)purpose:markdown>?
< A detailed description of how the laboratory diagnostic service is used from a clinical perspective.; (xsd)usage:markdown>?
< 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. The short copyright declaration (e.g. (c) '2015+ xyz organization' should be sent in the copyrightLabel element.; (xsd)copyright:markdown>?
< A short string (<50 characters), suitable for inclusion in a page footer that identifies the copyright holder, effective period, and optionally whether rights are resctricted. (e.g. 'All rights reserved', 'Some rights reserved'). The (c) symbol should NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general 'copyright' element.; (xsd)copyrightLabel:string>?
< 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.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)approvalDate:date>?
< 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.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)lastReviewDate:date>?
< 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 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](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)effectivePeriod:Period>?
[]< Descriptive topics related to the content of the laboratory service definition. Topics provide a high-level categorization of the definition that can be useful for filtering and searching. Some possible axes of categorization include laboratory specialty, kind of pathology, kind of biologic specimen tested, ... Topics are usually chosen by the laboratory or the organization owning the catalog Binding: definition-topic (example, High-level categorization of the definition, used for searching, sorting, and filtering.); (xsd)topic:CodeableConcept>*
[]< An individiual or organization primarily involved in the creation and maintenance of the content.; (xsd)author:ContactDetail>*
[]< An individual or organization primarily responsible for internal coherence of the content.; (xsd)editor:ContactDetail>*
[]< An individual or organization asserted by the publisher to be primarily responsible for review of some aspect of the content. See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)reviewer:ContactDetail>*
[]< An individual or organization asserted by the publisher to be responsible for officially endorsing the content for use in some setting. See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)endorser:ContactDetail>*
[]< 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.; (xsd)relatedArtifact:RelatedArtifact>*
[]< A reference to a Library resource containing any formal logic used by the plan definition.; (xsd)library:Library*>*
[]< 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.; (xsd)goal:LabServiceDefinition.goal>*
[]< Actors represent the individuals or groups involved in the execution of the defined set of activities.; (xsd)actor:LabServiceDefinition.actor>*
< The concrete action or group of actions conveyed by this laboratory diagnostic service The LabServiceDefinition profile constrains the content of PlanDefinition to be a single action at the top level. This action may be implemented by a single laboratory procedure referenced as an instance of ActivityDefinition, or may be decomposed into any level of logical groups of more granular actions, each leaf action referencing an ActivityDefinition.; (xsd)action:LabServiceDefinition.action>
< If a CodeableConcept is present, it indicates the pre-condition for performing the service. For example "pain", "on flare-up", etc. Binding: medication-as-needed-reason (example, A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc.); (xsd)asNeeded:(<boolean>
|<CodeableConcept>)>?
[]< This extension to PlanDefinition, MedicationKnowledge and DeviceDefinition conveys the reference to a catalog containing the extended resource; (xsd)CatalogReference>*
[]< Optional Extension Element - found in all resources.; (xsd)ServiceBillingCode>*
< An Extension; (xsd)BillingSummary>?
< An Extension; (xsd)ScheduleSummary>?
< An Extension; (xsd)LimitationSummary>?
< An Extension; (xsd)RegulatorySummary>?
< An Extension; (xsd)ResultInterpretationSummary>?
< The presence of this slice indicates that the service is open to laboratory order entry When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)Orderable:LabServiceDefinition.Orderable>?
< The presence of this slice indicates that the service may be added to an existing order by the pathologist after review of the preliminary results of this order When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)PathologistInitiative:LabServiceDefinition.PathologistInitiative>?
< The presence of this slice indicates that the service is restricted to one gender of subject (female or male) When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)OneGender:LabServiceDefinition.OneGender>?
< The presence of this slice indicates that the specimens used to perform this service will be kept in long-time storage and available for re-testing in the future When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)StoreSpecimen:LabServiceDefinition.StoreSpecimen>?
[]< 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.; (xsd)AgeRange:LabServiceDefinition.AgeRange>*
[]< Document that needs to be provided alongside the order for the laboratory service Examples of documents that should accompany an order for this service include patient consent for genetic testing, patient agreement for payment of a non-reimbursable service, insurance formal acceptation of a specific test (e.g. prenatal karyotyping) ...; (xsd)InputDocumentExpected:LabServiceDefinition.InputDocumentExpected>*
[]< The related artifact is another instance of PlanDefinition, which is a replacement for the current no longer usable laboratory service Each related artifact is either an attachment, or a reference to another resource, but not both.; (xsd)IsReplacedBy:LabServiceDefinition.IsReplacedBy>*
[]< The related artifact is another instance of PlanDefinition, representing a laboratory service orderable on its own, and which is also part of the current one, either systematically or reflexed by a trigger. Each related artifact is either an attachment, or a reference to another resource, but not both.; (xsd)Includes:LabServiceDefinition.Includes>*
[]< Related bibliographic references such as documentation, justification, or citation. Each related artifact is either an attachment, or a reference to another resource, but not both.; (xsd)Bibliography:LabServiceDefinition.Bibliography>*🔗 The concrete action or group of actions conveyed by this laboratory diagnostic service The LabServiceDefinition profile constrains the content of PlanDefinition to be a single action at the top level. This action may be implemented by a single laboratory procedure referenced as an instance of ActivityDefinition, or may be decomposed into any level of logical groups of more granular actions, each leaf action referencing an ActivityDefinition.LabServiceDefinition.action(xsd)(doc)=
<#base:PlanDefinition.action>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< An identifier that is unique within the PlanDefinition to allow linkage within the realized CarePlan and/or RequestOrchestration.; (xsd)linkId:string>?
< A user-visible prefix for the action. For example a section or item numbering such as 1. or A.; (xsd)prefix:string>?
< 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.; (xsd)title:string>?
< A brief description of the laboratory service, which may mention the analytical method(s) used by the laboratory; (xsd)description:markdown>?
< 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.; (xsd)textEquivalent:markdown>?
< Indicates how quickly this diagnostic panel or test should be performed. Binding: request-priority (required, Identifies the level of importance to be assigned to actioning the request.); (xsd)priority:code>?
< A code that provides meaning to the laboratory service Binding: action-code (example, Provides examples of actions to be performed.); (xsd)code:LabServiceDefinition.action.code>?
[]< 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. Binding: action-reason-code (example, Provides examples of reasons for actions to be performed.); (xsd)reason:CodeableConcept>*
[]< 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.; (xsd)documentation:RelatedArtifact>*
[]< 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.; (xsd)goalId:id>*
< 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. 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). Binding: participant-resource-types (extensible, The possible types of subjects for a plan definition (E.g. Patient, Practitioner, Organization, Location, etc.).); (xsd)subject:(<CodeableConcept>
|<Group>
|<Resource>)>?
[]< A description of when the action should be triggered. When multiple triggers are specified on an action, any triggering event invokes the action.; (xsd)trigger:TriggerDefinition>*
[]< 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.; (xsd)condition:LabServiceDefinition.action.condition>*
[]< Defines input data requirements for the action.; (xsd)input:LabServiceDefinition.action.input>*
[]< Defines the outputs of the action, if any.; (xsd)output:LabServiceDefinition.action.output>*
[]< 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.; (xsd)relatedAction:LabServiceDefinition.action.relatedAction>*
< An optional value describing when the action should be performed. The intent of the timing element is to provide timing when the action should be performed. As a definitional resource, this timing is interpreted as part of an apply operation so that the timing of the result actions in a CarePlan or RequestOrchestration, for example, would be specified by evaluating the timing definition in the context of the apply and setting the resulting timing on the appropriate elements of the target resource. If the timing is an Age, the activity is expected to be performed when the subject is the given Age. When the timing is a Duration, the activity is expected to be performed within the specified duration from the apply. When the timing is a Range, it may be a range of Ages or Durations, providing a range for the expected timing of the resulting activity. When the timing is a Timing, it is establishing a schedule for the timing of the resulting activity.; (xsd)timing:(<Age>
|<Duration>
|<Range>
|<Timing>)>?
< Identifies the facility where the action will occur; e.g. home, hospital, specific clinic, etc. May reference a specific clinical location or may just identify a type of location.; (xsd)location:Location*>?
[]< Indicates who should participate in performing the action described.; (xsd)participant:LabServiceDefinition.action.participant>*
< The type of action to perform (create, update, remove). Binding: action-type (extensible, The type of action to be performed.); (xsd)type:CodeableConcept>?
< Defines the grouping behavior for the action and its children. Binding: action-grouping-behavior (required, Defines organization behavior of a group.) logical-group; (xsd)groupingBehavior:code>?
< Defines the selection behavior for the action and its children. Binding: action-selection-behavior (required, Defines selection behavior of a group.); (xsd)selectionBehavior:code>?
< Defines the required behavior for the action. Binding: action-required-behavior (required, Defines expectations around whether an action or action group is required.); (xsd)requiredBehavior:code>?
< Defines whether the action should usually be preselected. Binding: action-precheck-behavior (required, Defines selection frequency behavior for an action or group.); (xsd)precheckBehavior:code>?
< Defines whether the action can be selected multiple times. Binding: action-cardinality-behavior (required, Defines behavior for an action or a group for how many times that item may be repeated.); (xsd)cardinalityBehavior:code>?
< A reference to an ActivityDefinition that describes the laboratory procedure to be performed, or to a PlanDefinition representing a child laboratory service, either embedded or reflexed by the current one. The definition is present only when there is no grouping of sub-actions; (xsd)definition:LabProcedureDefinition*>?
< 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.; (xsd)transform:StructureMap*>?
[]< 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.; (xsd)dynamicValue:LabServiceDefinition.action.dynamicValue>*
[]< 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.; (xsd)action:PlanDefinition.action>*
[]< A set of specimens requested as input by this laboratory service. The set is organized as a collection of one or more alternative groups (exactly one group should be chosen at specimen collection time). Each group describes one or more specimens that must all be provided, in case this group is the one chosen. In case this element has multiple occurrence, all occurrences apply: Each set of specimen requirements represented by an occurrence of action.extension:SpecimenRequested must be fulfilled for the service described by the PlanDefinition instance.; (xsd)SpecimenRequested>*
[]< This trigger introduces a reflex laboratory procedure (test or panel) represended by the ActivityDefinition referenced by the action.definition. The trigger is expressed as a named event, and may also be refined with a data requirement and a condition.; (xsd)Reflex:LabServiceDefinition.action.Reflex>*🔗 A code that provides meaning to the laboratory service Binding: action-code (example, Provides examples of actions to be performed.)LabServiceDefinition.action.code(xsd)(doc)=
<#base:CodeableConcept>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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.; (xsd)coding:Coding>*
< 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.; (xsd)text:string>?
< 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.; (xsd)orderCodeLOINC:LabServiceDefinition.action.code.orderCodeLOINC>?🔗 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.LabServiceDefinition.action.code.orderCodeLOINC(xsd)(doc)=
<#base:Coding>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< 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 be an absolute reference to some definition that establishes the system clearly and unambiguously. http://loinc.org; (xsd)system:uri>?
< 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.; (xsd)version:string>?
< 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).; (xsd)code>?
< A representation of the meaning of the code in the system, following the rules of the system.; (xsd)display:string>?
< 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.; (xsd)userSelected:boolean>?🔗 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.LabServiceDefinition.action.condition(xsd)(doc)=
<#base:PlanDefinition.action.condition>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The kind of condition. 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. Binding: action-condition-kind (required, Defines the kinds of conditions that can appear on actions.); (xsd)kind:code>
< 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.; (xsd)expression:Expression>?🔗 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.LabServiceDefinition.action.dynamicValue(xsd)(doc)=
<#base:PlanDefinition.action.dynamicValue>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< 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](http://hl7.org/fhir/R5/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/R5/fhirpath.html#simple) that allows path traversal, but not calculation.; (xsd)path:string>?
< An expression specifying the value of the customized element. The expression may be inlined or may be a reference to a named expression within a logic library referenced by the library element.; (xsd)expression:Expression>?🔗 Defines input data requirements for the action.LabServiceDefinition.action.input(xsd)(doc)=
<#base:PlanDefinition.action.input>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A human-readable label for the data requirement used to label data flows in BPMN or similar diagrams. Also provides a human readable label when rendering the data requirement that conveys its purpose to human readers.; (xsd)title:string>?
< Defines the data that is to be provided as input to the action.; (xsd)requirement:DataRequirement>?
< Points to an existing input or output element that provides data to this input. The relatedData element allows indicating that an input to a parent action is an input to specific child actions. It also allows the output of one action to be identified as the input to a different action; (xsd)relatedData:id>?🔗 Defines the outputs of the action, if any.LabServiceDefinition.action.output(xsd)(doc)=
<#base:PlanDefinition.action.output>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A human-readable label for the data requirement used to label data flows in BPMN or similar diagrams. Also provides a human readable label when rendering the data requirement that conveys its purpose to human readers.; (xsd)title:string>?
< Defines the data that results as output from the action.; (xsd)requirement:DataRequirement>?
< Points to an existing input or output element that is results as output from the action. The relatedData element allows indicating that the output of child action is also the output of a parent action. It also allows the input of one action to be identified as the output of a different action; (xsd)relatedData:string>?🔗 Indicates who should participate in performing the action described.LabServiceDefinition.action.participant(xsd)(doc)=
<#base:PlanDefinition.action.participant>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A reference to the id element of the actor who will participate in this action.; (xsd)actorId:string>?
< The type of participant in the action. Binding: action-participant-type (required, The type of participant in the activity.); (xsd)type:code>?
< The type of participant in the action.; (xsd)typeCanonical:CapabilityStatement*>?
< The type of participant in the action. When this element is a reference, it SHOULD be a reference to a definitional resource (for example, a location type, rather than a specific location).; (xsd)typeReference:(<CareTeam>
|<Device>
|<DeviceDefinition>
|<Endpoint>
|<Group>
|<HealthcareService>
|<Location>
|<Organization>
|<Patient>
|<Practitioner>
|<PractitionerRole>
|<RelatedPerson>)>?
< The role the participant should play in performing the described action. Binding: http://terminology.hl7.org/ValueSet/action-participant-role (example, Defines roles played by participants for the action.); (xsd)role:CodeableConcept>?
< Indicates how the actor will be involved in the action - author, reviewer, witness, etc. Binding: action-participant-function (example, ); (xsd)function:CodeableConcept>?🔗 This trigger introduces a reflex laboratory procedure (test or panel) represended by the ActivityDefinition referenced by the action.definition. The trigger is expressed as a named event, and may also be refined with a data requirement and a condition.LabServiceDefinition.action.Reflex(xsd)(doc)=
<#base:TriggerDefinition>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The type of triggering event. Binding: trigger-type (required, The type of trigger.) named-event; (xsd)type:code>
< The natural language expression of the trigger for the reflex laboratory procedure An event name can be provided for all event types, but is required for named events. If a name is provided for a type other than named events, it is considered to be a shorthand for the semantics described by the formal description of the event.; (xsd)name:string>
< A code that identifies the event.; (xsd)code:CodeableConcept>?
< A reference to a SubscriptionTopic resource that defines the event. If this element is provided, no other information about the trigger definition may be supplied.; (xsd)subscriptionTopic:SubscriptionTopic*>?
< The timing of the event (if this is a periodic trigger).; (xsd)timing:(<date>
|<dateTime>
|<Schedule>
|<Timing>)>?
[]< The triggering data of the event (if this is a data trigger). If more than one data is requirement is specified, then all the data requirements must be true. This element shall be present for any data type trigger.; (xsd)data:DataRequirement>*
< A boolean-valued expression that is evaluated in the context of the container of the trigger definition and returns whether or not the trigger fires. This element can be only be specified for data type triggers and provides additional semantics for the trigger. The context available within the condition is based on the type of data event. For all events, the current resource will be available as context. In addition, for modification events, the previous resource will also be available. The expression may be inlined, or may be a simple absolute URI, which is a reference to a named expression within a logic library referenced by a library element or extension within the containing resource. If the expression is a FHIR Path expression, it evaluates in the context of a resource of one of the type identified in the data requirement, and may also refer to the variable %previous for delta comparisons on events of type data-changed, data-modified, and data-deleted which will always have the same type.; (xsd)condition:Expression>?🔗 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.LabServiceDefinition.action.relatedAction(xsd)(doc)=
<#base:PlanDefinition.action.relatedAction>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The element id of the target related action.; (xsd)targetId:id>
< The relationship of the start of this action to the related action. Binding: action-relationship-type (required, Defines the types of relationships between actions.); (xsd)relationship:code>
< The relationship of the end of this action to the related action. Binding: action-relationship-type (required, Defines the types of relationships between actions.); (xsd)endRelationship:code>?
< A duration or range of durations to apply to the relationship. For example, 30-60 minutes before.; (xsd)offset:(<Duration>
|<Range>)>?🔗 Actors represent the individuals or groups involved in the execution of the defined set of activities.LabServiceDefinition.actor(xsd)(doc)=
<#base:PlanDefinition.actor>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A descriptive label for the actor.; (xsd)title:string>?
< A description of how the actor fits into the overall actions of the plan definition.; (xsd)description:markdown>?
[]< The characteristics of the candidates that could serve as the actor.; (xsd)option:LabServiceDefinition.actor.option>+🔗 The characteristics of the candidates that could serve as the actor.LabServiceDefinition.actor.option(xsd)(doc)=
<#base:PlanDefinition.actor.option>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type of participant in the action. Binding: action-participant-type (required, The type of participant in the activity.); (xsd)type:code>?
< The type of participant in the action.; (xsd)typeCanonical:CapabilityStatement*>?
< The type of participant in the action. When this element is a reference, it SHOULD be a reference to a definitional resource (for example, a location type, rather than a specific location).; (xsd)typeReference:(<CareTeam>
|<Device>
|<DeviceDefinition>
|<Endpoint>
|<Group>
|<HealthcareService>
|<Location>
|<Organization>
|<Patient>
|<Practitioner>
|<PractitionerRole>
|<RelatedPerson>)>?
< The role the participant should play in performing the described action. Binding: http://terminology.hl7.org/ValueSet/action-participant-role (example, ); (xsd)role:CodeableConcept>?🔗 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.LabServiceDefinition.AgeRange(xsd)(doc)=
<#base:UsageContext>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< A code that identifies the type of context being specified by this usage context. Binding: http://terminology.hl7.org/ValueSet/usage-context-type (extensible, A code that specifies a type of context being specified by a usage context.); (xsd)code:Coding>
< A value that defines the context specified in this context of use. The interpretation of the value is defined by the code. Binding: use-context (example, A code that defines the specific value for the context being specified.); (xsd)value:Range>🔗 Related bibliographic references such as documentation, justification, or citation. Each related artifact is either an attachment, or a reference to another resource, but not both.LabServiceDefinition.Bibliography(xsd)(doc)=
<#base:RelatedArtifact>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< kind of associated bibliographic artifact The presence of both sides of a relationship type (e.g. successor and predecessor) is required to support use cases where one side of a relationship is not represented in FHIR. However, this feature SHALL NOT be used to create bi-directional resource links in FHIR instances. Specifically, following the methodology of "new points to old" and "many points to one", when using related artifact elements to describe and reference FHIR resources, the type element SHALL be drawn from the fhir-related-artifact-type ValueSet. Binding: bibliography-artifact-type (required, ); (xsd)type:code>
[]< Provides additional classifiers of the related artifact. Binding: citation-artifact-classifier (example, Additional classifiers for the related artifact.); (xsd)classifier:CodeableConcept>*
< A short label that can be used to reference the citation from elsewhere in the containing artifact, such as a footnote index.; (xsd)label:string>?
< A brief description of the document or knowledge resource being referenced, suitable for display to a consumer.; (xsd)display:string>?
< A bibliographic citation for the related artifact. This text SHOULD be formatted according to an accepted citation format. Additional structured information about citations should be captured as extensions.; (xsd)citation:markdown>?
< The document being referenced, represented as an attachment. This is exclusive with the resource element.; (xsd)document:Attachment>?
< The related artifact, such as a library, value set, profile, or other knowledge resource. If the type is predecessor, this is a reference to the succeeding knowledge resource. If the type is successor, this is a reference to the prior knowledge resource.; (xsd)resource:Resource*>?
< The related artifact, if the artifact is not a canonical resource, or a resource reference to a canonical resource. If both resource and resourceReference are present, they SHOULD be consistent and reference the same resource. Although relatedArtifact is intended to support references to definitional resources, there are cases where non-definitional resources can be definitional (such as Location where the kind is mode). Related artifacts SHOULD be used to reference definitional resources, and profiles SHOULD be used to make that explicit for particular use cases.; (xsd)resourceReference:Resource*>?
< The publication status of the artifact being referred to. Binding: publication-status (required, Publication status of an artifact being referred to.); (xsd)publicationStatus:code>?
< The date of publication of the artifact being referred to.; (xsd)publicationDate:date>?🔗 A free text natural language description of the plan definition from a consumer's perspective. This description provides details such as when this laboratory diagnostic service can be ordered, 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).LabServiceDefinition.description(xsd)(doc)=
<#base:markdown>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< Primitive value for markdown; (xsd)value:string>?
[]< Translation of the description of the laboratory service in a specified language; (xsd)OtherDescription:Extension>*🔗 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.LabServiceDefinition.goal(xsd)(doc)=
<#base:PlanDefinition.goal>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Indicates a category the goal falls within. Binding: goal-category (example, Example codes for grouping goals for filtering or presentation.); (xsd)category:CodeableConcept>?
< 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. Binding: clinical-findings (example, Describes goals that can be achieved.); (xsd)description:CodeableConcept>
< Identifies the expected level of importance associated with reaching/sustaining the defined goal. Binding: goal-priority (preferred, Indicates the level of importance associated with reaching or sustaining a goal.); (xsd)priority:CodeableConcept>?
< The event after which the goal should begin being pursued. Binding: goal-start-event (example, Identifies the types of events that might trigger the start of a goal.); (xsd)start:CodeableConcept>?
[]< Identifies problems, conditions, issues, or concerns the goal is intended to address. Binding: condition-code (example, Identifies problems, conditions, issues, or concerns that goals may address.); (xsd)addresses:CodeableConcept>*
[]< 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.; (xsd)documentation:RelatedArtifact>*
[]< Indicates what should be done and within what timeframe.; (xsd)target:LabServiceDefinition.goal.target>*🔗 Indicates what should be done and within what timeframe.LabServiceDefinition.goal.target(xsd)(doc)=
<#base:PlanDefinition.goal.target>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The parameter whose value is to be tracked, e.g. body weight, blood pressure, or hemoglobin A1c level. Binding: observation-codes (example, Identifies types of parameters that can be tracked to determine goal achievement.); (xsd)measure:CodeableConcept>?
< 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. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the goal.target.measure defines a coded value.; (xsd)detail:(<boolean>
|<CodeableConcept>
|<integer>
|<Quantity>
|<Range>
|<Ratio>
|<string>)>?
< Indicates the timeframe after the start of the goal in which the goal should be met.; (xsd)due:Duration>?🔗 The related artifact is another instance of PlanDefinition, representing a laboratory service orderable on its own, and which is also part of the current one, either systematically or reflexed by a trigger. Each related artifact is either an attachment, or a reference to another resource, but not both.LabServiceDefinition.Includes(xsd)(doc)=
<#base:RelatedArtifact>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The type of relationship to the related artifact is composed-of, meaning that the related artifact is another standalone laboratory service, which is also included as a sub-service of the current one. The presence of both sides of a relationship type (e.g. successor and predecessor) is required to support use cases where one side of a relationship is not represented in FHIR. However, this feature SHALL NOT be used to create bi-directional resource links in FHIR instances. Specifically, following the methodology of "new points to old" and "many points to one", when using related artifact elements to describe and reference FHIR resources, the type element SHALL be drawn from the fhir-related-artifact-type ValueSet. Binding: related-artifact-type (required, The type of relationship to the related artifact.) composed-of; (xsd)type:code>
[]< Provides additional classifiers of the related artifact. Binding: citation-artifact-classifier (example, Additional classifiers for the related artifact.); (xsd)classifier:CodeableConcept>*
< A short label that can be used to reference the citation from elsewhere in the containing artifact, such as a footnote index.; (xsd)label:string>?
< A brief description of the document or knowledge resource being referenced, suitable for display to a consumer.; (xsd)display:string>?
< A bibliographic citation for the related artifact. This text SHOULD be formatted according to an accepted citation format. Additional structured information about citations should be captured as extensions.; (xsd)citation:markdown>?
< The document being referenced, represented as an attachment. This is exclusive with the resource element.; (xsd)document:Attachment>?
< The related resource, in this case a PlanDefinition constrained by the LabServiceDefinition profile If the type is predecessor, this is a reference to the succeeding knowledge resource. If the type is successor, this is a reference to the prior knowledge resource.; (xsd)resource:LabServiceDefinition*>
< The related artifact, if the artifact is not a canonical resource, or a resource reference to a canonical resource. If both resource and resourceReference are present, they SHOULD be consistent and reference the same resource. Although relatedArtifact is intended to support references to definitional resources, there are cases where non-definitional resources can be definitional (such as Location where the kind is mode). Related artifacts SHOULD be used to reference definitional resources, and profiles SHOULD be used to make that explicit for particular use cases.; (xsd)resourceReference:Resource*>?
< The publication status of the artifact being referred to. Binding: publication-status (required, Publication status of an artifact being referred to.); (xsd)publicationStatus:code>?
< The date of publication of the artifact being referred to.; (xsd)publicationDate:date>?🔗 Document that needs to be provided alongside the order for the laboratory service Examples of documents that should accompany an order for this service include patient consent for genetic testing, patient agreement for payment of a non-reimbursable service, insurance formal acceptation of a specific test (e.g. prenatal karyotyping) ...LabServiceDefinition.InputDocumentExpected(xsd)(doc)=
<#base:RelatedArtifact>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The type of relationship to the related artifact. The presence of both sides of a relationship type (e.g. successor and predecessor) is required to support use cases where one side of a relationship is not represented in FHIR. However, this feature SHALL NOT be used to create bi-directional resource links in FHIR instances. Specifically, following the methodology of "new points to old" and "many points to one", when using related artifact elements to describe and reference FHIR resources, the type element SHALL be drawn from the fhir-related-artifact-type ValueSet. Binding: related-artifact-type (required, The type of relationship to the related artifact.) depends-on; (xsd)type:code>
[]< Provides additional classifiers of the related artifact. Binding: citation-artifact-classifier (example, Additional classifiers for the related artifact.); (xsd)classifier:CodeableConcept>*
< Various kinds (or models) of documents may be expected as input to a laboratory service. This element provides an unambiguous short name for such a kind of document. Examples of kinds of documents expected include:
- the paper lab order scanned
- the statement of acceptation of the service by the insurance provider (e.g. for a prenatal karyotyping)
- the patient consent (e.g. for a genetic test)
- the patient insurance affiliation scanned; (xsd)label:string>
< A brief description of the document that need to be provided alongside the order of this laboratory service; (xsd)display:string>
< A bibliographic citation for the related artifact. This text SHOULD be formatted according to an accepted citation format. Additional structured information about citations should be captured as extensions.; (xsd)citation:markdown>?
< provides in the attachment a model for the kind of document expected The model can be encoded in base64 in the data sub-element, with its mime type encoded in the contentType sub-element, or it can be external, accessible through the url sub-element.; (xsd)document:LabServiceDefinition.InputDocumentExpected.document>?
< The related artifact, such as a library, value set, profile, or other knowledge resource. If the type is predecessor, this is a reference to the succeeding knowledge resource. If the type is successor, this is a reference to the prior knowledge resource.; (xsd)resource:Resource*>?
< The related artifact, if the artifact is not a canonical resource, or a resource reference to a canonical resource. If both resource and resourceReference are present, they SHOULD be consistent and reference the same resource. Although relatedArtifact is intended to support references to definitional resources, there are cases where non-definitional resources can be definitional (such as Location where the kind is mode). Related artifacts SHOULD be used to reference definitional resources, and profiles SHOULD be used to make that explicit for particular use cases.; (xsd)resourceReference:Resource*>?
< The publication status of the artifact being referred to. Binding: publication-status (required, Publication status of an artifact being referred to.); (xsd)publicationStatus:code>?
< The date of publication of the artifact being referred to.; (xsd)publicationDate:date>?🔗 provides in the attachment a model for the kind of document expected The model can be encoded in base64 in the data sub-element, with its mime type encoded in the contentType sub-element, or it can be external, accessible through the url sub-element.LabServiceDefinition.InputDocumentExpected.document(xsd)(doc)=
<#base:Attachment>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Identifies the type of the data in the attachment and allows a method to be chosen to interpret or render the data. Includes mime type parameters such as charset where appropriate. Binding: mimetypes (required, BCP 13 (RFCs 2045, 2046, 2047, 4288, 4289 and 2049)); (xsd)contentType:code>?
< The human language of the content. The value can be any valid value according to BCP 47. Binding: all-languages (required, IETF language tag for a human language.); (xsd)language:code>?
< The actual data of the attachment - a sequence of bytes, base64 encoded. The base64-encoded data SHALL be expressed in the same character set as the base resource XML or JSON.; (xsd)data:base64Binary>?
< used if the model of document is accessible externally If both data and url are provided, the url SHALL point to the same content as the data contains. Urls may be relative references or may reference transient locations such as a wrapping envelope using cid: though this has ramifications for using signatures. Relative URLs are interpreted relative to the service url, like a resource reference, rather than relative to the resource itself. If a URL is provided, it SHALL resolve to actual data.; (xsd)url>?
< The number of bytes of data that make up this attachment (before base64 encoding, if that is done). The number of bytes is redundant if the data is provided as a base64binary, but is useful if the data is provided as a url reference.; (xsd)size:integer64>?
< The calculated hash of the data using SHA-1. Represented using base64. The hash is calculated on the data prior to base64 encoding, if the data is based64 encoded. The hash is not intended to support digital signatures. Where protection against malicious threats a digital signature should be considered, see [Provenance.signature](http://hl7.org/fhir/R5/provenance-definitions.html#Provenance.signature) for mechanism to protect a resource with a digital signature.; (xsd)hash:base64Binary>?
< May be sufficient to specify the document expected, in cases where no pre-defined needs to be communicated to the orderer of the service. May sometimes be derived from the source filename.; (xsd)title:string>?
< The date that the attachment was first created.; (xsd)creation:dateTime>?
< Height of the image in pixels (photo/video).; (xsd)height:positiveInt>?
< Width of the image in pixels (photo/video).; (xsd)width:positiveInt>?
< The number of frames in a photo. This is used with a multi-page fax, or an imaging acquisition context that takes multiple slices in a single image, or an animated gif. If there is more than one frame, this SHALL have a value in order to alert interface software that a multi-frame capable rendering widget is required. if the number of frames is not supplied, the value may be unknown. Applications should not assume that there is only one frame unless it is explicitly stated.; (xsd)frames:positiveInt>?
< The duration of the recording in seconds - for audio and video. The duration might differ from occurrencePeriod if recording was paused.; (xsd)duration:decimal>?
< The number of pages when printed.; (xsd)pages:positiveInt>?🔗 The related artifact is another instance of PlanDefinition, which is a replacement for the current no longer usable laboratory service Each related artifact is either an attachment, or a reference to another resource, but not both.LabServiceDefinition.IsReplacedBy(xsd)(doc)=
<#base:RelatedArtifact>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< The type of relationship to the related artifact is successor, meaning that the related artifact is in this case another instance of PlanDefinition representing the laboratory service, which is substituted to the current instance. The presence of both sides of a relationship type (e.g. successor and predecessor) is required to support use cases where one side of a relationship is not represented in FHIR. However, this feature SHALL NOT be used to create bi-directional resource links in FHIR instances. Specifically, following the methodology of "new points to old" and "many points to one", when using related artifact elements to describe and reference FHIR resources, the type element SHALL be drawn from the fhir-related-artifact-type ValueSet. Binding: related-artifact-type (required, The type of relationship to the related artifact.) successor; (xsd)type:code>
[]< Provides additional classifiers of the related artifact. Binding: citation-artifact-classifier (example, Additional classifiers for the related artifact.); (xsd)classifier:CodeableConcept>*
< A short label that can be used to reference the citation from elsewhere in the containing artifact, such as a footnote index.; (xsd)label:string>?
< A brief description of the document or knowledge resource being referenced, suitable for display to a consumer.; (xsd)display:string>?
< A bibliographic citation for the related artifact. This text SHOULD be formatted according to an accepted citation format. Additional structured information about citations should be captured as extensions.; (xsd)citation:markdown>?
< The document being referenced, represented as an attachment. This is exclusive with the resource element.; (xsd)document:Attachment>?
< The related resource, in this case a PlanDefinition constrained by the LabServiceDefinition profile If the type is predecessor, this is a reference to the succeeding knowledge resource. If the type is successor, this is a reference to the prior knowledge resource.; (xsd)resource:LabServiceDefinition*>
< The related artifact, if the artifact is not a canonical resource, or a resource reference to a canonical resource. If both resource and resourceReference are present, they SHOULD be consistent and reference the same resource. Although relatedArtifact is intended to support references to definitional resources, there are cases where non-definitional resources can be definitional (such as Location where the kind is mode). Related artifacts SHOULD be used to reference definitional resources, and profiles SHOULD be used to make that explicit for particular use cases.; (xsd)resourceReference:Resource*>?
< The publication status of the artifact being referred to. Binding: publication-status (required, Publication status of an artifact being referred to.); (xsd)publicationStatus:code>?
< The date of publication of the artifact being referred to.; (xsd)publicationDate:date>?🔗 The presence of this slice indicates that the service is restricted to one gender of subject (female or male) When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.LabServiceDefinition.OneGender(xsd)(doc)=
<#base:UsageContext>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< A code that identifies the type of context being specified by this usage context. Binding: http://terminology.hl7.org/ValueSet/usage-context-type (extensible, A code that specifies a type of context being specified by a usage context.); (xsd)code:Coding>
< A value that defines the context specified in this context of use. The interpretation of the value is defined by the code. Binding: administrative-gender (required, ); (xsd)value:CodeableConcept>🔗 The presence of this slice indicates that the service is open to laboratory order entry When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.LabServiceDefinition.Orderable(xsd)(doc)=
<#base:UsageContext>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< A code that identifies the type of context being specified by this usage context. Binding: http://terminology.hl7.org/ValueSet/usage-context-type (extensible, A code that specifies a type of context being specified by a usage context.); (xsd)code:Coding>
< A value that defines the context specified in this context of use. The interpretation of the value is defined by the code. Binding: use-context (example, A code that defines the specific value for the context being specified.); (xsd)value:CodeableConcept>🔗 The presence of this slice indicates that the service may be added to an existing order by the pathologist after review of the preliminary results of this order When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.LabServiceDefinition.PathologistInitiative(xsd)(doc)=
<#base:UsageContext>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< A code that identifies the type of context being specified by this usage context. Binding: http://terminology.hl7.org/ValueSet/usage-context-type (extensible, A code that specifies a type of context being specified by a usage context.); (xsd)code:Coding>
< A value that defines the context specified in this context of use. The interpretation of the value is defined by the code. Binding: use-context (example, A code that defines the specific value for the context being specified.); (xsd)value:CodeableConcept>🔗 The presence of this slice indicates that the specimens used to perform this service will be kept in long-time storage and available for re-testing in the future When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.LabServiceDefinition.StoreSpecimen(xsd)(doc)=
<#base:UsageContext>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< A code that identifies the type of context being specified by this usage context. Binding: http://terminology.hl7.org/ValueSet/usage-context-type (extensible, A code that specifies a type of context being specified by a usage context.); (xsd)code:Coding>
< A value that defines the context specified in this context of use. The interpretation of the value is defined by the code. Binding: use-context (example, A code that defines the specific value for the context being specified.); (xsd)value:CodeableConcept>🔗 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.LabServiceDefinition.title(xsd)(doc)=
<#base:string>
< unique id for the element within a resource (for internal references); (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< The actual value; (xsd)value:string>?
[]< Expresses a synonym of the laboratory service in a specified language; (xsd)OtherTitle:Extension>*🔗 A kind of specimen with associated set of requirements.LabSpecimenDefinition(xsd)(doc)=
<#base:SpecimenDefinition>
< The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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 its narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
< 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). Binding: all-languages (required, IETF language tag for a human language); (xsd)language:code>?
< 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 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.; (xsd)text:Narrative>?
[]< 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. 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.; (xsd)contained:Resource>*
[]< May be used to represent additional information that is not part of the basic definition of the resource. 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< An absolute URL that is used to identify this SpecimenDefinition when it is referenced in a specification, model, design or an instance. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this SpecimenDefinition is (or will be) published. The URL SHOULD include the major version of the SpecimenDefinition. For more information see Technical and Business Versions. Can be a urn:uuid: or a urn:oid:, but real http: addresses are preferred. This is the URI that will be used when making canonical references to this resource.; (xsd)url:uri>?
< A business identifier assigned to this SpecimenDefinition.; (xsd)identifier:Identifier>?
< The identifier that is used to identify this version of the SpecimenDefinition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the SpecimenDefinition author and is not expected to be globally unique. There may be multiple different instances of a SpecimenDefinition that have the same identifier but different versions.; (xsd)version:string>?
< Indicates the mechanism used to compare versions to determine which is more current. If set as a string, this is a FHIRPath expression that has two additional context variables passed in - %version1 and %version2 and will return a negative number if version1 is newer, a positive number if version2 and a 0 if the version ordering can't be successfully be determined. Binding: version-algorithm (extensible, ); (xsd)versionAlgorithm:(<Coding>
|<string>)>?
< A natural language name identifying the {{title}}. 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.; (xsd)name:string>?
< A short, descriptive, user-friendly title for the SpecimenDefinition.; (xsd)title:string>?
[]< The canonical URL pointing to another FHIR-defined SpecimenDefinition that is adhered to in whole or in part by this definition.; (xsd)derivedFromCanonical:SpecimenDefinition*>*
[]< The URL pointing to an externally-defined type of specimen, guideline or other definition that is adhered to in whole or in part by this definition.; (xsd)derivedFromUri:uri>*
< The current state of theSpecimenDefinition. A nominal state-transition diagram can be found in the [Definition pattern](http://hl7.org/fhir/R5/definition.html#statemachine) documentation
Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization). Binding: publication-status (required, Codes identifying the status of a SpecimenDefinition resource.); (xsd)status:code>
< A flag to indicate that this SpecimenDefinition is not authored for genuine usage. Allows filtering of SpecimenDefinition that are appropriate for use vs. not.; (xsd)experimental:boolean>?
< A code or group definition that describes the intended subject from which this kind of specimen is to be collected. Examples: person, animal, device, water ….; (xsd)subject:(<CodeableConcept>
|<Group>)>?
< For draft definitions, indicates the date of initial creation. For active definitions, represents the date of activation. For withdrawn definitions, indicates the date of withdrawal. See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)date:dateTime>?
< Helps establish the "authority/credibility" of the SpecimenDefinition. May also allow for contact.; (xsd)publisher:string>?
[]< 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.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)contact:ContactDetail>*
< A free text natural language description of the SpecimenDefinition from the consumer's perspective. This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the module as conveyed in the text field of the resource itself. This item SHOULD be populated unless the information is available from context.; (xsd)description:markdown>?
[]< The content was developed with a focus and intent of supporting the contexts that are listed. These terms may be used to assist with indexing and searching of specimen definitions. When multiple usageContexts are specified, there is no expectation for whether all or any of the contexts apply.; (xsd)useContext:UsageContext>*
[]< A jurisdiction in which the SpecimenDefinition is intended to be used. 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.) Binding: jurisdiction (extensible, Codes for country, country subdivision and region for indicating where a resource is intended to be used.); (xsd)jurisdiction:CodeableConcept>*
< Explains why this SpecimeDefinition is needed and why it has been designed as it has. This element does not describe the usage of the SpecimenDefinition. Rather it is for 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 SpecimenDefinition.; (xsd)purpose:markdown>?
< Copyright statement relating to the SpecimenDefinition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the SpecimenDefinition.; (xsd)copyright:markdown>?
< A short string (<50 characters), suitable for inclusion in a page footer that identifies the copyright holder, effective period, and optionally whether rights are resctricted. (e.g. 'All rights reserved', 'Some rights reserved'). The (c) symbol should NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general 'copyright' element.; (xsd)copyrightLabel:string>?
< The date on which the asset content was approved by the publisher. Approval happens once when the content is officially approved for usage. The date may be more recent than the approval date because of minor changes / editorial corrections.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)approvalDate:date>?
< The date on which the asset content was last reviewed. Review happens periodically after that, but doesn't change the original approval date. If specified, this is usually after the approval date.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)lastReviewDate:date>?
< The period during which the SpecimenDefinition content was or is planned to be effective. The effective period for a SpecimenDefinition determines when the content is applicable for usage and is independent of publication and review dates.
See guidance around (not) making local changes to elements [here](http://hl7.org/fhir/R5/canonicalresource.html#localization).; (xsd)effectivePeriod:Period>?
< The kind of material to be collected. Binding: http://terminology.hl7.org/ValueSet/v2-0487 (example, The type of the specimen to be collected.); (xsd)typeCollected:CodeableConcept>?
[]< Preparation of the patient for specimen collection. Binding: prepare-patient-prior-specimen-collection (example, SCT descendants of 703763000 |Precondition value (qualifier value)|); (xsd)patientPreparation:CodeableConcept>*
< Time aspect of specimen collection (duration or offset).; (xsd)timeAspect:string>?
[]< The action to be performed for collecting the specimen. Binding: specimen-collection (example, SCT actions and procedures for specimen collection); (xsd)collection:CodeableConcept>*
[]< Specimen conditioned in a container as expected by the testing laboratory.; (xsd)typeTested:LabSpecimenDefinition.typeTested>*🔗 Specimen conditioned in a container as expected by the testing laboratory.LabSpecimenDefinition.typeTested(xsd)(doc)=
<#base:SpecimenDefinition.typeTested>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Primary of secondary specimen.; (xsd)isDerived:boolean>?
< The kind of specimen conditioned for testing expected by lab. Binding: http://terminology.hl7.org/ValueSet/v2-0487 (example, The type of specimen conditioned in a container for lab testing.); (xsd)type:CodeableConcept>?
< The preference for this type of conditioned specimen. Binding: specimen-contained-preference (required, Degree of preference of a type of conditioned specimen.); (xsd)preference:code>
< The specimen's container.; (xsd)container:LabSpecimenDefinition.typeTested.container>?
< Requirements for delivery and special handling of this kind of conditioned specimen.; (xsd)requirement:markdown>?
< The usual time that a specimen of this kind is retained after the ordered tests are completed, for the purpose of additional testing.; (xsd)retentionTime:Duration>?
< Specimen can be used by only one test or panel if the value is "true".; (xsd)singleUse:boolean>?
[]< Criterion for rejection of the specimen in its container by the laboratory. Binding: rejection-criteria (example, Criterion for rejection of the specimen by laboratory.); (xsd)rejectionCriterion:CodeableConcept>*
[]< Set of instructions for preservation/transport of the specimen at a defined temperature interval, prior the testing process.; (xsd)handling:LabSpecimenDefinition.typeTested.handling>*
[]< Where the specimen will be tested: e.g., lab, sector, device or any combination of these. Binding: diagnostic-service-sections (example, Codes specifying where the specimen will be tested.); (xsd)testingDestination:CodeableConcept>*🔗 The specimen's container.LabSpecimenDefinition.typeTested.container(xsd)(doc)=
<#base:SpecimenDefinition.typeTested.container>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type of material of the container. Examples: glass, plastic, metal. Binding: container-material (example, SCT 32039001 |Glass|, 61088005 |Plastic|, 425620007 |Metal|); (xsd)material:CodeableConcept>?
< The type of container used to contain this kind of specimen. Binding: specimen-container-type (example, SCT descendants of 706041008 |Device for body fluid and tissue collection/transfer/processing (physical object)|); (xsd)type:CodeableConcept>?
< Color of container cap. Binding: container-cap (example, Color of the container cap.); (xsd)cap:CodeableConcept>?
< The textual description of the kind of container.; (xsd)description:markdown>?
< The capacity (volume or other measure) of this kind of container.; (xsd)capacity:SimpleQuantity>?
< The minimum volume to be conditioned in the container.; (xsd)minimumVolume:(<SimpleQuantity>
|<string>)>?
[]< Substance introduced in the kind of container to preserve, maintain or enhance the specimen. Examples: Formalin, Citrate, EDTA.; (xsd)additive:LabSpecimenDefinition.typeTested.container.additive>*
< Special processing that should be applied to the container for this kind of specimen.; (xsd)preparation:markdown>?🔗 Substance introduced in the kind of container to preserve, maintain or enhance the specimen. Examples: Formalin, Citrate, EDTA.LabSpecimenDefinition.typeTested.container.additive(xsd)(doc)=
<#base:SpecimenDefinition.typeTested.container.additive>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< Substance introduced in the kind of container to preserve, maintain or enhance the specimen. Examples: Formalin, Citrate, EDTA. Binding: http://terminology.hl7.org/ValueSet/v2-0371 (example, Substance added to specimen container.); (xsd)additive:(<CodeableConcept>
|<SubstanceDefinition>)>🔗 Set of instructions for preservation/transport of the specimen at a defined temperature interval, prior the testing process.LabSpecimenDefinition.typeTested.handling(xsd)(doc)=
<#base:SpecimenDefinition.typeTested.handling>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< It qualifies the interval of temperature, which characterizes an occurrence of handling. Conditions that are not related to temperature may be handled in the instruction element. Binding: handling-condition (example, Set of handling instructions prior testing of the specimen.); (xsd)temperatureQualifier:CodeableConcept>?
< The temperature interval for this set of handling instructions.; (xsd)temperatureRange:Range>?
< The maximum time interval of preservation of the specimen with these conditions.; (xsd)maxDuration:Duration>?
< Additional textual instructions for the preservation or transport of the specimen. For instance, 'Protect from light exposure'.; (xsd)instruction:markdown>?🔗 An ExtensionLimitationSummary(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/order-catalog/StructureDefinition/LimitationSummary; (xsd)url:string>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).; (xsd)value:string>?🔗 An ExtensionRegulatorySummary(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/order-catalog/StructureDefinition/RegulatorySummary; (xsd)url:string>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).; (xsd)value:string>?🔗 An ExtensionResultInterpretationSummary(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/order-catalog/StructureDefinition/ResultInterpretationSummary; (xsd)url:string>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).; (xsd)value:markdown>?🔗 Optional Extension Element - found in all resources.ServiceBillingCode(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/order-catalog/StructureDefinition/ServiceBillingCode; (xsd)url:string>
(<valueCodeableConcept:CodeableConcept>
|<valueResource:Resource>)?
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).; (xsd)valueCodeableConcept:CodeableConcept>?
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).; (xsd)valueReference:LabChargeItemDefinition*>?🔗 An ExtensionScheduleSummary(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/order-catalog/StructureDefinition/ScheduleSummary; (xsd)url:string>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).; (xsd)value:string>?🔗 An ExtensionSpecimenRequested(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/order-catalog/StructureDefinition/SpecimenRequested; (xsd)url:string>
(<valueAddress:Address>
|<valueAge:Age>
|<valueAnnotation:Annotation>
|<valueAttachment:Attachment>
|<valueAvailability:Availability>
|<valueBase64Binary:base64Binary>
|<valueBoolean:boolean>
|<valueCode:code>
|<valueCodeableConcept:CodeableConcept>
|<valueCoding:Coding>
|<valueContactDetail:ContactDetail>
|<valueContactPoint:ContactPoint>
|<valueCount:Count>
|<valueDataRequirement:DataRequirement>
|<valueDate:date>
|<valueDateTime:dateTime>
|<valueDecimal:decimal>
|<valueDistance:Distance>
|<valueDosage:Dosage>
|<valueDuration:Duration>
|<valueExpression:Expression>
|<valueExtendedContactDetail:ExtendedContactDetail>
|<valueHumanName:HumanName>
|<valueId:id>
|<valueIdentifier:Identifier>
|<valueInstant:instant>
|<valueInteger:integer>
|<valueInteger64:integer64>
|<valueMarkdown:markdown>
|<valueMeta:Meta>
|<valueMoney:Money>
|<valueOid:oid>
|<valueParameterDefinition:ParameterDefinition>
|<valuePeriod:Period>
|<valuePositiveInt:positiveInt>
|<valueQuantity:Quantity>
|<valueRange:Range>
|<valueRatio:Ratio>
|<valueRatioRange:RatioRange>
|<valueRelatedArtifact:RelatedArtifact>
|<valueResource:Resource>
|<valueSampledData:SampledData>
|<valueSignature:Signature>
|<valueString:string>
|<valueTime:time>
|<valueTiming:Timing>
|<valueTriggerDefinition:TriggerDefinition>
|<valueUnsignedInt:unsignedInt>
|<valueUri:uri>
|<valueUrl:url>
|<valueUsageContext:UsageContext>
|<valueUuid:uuid>){0,0}
[]< A group of specimens requested that must all be provided in case this group is chosen at specimen collection time. In case multiple groups are defined, these groups are mutually exclusive: one and only one group must be chosen at specimen collection time.; (xsd)ExclusiveGroup:SpecimenRequested.ExclusiveGroup>+🔗 A group of specimens requested that must all be provided in case this group is chosen at specimen collection time. In case multiple groups are defined, these groups are mutually exclusive: one and only one group must be chosen at specimen collection time.SpecimenRequested.ExclusiveGroup(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< An Extension; (xsd)extension:Extension>*
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. ExclusiveGroup; (xsd)url:string>
(<valueAddress:Address>
|<valueAge:Age>
|<valueAnnotation:Annotation>
|<valueAttachment:Attachment>
|<valueAvailability:Availability>
|<valueBase64Binary:base64Binary>
|<valueBoolean:boolean>
|<valueCode:code>
|<valueCodeableConcept:CodeableConcept>
|<valueCoding:Coding>
|<valueContactDetail:ContactDetail>
|<valueContactPoint:ContactPoint>
|<valueCount:Count>
|<valueDataRequirement:DataRequirement>
|<valueDate:date>
|<valueDateTime:dateTime>
|<valueDecimal:decimal>
|<valueDistance:Distance>
|<valueDosage:Dosage>
|<valueDuration:Duration>
|<valueExpression:Expression>
|<valueExtendedContactDetail:ExtendedContactDetail>
|<valueHumanName:HumanName>
|<valueId:id>
|<valueIdentifier:Identifier>
|<valueInstant:instant>
|<valueInteger:integer>
|<valueInteger64:integer64>
|<valueMarkdown:markdown>
|<valueMeta:Meta>
|<valueMoney:Money>
|<valueOid:oid>
|<valueParameterDefinition:ParameterDefinition>
|<valuePeriod:Period>
|<valuePositiveInt:positiveInt>
|<valueQuantity:Quantity>
|<valueRange:Range>
|<valueRatio:Ratio>
|<valueRatioRange:RatioRange>
|<valueRelatedArtifact:RelatedArtifact>
|<valueResource:Resource>
|<valueSampledData:SampledData>
|<valueSignature:Signature>
|<valueString:string>
|<valueTime:time>
|<valueTiming:Timing>
|<valueTriggerDefinition:TriggerDefinition>
|<valueUnsignedInt:unsignedInt>
|<valueUri:uri>
|<valueUrl:url>
|<valueUsageContext:UsageContext>
|<valueUuid:uuid>){0,0}
[]< A reference to a SpecimenDefinition resource representing the material When multiple materials are present under an exclusive group, all are requested.; (xsd)Material:SpecimenRequested.ExclusiveGroup.Material>+🔗 A reference to a SpecimenDefinition resource representing the material When multiple materials are present under an exclusive group, all are requested.SpecimenRequested.ExclusiveGroup.Material(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. Material; (xsd)url:string>
< A reference to SpecimenDefinition as constrained by the LabSpecimenDefinition profile; (xsd)value:LabSpecimenDefinition*>?🔗 A single issue - either an indication, contraindication, interaction or an undesirable effect for a medicinal product, medication, device or procedure.UndesirableEffectDefinition(xsd)(doc)=
<#base:ClinicalUseDefinition>
< The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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 its narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
< 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). Binding: all-languages (required, IETF language tag for a human language); (xsd)language:code>?
< 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 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.; (xsd)text:Narrative>?
[]< 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. 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.; (xsd)contained:Resource>*
[]< May be used to represent additional information that is not part of the basic definition of the resource. 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Business identifier for this issue.; (xsd)identifier:Identifier>*
< indication | contraindication | interaction | undesirable-effect | warning. Binding: clinical-use-definition-type (required, Overall defining type of this clinical use definition.) undesirable-effect; (xsd)type:code>
[]< A categorisation of the issue, primarily for dividing warnings into subject heading areas such as "Pregnancy and Lactation", "Overdose", "Effects on Ability to Drive and Use Machines". Binding: clinical-use-definition-category (preferred, A categorisation for a clinical use information item.); (xsd)category:CodeableConcept>*
[]< The medication, product, substance, device, procedure etc. for which this is an indication.; (xsd)subject:(<ActivityDefinition>
|<BiologicallyDerivedProduct>
|<Device>
|<DeviceDefinition>
|<Medication>
|<MedicinalProductDefinition>
|<NutritionProduct>
|<PlanDefinition>
|<Substance>)>*
< Whether this is a current issue or one that has been retired etc. Binding: publication-status (preferred, The lifecycle status of an artifact.); (xsd)status:CodeableConcept>?
< Specifics for when this is a contraindication.; (xsd)contraindication:UndesirableEffectDefinition.contraindication>{0,0}
< Specifics for when this is an indication.; (xsd)indication:UndesirableEffectDefinition.indication>{0,0}
< Specifics for when this is an interaction.; (xsd)interaction:UndesirableEffectDefinition.interaction>{0,0}
[]< The population group to which this applies.; (xsd)population:Group*>*
[]< Logic used by the clinical use definition.; (xsd)library:Library*>*
< Describe the possible undesirable effects (negative outcomes) from the use of the medicinal product as treatment.; (xsd)undesirableEffect:UndesirableEffectDefinition.undesirableEffect>
< A critical piece of information about environmental, health or physical risks or hazards that serve as caution to the user. For example 'Do not operate heavy machinery', 'May cause drowsiness', or 'Get medical advice/attention if you feel unwell'.; (xsd)warning:UndesirableEffectDefinition.warning>{0,0}🔗 Specifics for when this is a contraindication.UndesirableEffectDefinition.contraindication(xsd)(doc)=
<#base:ClinicalUseDefinition.contraindication>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The situation that is being documented as contraindicating against this item. Binding: disease-symptom-procedure (example, A symptom, disease or procedure.); (xsd)diseaseSymptomProcedure:ObservationDefinition*>?
< The status of the disease or symptom for the contraindication, for example "chronic" or "metastatic". Binding: disease-status (example, The status of a disease or symptom.); (xsd)diseaseStatus:ObservationDefinition*>?
[]< A comorbidity (concurrent condition) or coinfection. Binding: disease-symptom-procedure (example, A symptom, disease or procedure.); (xsd)comorbidity:ObservationDefinition*>*
[]< The indication which this is a contraidication for.; (xsd)indication:ClinicalUseDefinition*>*
< An expression that returns true or false, indicating whether the indication is applicable or not, after having applied its other elements. The expression may be inlined or may be a reference to a named expression within a logic library referenced by the library element.; (xsd)applicability:Expression>?
[]< Information about the use of the medicinal product in relation to other therapies described as part of the contraindication.; (xsd)otherTherapy:UndesirableEffectDefinition.contraindication.otherTherapy>*🔗 Information about the use of the medicinal product in relation to other therapies described as part of the contraindication.UndesirableEffectDefinition.contraindication.otherTherapy(xsd)(doc)=
<#base:ClinicalUseDefinition.contraindication.otherTherapy>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type of relationship between the medicinal product indication or contraindication and another therapy. Binding: therapy-relationship-type (preferred, Classification of relationship between a therapy and a contraindication or an indication.); (xsd)relationshipType:CodeableConcept>
< Reference to a specific medication (active substance, medicinal product or class of products, biological, food etc.) as part of an indication or contraindication. Binding: therapy (example, A therapy.); (xsd)treatment:(<ActivityDefinition>
|<BiologicallyDerivedProduct>
|<Medication>
|<MedicinalProductDefinition>
|<NutritionProduct>
|<Substance>
|<SubstanceDefinition>)>🔗 Specifics for when this is an indication.UndesirableEffectDefinition.indication(xsd)(doc)=
<#base:ClinicalUseDefinition.indication>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The situation that is being documented as an indicaton for this item. Binding: disease-symptom-procedure (example, A symptom, disease or procedure.); (xsd)diseaseSymptomProcedure:ObservationDefinition*>?
< The status of the disease or symptom for the indication, for example "chronic" or "metastatic". Binding: disease-status (example, The status of a disease or symptom.); (xsd)diseaseStatus:ObservationDefinition*>?
[]< A comorbidity (concurrent condition) or coinfection as part of the indication. Binding: disease-symptom-procedure (example, A symptom, disease or procedure.); (xsd)comorbidity:ObservationDefinition*>*
< The intended effect, aim or strategy to be achieved. Binding: product-intended-use (preferred, The overall intended use of a product.); (xsd)intendedEffect:ObservationDefinition*>?
< Timing or duration information, that may be associated with use with the indicated condition e.g. Adult patients suffering from myocardial infarction (from a few days until less than 35 days), ischaemic stroke (from 7 days until less than 6 months).; (xsd)duration:(<Range>
|<string>)>?
[]< An unwanted side effect or negative outcome that may happen if you use the drug (or other subject of this resource) for this indication.; (xsd)undesirableEffect:ClinicalUseDefinition*>*
< An expression that returns true or false, indicating whether the indication is applicable or not, after having applied its other elements. The expression may be inlined or may be a reference to a named expression within a logic library referenced by the library element.; (xsd)applicability:Expression>?
[]< Information about the use of the medicinal product in relation to other therapies described as part of the indication.; (xsd)otherTherapy:ClinicalUseDefinition.contraindication.otherTherapy>*🔗 Specifics for when this is an interaction.UndesirableEffectDefinition.interaction(xsd)(doc)=
<#base:ClinicalUseDefinition.interaction>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< The specific medication, product, food, substance etc. or laboratory test that interacts.; (xsd)interactant:UndesirableEffectDefinition.interaction.interactant>*
< The type of the interaction e.g. drug-drug interaction, drug-food interaction, drug-lab test interaction. Binding: interaction-type (example, A categorisation for an interaction between two substances.); (xsd)type:CodeableConcept>?
< The effect of the interaction, for example "reduced gastric absorption of primary medication". Binding: interaction-effect (example, A interaction effect of clinical use of a medication or other substance.); (xsd)effect:ObservationDefinition*>?
< The incidence of the interaction, e.g. theoretical, observed. Binding: interaction-incidence (example, A categorisation for incidence of occurence of an interaction.); (xsd)incidence:CodeableConcept>?
[]< Actions for managing the interaction. Binding: interaction-management (example, A type of management for an interaction of a medication or other substance.); (xsd)management:CodeableConcept>*🔗 The specific medication, product, food, substance etc. or laboratory test that interacts.UndesirableEffectDefinition.interaction.interactant(xsd)(doc)=
<#base:ClinicalUseDefinition.interaction.interactant>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The specific medication, product, food, substance etc. or laboratory test that interacts. Binding: interactant (example, An interactant - a substance that may have a clinically significant effect on another.); (xsd)item:(<BiologicallyDerivedProduct>
|<CodeableConcept>
|<Medication>
|<MedicinalProductDefinition>
|<NutritionProduct>
|<ObservationDefinition>
|<Substance>)>🔗 Describe the possible undesirable effects (negative outcomes) from the use of the medicinal product as treatment.UndesirableEffectDefinition.undesirableEffect(xsd)(doc)=
<#base:ClinicalUseDefinition.undesirableEffect>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The situation in which the undesirable effect may manifest. Binding: undesirable-effect-symptom (example, An undesirable effect of clinical use.); (xsd)symptomConditionEffect:ObservationDefinition*>?
< High level classification of the effect. Binding: undesirable-effect-classification (example, A categorisation for an undesirable effect.); (xsd)classification:CodeableConcept>?
< How often the effect is seen. Binding: undesirable-effect-frequency (example, A categorisation for a frequency of occurence of an undesirable effect.); (xsd)frequencyOfOccurrence:CodeableConcept>?🔗 A critical piece of information about environmental, health or physical risks or hazards that serve as caution to the user. For example 'Do not operate heavy machinery', 'May cause drowsiness', or 'Get medical advice/attention if you feel unwell'.UndesirableEffectDefinition.warning(xsd)(doc)=
<#base:ClinicalUseDefinition.warning>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A textual definition of this warning, with formatting.; (xsd)description:markdown>?
< A coded or unformatted textual definition of this warning. Binding: warning-type (example, Classification of warning type.); (xsd)code:CodeableConcept>?🔗 The period in which the Composition is valid (for Order Catalog profiles), with optional start and end dates.ValidityPeriod(xsd)(doc)=
<#base:Extension>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
< Source of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/order-catalog/StructureDefinition/ValidityPeriod; (xsd)url:string>
< Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).; (xsd)value:Period>🔗 A single issue - either an indication, contraindication, interaction or an undesirable effect for a medicinal product, medication, device or procedure.WarningDefinition(xsd)(doc)=
<#base:ClinicalUseDefinition>
< The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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.; (xsd)id:string>?
< 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.; (xsd)meta:Meta>?
< 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 its narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
< 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). Binding: all-languages (required, IETF language tag for a human language); (xsd)language:code>?
< 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 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.; (xsd)text:Narrative>?
[]< 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. 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.; (xsd)contained:Resource>*
[]< May be used to represent additional information that is not part of the basic definition of the resource. 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< Business identifier for this issue.; (xsd)identifier:Identifier>*
< indication | contraindication | interaction | undesirable-effect | warning. Binding: clinical-use-definition-type (required, Overall defining type of this clinical use definition.) warning; (xsd)type:code>
[]< A categorisation of the issue, primarily for dividing warnings into subject heading areas such as "Pregnancy and Lactation", "Overdose", "Effects on Ability to Drive and Use Machines". Binding: clinical-use-definition-category (preferred, A categorisation for a clinical use information item.); (xsd)category:CodeableConcept>*
[]< The medication, product, substance, device, procedure etc. for which this is an indication.; (xsd)subject:(<ActivityDefinition>
|<BiologicallyDerivedProduct>
|<Device>
|<DeviceDefinition>
|<Medication>
|<MedicinalProductDefinition>
|<NutritionProduct>
|<PlanDefinition>
|<Substance>)>*
< Whether this is a current issue or one that has been retired etc. Binding: publication-status (preferred, The lifecycle status of an artifact.); (xsd)status:CodeableConcept>?
< Specifics for when this is a contraindication.; (xsd)contraindication:WarningDefinition.contraindication>{0,0}
< Specifics for when this is an indication.; (xsd)indication:WarningDefinition.indication>{0,0}
< Specifics for when this is an interaction.; (xsd)interaction:WarningDefinition.interaction>{0,0}
[]< The population group to which this applies.; (xsd)population:Group*>*
[]< Logic used by the clinical use definition.; (xsd)library:Library*>*
< Describe the possible undesirable effects (negative outcomes) from the use of the medicinal product as treatment.; (xsd)undesirableEffect:WarningDefinition.undesirableEffect>{0,0}
< A critical piece of information about environmental, health or physical risks or hazards that serve as caution to the user. For example 'Do not operate heavy machinery', 'May cause drowsiness', or 'Get medical advice/attention if you feel unwell'.; (xsd)warning:WarningDefinition.warning>🔗 Specifics for when this is a contraindication.WarningDefinition.contraindication(xsd)(doc)=
<#base:ClinicalUseDefinition.contraindication>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The situation that is being documented as contraindicating against this item. Binding: disease-symptom-procedure (example, A symptom, disease or procedure.); (xsd)diseaseSymptomProcedure:ObservationDefinition*>?
< The status of the disease or symptom for the contraindication, for example "chronic" or "metastatic". Binding: disease-status (example, The status of a disease or symptom.); (xsd)diseaseStatus:ObservationDefinition*>?
[]< A comorbidity (concurrent condition) or coinfection. Binding: disease-symptom-procedure (example, A symptom, disease or procedure.); (xsd)comorbidity:ObservationDefinition*>*
[]< The indication which this is a contraidication for.; (xsd)indication:ClinicalUseDefinition*>*
< An expression that returns true or false, indicating whether the indication is applicable or not, after having applied its other elements. The expression may be inlined or may be a reference to a named expression within a logic library referenced by the library element.; (xsd)applicability:Expression>?
[]< Information about the use of the medicinal product in relation to other therapies described as part of the contraindication.; (xsd)otherTherapy:WarningDefinition.contraindication.otherTherapy>*🔗 Information about the use of the medicinal product in relation to other therapies described as part of the contraindication.WarningDefinition.contraindication.otherTherapy(xsd)(doc)=
<#base:ClinicalUseDefinition.contraindication.otherTherapy>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The type of relationship between the medicinal product indication or contraindication and another therapy. Binding: therapy-relationship-type (preferred, Classification of relationship between a therapy and a contraindication or an indication.); (xsd)relationshipType:CodeableConcept>
< Reference to a specific medication (active substance, medicinal product or class of products, biological, food etc.) as part of an indication or contraindication. Binding: therapy (example, A therapy.); (xsd)treatment:(<ActivityDefinition>
|<BiologicallyDerivedProduct>
|<Medication>
|<MedicinalProductDefinition>
|<NutritionProduct>
|<Substance>
|<SubstanceDefinition>)>🔗 Specifics for when this is an indication.WarningDefinition.indication(xsd)(doc)=
<#base:ClinicalUseDefinition.indication>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The situation that is being documented as an indicaton for this item. Binding: disease-symptom-procedure (example, A symptom, disease or procedure.); (xsd)diseaseSymptomProcedure:ObservationDefinition*>?
< The status of the disease or symptom for the indication, for example "chronic" or "metastatic". Binding: disease-status (example, The status of a disease or symptom.); (xsd)diseaseStatus:ObservationDefinition*>?
[]< A comorbidity (concurrent condition) or coinfection as part of the indication. Binding: disease-symptom-procedure (example, A symptom, disease or procedure.); (xsd)comorbidity:ObservationDefinition*>*
< The intended effect, aim or strategy to be achieved. Binding: product-intended-use (preferred, The overall intended use of a product.); (xsd)intendedEffect:ObservationDefinition*>?
< Timing or duration information, that may be associated with use with the indicated condition e.g. Adult patients suffering from myocardial infarction (from a few days until less than 35 days), ischaemic stroke (from 7 days until less than 6 months).; (xsd)duration:(<Range>
|<string>)>?
[]< An unwanted side effect or negative outcome that may happen if you use the drug (or other subject of this resource) for this indication.; (xsd)undesirableEffect:ClinicalUseDefinition*>*
< An expression that returns true or false, indicating whether the indication is applicable or not, after having applied its other elements. The expression may be inlined or may be a reference to a named expression within a logic library referenced by the library element.; (xsd)applicability:Expression>?
[]< Information about the use of the medicinal product in relation to other therapies described as part of the indication.; (xsd)otherTherapy:ClinicalUseDefinition.contraindication.otherTherapy>*🔗 Specifics for when this is an interaction.WarningDefinition.interaction(xsd)(doc)=
<#base:ClinicalUseDefinition.interaction>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
[]< The specific medication, product, food, substance etc. or laboratory test that interacts.; (xsd)interactant:WarningDefinition.interaction.interactant>*
< The type of the interaction e.g. drug-drug interaction, drug-food interaction, drug-lab test interaction. Binding: interaction-type (example, A categorisation for an interaction between two substances.); (xsd)type:CodeableConcept>?
< The effect of the interaction, for example "reduced gastric absorption of primary medication". Binding: interaction-effect (example, A interaction effect of clinical use of a medication or other substance.); (xsd)effect:ObservationDefinition*>?
< The incidence of the interaction, e.g. theoretical, observed. Binding: interaction-incidence (example, A categorisation for incidence of occurence of an interaction.); (xsd)incidence:CodeableConcept>?
[]< Actions for managing the interaction. Binding: interaction-management (example, A type of management for an interaction of a medication or other substance.); (xsd)management:CodeableConcept>*🔗 The specific medication, product, food, substance etc. or laboratory test that interacts.WarningDefinition.interaction.interactant(xsd)(doc)=
<#base:ClinicalUseDefinition.interaction.interactant>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The specific medication, product, food, substance etc. or laboratory test that interacts. Binding: interactant (example, An interactant - a substance that may have a clinically significant effect on another.); (xsd)item:(<BiologicallyDerivedProduct>
|<CodeableConcept>
|<Medication>
|<MedicinalProductDefinition>
|<NutritionProduct>
|<ObservationDefinition>
|<Substance>)>🔗 Describe the possible undesirable effects (negative outcomes) from the use of the medicinal product as treatment.WarningDefinition.undesirableEffect(xsd)(doc)=
<#base:ClinicalUseDefinition.undesirableEffect>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< The situation in which the undesirable effect may manifest. Binding: undesirable-effect-symptom (example, An undesirable effect of clinical use.); (xsd)symptomConditionEffect:ObservationDefinition*>?
< High level classification of the effect. Binding: undesirable-effect-classification (example, A categorisation for an undesirable effect.); (xsd)classification:CodeableConcept>?
< How often the effect is seen. Binding: undesirable-effect-frequency (example, A categorisation for a frequency of occurence of an undesirable effect.); (xsd)frequencyOfOccurrence:CodeableConcept>?🔗 A critical piece of information about environmental, health or physical risks or hazards that serve as caution to the user. For example 'Do not operate heavy machinery', 'May cause drowsiness', or 'Get medical advice/attention if you feel unwell'.WarningDefinition.warning(xsd)(doc)=
<#base:ClinicalUseDefinition.warning>
< Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
[]< 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. 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.; (xsd)extension:Extension>*
[]< 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). 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.; (xsd)modifierExtension:Extension>*
< A textual definition of this warning, with formatting.; (xsd)description:markdown>?
< A coded or unformatted textual definition of this warning. Binding: warning-type (example, Classification of warning type.); (xsd)code:CodeableConcept>?