composition-discharge-summary-v1-5-0 (Composition) | I | Composition | There are no (further) constraints on this element Element idComposition A set of resources composed into a single coherent clinical statement with clinical attestation DefinitionA set of healthcare-related information that is assembled together into a single logical document 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. While a Composition defines the structure, it does not actually contain the content: rather the full content of a document is contained in a Bundle, of which the Composition is the first resource contained. 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.
| |
id | Σ | 1..1 | id | There are no (further) constraints on this element Element idComposition.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
|
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idComposition.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idComposition.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. 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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.language Language of the resource content DefinitionThe 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). A human language. Common Languages (extensible)Constraints
| |
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.
|
contained | 0..* | Resource | There are no (further) constraints on this element Element idComposition.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
extension-composition-author | I | 1..* | Extension(CodeableConcept) | There are no (further) constraints on this element Element idComposition.extension:extension-composition-author Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. http://spms.min-saude.pt/iop/extensions/composition-author Constraints
|
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
identifier | Σ | 1..1 | Identifier | There are no (further) constraints on this element Element idComposition.identifier Logical identifier of composition (version-independent) DefinitionLogical identifier for the composition, assigned when created. This identifier stays constant as the composition is changed over time. See discussion in resource definition for how these relate.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.identifier.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.identifier.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.identifier.use usual | official | temp | secondary (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
|
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
|
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element idComposition.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. see http://en.wikipedia.org/wiki/Uniform_resource_identifier
General http://www.acme.com/identifiers/patient Mappings
|
value | Σ | 1..1 | string | There are no (further) constraints on this element Element idComposition.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension.
General 123456 Mappings
|
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element idComposition.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. This is not a duration - that's a measure of time (a separate type), but a duration that occurs at a fixed value of time. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). If duration is required, specify the type as Interval|Duration.
|
assigner | Σ I | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element idComposition.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
|
status | Σ ?! | 1..1 | codeBindingFixed Value | There are no (further) constraints on this element Element idComposition.status preliminary | final | amended | entered-in-error DefinitionThe workflow/clinical status of this composition. The status is a marker for the clinical standing of the document. Need to be able to mark interim, amended, or withdrawn compositions or documents. 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. The workflow/clinical status of the composition. CompositionStatus (required)Constraints
final
|
type | Σ | 1..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.type Kind of composition (LOINC if possible) DefinitionSpecifies the particular kind of composition (e.g. History and Physical, Discharge Summary, Progress Note). This usually equates to the purpose of making the composition. Key metadata element describing the composition, used in searching/filtering. 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. Type of a composition. FHIR Document Type Codes (preferred)Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.type.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.type.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 1..1 | Coding | There are no (further) constraints on this element Element idComposition.type.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.type.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.type.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.type.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://loinc.org
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.type.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 1..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.type.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
18842-5
|
display | Σ | 1..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.type.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
Discharge summary
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.type.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.type.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
class | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.class Categorization of Composition DefinitionA 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. Helps humans to assess whether the composition is of interest when viewing an index of compositions or documents. This is a metadata field from XDS/MHD. High-level kind of a clinical document at a macro level. FHIR Document Class Codes (example)Constraints
|
subject | Σ I | 1..1 | Reference(patient-discharge-summary) | There are no (further) constraints on this element Element idComposition.subject Who and/or what the composition is about DefinitionWho 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). Essential metadata for searching for the composition. Identifies who and/or what the composition/document is about. For clinical documents, this is usually the patient. Reference(patient-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
encounter | Σ I | 1..1 | Reference(encounter-discharge-summary) | There are no (further) constraints on this element Element idComposition.encounter Context of the Composition DefinitionDescribes the clinical encounter or type of care this documentation is associated with. Provides context for the composition and supports searching. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(encounter-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
date | Σ | 1..1 | dateTime | There are no (further) constraints on this element Element idComposition.date Composition editing time DefinitionThe composition editing time, when the composition was last logically changed by the author. dateTime is used for tracking, organizing versions and searching. The Last Modified Date on the composition may be after the date of the document was attested without being changed.
|
author | Σ I | 1..* | Reference(practitioner-discharge-summary) | There are no (further) constraints on this element Element idComposition.author Who and/or what authored the composition DefinitionIdentifies who is responsible for the information in the composition, not necessarily who typed it in. Identifies who is responsible for the content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(practitioner-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
title | Σ | 1..1 | string | There are no (further) constraints on this element Element idComposition.title Human Readable name/title DefinitionOfficial 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.
|
confidentiality | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.confidentiality As defined by affinity domain DefinitionThe code specifying the level of confidentiality of the Composition. The exact use of this element, and enforcement and issues related to highly sensitive documents are out of scope for the base specification, and delegated to implementation profiles (see security section). This element is labeled as a modifier because highly confidential documents must not be treated as if they are not. Codes specifying the level of confidentiality of the composition. ConfidentialityClassification (required)Constraints
|
attester | Σ | 1..* | BackboneElement | There are no (further) constraints on this element Element idComposition.attester Attests to accuracy of composition DefinitionA participant who has attested to the accuracy of the composition/document. Identifies responsibility for the accuracy of the composition content. Only list each attester once.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.attester.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.attester.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.attester.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
mode | Σ | 1..* | codeBinding | There are no (further) constraints on this element Element idComposition.attester.mode personal | professional | legal | official DefinitionThe type of attestation the authenticator offers. Indicates the level of authority of the attestation. Use more than one code where a single attester has more than one mode (professional and legal are often paired). The way in which a person authenticated a composition. CompositionAttestationMode (required)Constraints
|
time | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idComposition.attester.time When the composition was attested DefinitionWhen the composition was attested by the party. Identifies when the information in the composition was deemed accurate. (Things may have changed since then.).
|
party | Σ I | 1..1 | Reference(patient-discharge-summary | practitioner-discharge-summary | organization-discharge-summary) | There are no (further) constraints on this element Element idComposition.attester.party Who attested the composition DefinitionWho attested the composition in the specified way. Identifies who has taken on the responsibility for accuracy of the composition content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(patient-discharge-summary | practitioner-discharge-summary | organization-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
custodian | Σ I | 1..1 | Reference(organization-discharge-summary) | There are no (further) constraints on this element Element idComposition.custodian Organization which maintains the composition DefinitionIdentifies the organization or group who is responsible for ongoing maintenance of and access to the composition/document information. Identifies where to go to find the current version, where to report issues, etc. 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. Reference(organization-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
relatesTo | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idComposition.relatesTo Relationships to other compositions/documents DefinitionRelationships that this composition has with other compositions or documents that already exist. A document is a version specific composition.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.relatesTo.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.relatesTo.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.relatesTo.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
code | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element idComposition.relatesTo.code replaces | transforms | signs | appends DefinitionThe type of relationship that this composition has with anther composition or document. If this document appends another document, then the document cannot be fully understood without also accessing the referenced document. The type of relationship between documents. DocumentRelationshipType (required)Constraints
|
target[x] | Σ | 1..1 | There are no (further) constraints on this element Element idComposition.relatesTo.target[x] Target of the relationship DefinitionThe target composition/document of this relationship.
| |
targetIdentifier | Identifier | There are no (further) constraints on this element Data type | ||
targetReference | Reference(Composition) | There are no (further) constraints on this element Data type | ||
event | Σ | 1..* | BackboneElement | There are no (further) constraints on this element Element idComposition.event The clinical service(s) being documented DefinitionThe clinical service, such as a colonoscopy or an appendectomy, being documented. Provides context for the composition and creates a linkage between a resource describing an event and the composition created describing the event. The event needs to be consistent with the type element, though can provide further information if desired.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.event.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.event.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.event.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
code | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idComposition.event.code Code(s) that apply to the event being documented DefinitionThis list of codes 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 the procedure being documented is necessarily a "History and Physical" act. 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 eventCodes 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. This list of codes represents the main clinical acts being documented. v3 Code System ActCode (example)Constraints
|
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element idComposition.event.period The period covered by the documentation DefinitionThe 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. This is not a duration - that's a measure of time (a separate type), but a duration that occurs at a fixed value of time. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). If duration is required, specify the type as Interval|Duration.
|
detail | Σ I | 1..* | Reference(Resource) | There are no (further) constraints on this element Element idComposition.event.detail The event(s) being documented DefinitionThe description and/or reference of the event(s) being documented. For example, this could be used to document such a colonoscopy or an appendectomy. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
section | I | 0..* | BackboneElement | There are no (further) constraints on this element Element idComposition.section Composition is broken into sections DefinitionThe root of the sections that make up the composition. Unordered, Open, by code.coding.code(Value) Constraints
|
(All Slices) | There are no (further) constraints on this element | |||
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | string | There are no (further) constraints on this element Element idComposition.section.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idComposition.section.entry A reference to data that supports this section DefinitionA 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.
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
sliceSectionAlergias | I | 0..1 | BackboneElement | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias Composition is broken into sections DefinitionThe root of the sections that make up the composition.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
Allergies
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://loinc.org
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
48765-2
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
Allergies
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(observation-discharge-summary | allergy-intolerance-discharge-summary) | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.entry A reference to data that supports this section DefinitionA 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. Reference(observation-discharge-summary | allergy-intolerance-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.emptyReason.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.emptyReason.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.emptyReason.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.emptyReason.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.emptyReason.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.emptyReason.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list-empty-reason
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.emptyReason.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.emptyReason.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.emptyReason.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.emptyReason.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.emptyReason.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionAlergias.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
sliceSectionEvolucaoNoInternamento | I | 0..1 | BackboneElement | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento Composition is broken into sections DefinitionThe root of the sections that make up the composition.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
Hospital course Narrative
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://loinc.org
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
8648-8
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
Hospital course Narrative
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(observation-discharge-summary) | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.entry A reference to data that supports this section DefinitionA 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. Reference(observation-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.emptyReason.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.emptyReason.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.emptyReason.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.emptyReason.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.emptyReason.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.emptyReason.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list-empty-reason
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.emptyReason.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.emptyReason.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.emptyReason.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.emptyReason.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.emptyReason.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionEvolucaoNoInternamento.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
sliceSectionDiagnosticosMedicosNaAlta | I | 0..1 | BackboneElement | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta Composition is broken into sections DefinitionThe root of the sections that make up the composition.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://loinc.org
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
78375-3
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
Discharge diagnosis Narrative
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(observation-discharge-summary | encounter-discharge-summary) | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.entry A reference to data that supports this section DefinitionA 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. Reference(observation-discharge-summary | encounter-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.emptyReason.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.emptyReason.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.emptyReason.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.emptyReason.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.emptyReason.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.emptyReason.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list-empty-reason
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.emptyReason.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.emptyReason.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.emptyReason.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.emptyReason.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.emptyReason.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosMedicosNaAlta.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
sliceSectionTerapeuticaNoAmbulatorio | I | 0..1 | BackboneElement | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio Composition is broken into sections DefinitionThe root of the sections that make up the composition.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
Discharge medications Narrative
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://loinc.org
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
75311-1
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
Discharge medications Narrative
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(medication-request-discharge-summary) | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.entry A reference to data that supports this section DefinitionA 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. Reference(medication-request-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.emptyReason.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.emptyReason.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.emptyReason.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.emptyReason.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.emptyReason.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.emptyReason.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list-empty-reason
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.emptyReason.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.emptyReason.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.emptyReason.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.emptyReason.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.emptyReason.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaNoAmbulatorio.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
sliceSectionDiagnosticosDeAdmissao | I | 0..1 | BackboneElement | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao Composition is broken into sections DefinitionThe root of the sections that make up the composition.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
Admission diagnosis (narrative)
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://loinc.org
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
42347-5
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
Admission diagnosis (narrative)
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(observation-discharge-summary | encounter-discharge-summary) | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.entry A reference to data that supports this section DefinitionA 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. Reference(observation-discharge-summary | encounter-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.emptyReason.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.emptyReason.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.emptyReason.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.emptyReason.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.emptyReason.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.emptyReason.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list-empty-reason
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.emptyReason.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.emptyReason.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.emptyReason.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.emptyReason.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.emptyReason.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiagnosticosDeAdmissao.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
sliceSectionTerapeuticaEfetuada | I | 0..1 | BackboneElement | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada Composition is broken into sections DefinitionThe root of the sections that make up the composition.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
Medications on admission (narrative)
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://loinc.org
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
42346-7
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
Medications on admission (narrative)
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(observation-discharge-summary | medication-administration-discharge-summary) | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.entry A reference to data that supports this section DefinitionA 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. Reference(observation-discharge-summary | medication-administration-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.emptyReason.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.emptyReason.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.emptyReason.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.emptyReason.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.emptyReason.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.emptyReason.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list-empty-reason
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.emptyReason.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.emptyReason.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.emptyReason.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.emptyReason.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.emptyReason.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionTerapeuticaEfetuada.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
sliceSectionPlanoNutricional | I | 0..1 | BackboneElement | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional Composition is broken into sections DefinitionThe root of the sections that make up the composition.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
Discharge diet (narrative)
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://loinc.org
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
42344-2
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
Discharge diet (narrative)
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(observation-discharge-summary) | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.entry A reference to data that supports this section DefinitionA 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. Reference(observation-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.emptyReason.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.emptyReason.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.emptyReason.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.emptyReason.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.emptyReason.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.emptyReason.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list-empty-reason
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.emptyReason.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.emptyReason.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.emptyReason.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.emptyReason.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.emptyReason.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionPlanoNutricional.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
sliceSectionHistoriaClinica | I | 0..1 | BackboneElement | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica Composition is broken into sections DefinitionThe root of the sections that make up the composition.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
History of Present illness Narrative
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/ce/valueset/document-sections
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
10164-2
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
History of Present illness Narrative
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(observation-discharge-summary) | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.entry A reference to data that supports this section DefinitionA 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. Reference(observation-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.emptyReason.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.emptyReason.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.emptyReason.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.emptyReason.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.emptyReason.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.emptyReason.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list-empty-reason
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.emptyReason.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.emptyReason.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.emptyReason.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.emptyReason.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.emptyReason.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoriaClinica.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
sliceSectionInstrucoesPosAlta | I | 0..1 | BackboneElement | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta Composition is broken into sections DefinitionThe root of the sections that make up the composition.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
Plan of care
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://loinc.org
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
18776-5
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
Plan of care
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(observation-discharge-summary) | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.entry A reference to data that supports this section DefinitionA 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. Reference(observation-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document. Unordered, Open, by code.coding.code(Value) Mappings
|
sliceSectionPropostaDeMonitorizacaoETratamento | I | 0..1 | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
Proposta de monitorização e tratamento
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
PMT
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
Proposta de monitorização e tratamento
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(observation-discharge-summary) | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.entry A reference to data that supports this section DefinitionA 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. Reference(observation-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.emptyReason.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.emptyReason.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.emptyReason.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.emptyReason.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.emptyReason.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.emptyReason.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list-empty-reason
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.emptyReason.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.emptyReason.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.emptyReason.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.emptyReason.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.emptyReason.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionPropostaDeMonitorizacaoETratamento.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
sliceSectionOrientacaoAgendamento | I | 0..1 | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
Orientação/agendamentos
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
ORI
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
Orientação/agendamentos
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(observation-discharge-summary | appointment-discharge-summary) | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.entry A reference to data that supports this section DefinitionA 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. Reference(observation-discharge-summary | appointment-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.emptyReason.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.emptyReason.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.emptyReason.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.emptyReason.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.emptyReason.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.emptyReason.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list-empty-reason
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.emptyReason.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.emptyReason.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.emptyReason.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.emptyReason.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.emptyReason.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionOrientacaoAgendamento.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
sliceSectionMeiosComplementaresDeDiagnosticoMarcado | I | 0..1 | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
Meios complementares de diagnóstico marcados
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
MCDTM
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
Meios complementares de diagnóstico marcados
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(observation-discharge-summary | procedure-request-discharge-summary) | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.entry A reference to data that supports this section DefinitionA 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. Reference(observation-discharge-summary | procedure-request-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.emptyReason.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.emptyReason.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.emptyReason.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.emptyReason.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.emptyReason.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.emptyReason.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list-empty-reason
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.emptyReason.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.emptyReason.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.emptyReason.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.emptyReason.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.emptyReason.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionInstrucoesPosAlta.section:sliceSectionMeiosComplementaresDeDiagnosticoMarcado.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
sliceSectionClassificacaoDaFuncionalidade | I | 0..1 | BackboneElement | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade Composition is broken into sections DefinitionThe root of the sections that make up the composition.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
Functional status assessment note
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://loinc.org
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
47420-5
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
Functional status assessment note
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.entry A reference to data that supports this section DefinitionA 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.
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document. Unordered, Open, by code.coding.code(Value) Mappings
|
sliceSectionFocosDeDiagnosticoDeEnfermagem | I | 0..1 | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
Focos de diagnóstio de enfermagem
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
FDE
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
Focos de diagnóstio de enfermagem
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(observation-discharge-summary | condition-discharge-summary) | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.entry A reference to data that supports this section DefinitionA 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. Reference(observation-discharge-summary | condition-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.emptyReason.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.emptyReason.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.emptyReason.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.emptyReason.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.emptyReason.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.emptyReason.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list-empty-reason
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.emptyReason.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.emptyReason.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.emptyReason.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.emptyReason.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.emptyReason.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionFocosDeDiagnosticoDeEnfermagem.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
sliceSectionAtitudesTerapeuticas | I | 0..1 | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
Atitudes terapêuticas
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
ATI
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
Atitudes terapêuticas
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(observation-discharge-summary | procedure-discharge-summary) | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.entry A reference to data that supports this section DefinitionA 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. Reference(observation-discharge-summary | procedure-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.emptyReason.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.emptyReason.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.emptyReason.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.emptyReason.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.emptyReason.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.emptyReason.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list-empty-reason
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.emptyReason.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.emptyReason.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.emptyReason.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.emptyReason.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.emptyReason.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionClassificacaoDaFuncionalidade.section:sliceSectionAtitudesTerapeuticas.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
sliceSectionHistoricoDeProcedimentos | I | 0..1 | BackboneElement | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos Composition is broken into sections DefinitionThe root of the sections that make up the composition.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
History of Procedures Document
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://loinc.org
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
47519-4
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
History of Procedures Document
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.entry A reference to data that supports this section DefinitionA 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.
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document. Unordered, Open, by code.coding.code(Value) Mappings
|
sliceSectionDispositivosImplantaveis | I | 0..1 | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
Dispositivos implantáveis
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
DIS
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
Dispositivos implantáveis
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(observation-discharge-summary | device-discharge-summary) | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.entry A reference to data that supports this section DefinitionA 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. Reference(observation-discharge-summary | device-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.emptyReason.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.emptyReason.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.emptyReason.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.emptyReason.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.emptyReason.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.emptyReason.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list-empty-reason
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.emptyReason.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.emptyReason.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.emptyReason.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.emptyReason.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.emptyReason.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionDispositivosImplantaveis.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
sliceSectionIntervencoesCirurgicas | I | 0..1 | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
Intervenções cirúrgicas
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
INT
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
Intervenções cirúrgicas
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(observation-discharge-summary | procedure-discharge-summary) | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.entry A reference to data that supports this section DefinitionA 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. Reference(observation-discharge-summary | procedure-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.emptyReason.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.emptyReason.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.emptyReason.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.emptyReason.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.emptyReason.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.emptyReason.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list-empty-reason
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.emptyReason.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.emptyReason.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.emptyReason.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.emptyReason.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.emptyReason.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionIntervencoesCirurgicas.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
sliceSectionVentilacaoMecanica | I | 0..1 | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
Ventilação mecânica
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
VEN
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
Ventilação mecânica
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(observation-discharge-summary | procedure-discharge-summary) | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.entry A reference to data that supports this section DefinitionA 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. Reference(observation-discharge-summary | procedure-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.emptyReason.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.emptyReason.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.emptyReason.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.emptyReason.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.emptyReason.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.emptyReason.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list-empty-reason
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.emptyReason.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.emptyReason.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.emptyReason.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.emptyReason.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.emptyReason.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionVentilacaoMecanica.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
sliceSectionInfecaoNosocomial | I | 0..1 | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
Infeção nosocomial
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
INF
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
Infeção nosocomial
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(observation-discharge-summary | procedure-discharge-summary) | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.entry A reference to data that supports this section DefinitionA 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. Reference(observation-discharge-summary | procedure-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.emptyReason.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.emptyReason.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.emptyReason.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.emptyReason.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.emptyReason.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.emptyReason.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list-empty-reason
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.emptyReason.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.emptyReason.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.emptyReason.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.emptyReason.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.emptyReason.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionInfecaoNosocomial.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
sliceSectionMeiosComplementaresDeDiagnosticosEfetuados | I | 0..1 | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
Meios complementares de diagnósticos efetuados
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
MCDTE
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
Meios complementares de diagnósticos efetuados
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(observation-discharge-summary | procedure-request-discharge-summary) | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.entry A reference to data that supports this section DefinitionA 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. Reference(observation-discharge-summary | procedure-request-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.emptyReason.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.emptyReason.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.emptyReason.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.emptyReason.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.emptyReason.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.emptyReason.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list-empty-reason
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.emptyReason.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.emptyReason.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.emptyReason.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.emptyReason.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.emptyReason.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionHistoricoDeProcedimentos.section:sliceSectionMeiosComplementaresDeDiagnosticosEfetuados.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
sliceSectionDiarios | I | 0..1 | BackboneElement | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios Composition is broken into sections DefinitionThe root of the sections that make up the composition.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
Review of systems Narrative - Reporte
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://loinc.org
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
10187-3
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
Review of systems Narrative - Reporte
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(observation-discharge-summary) | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.entry A reference to data that supports this section DefinitionA 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. Reference(observation-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.emptyReason.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.emptyReason.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.emptyReason.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.emptyReason.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.emptyReason.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.emptyReason.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list-empty-reason
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.emptyReason.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.emptyReason.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.emptyReason.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.emptyReason.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.emptyReason.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionDiarios.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
sliceSectionIdentificadoresAdministrativos | I | 0..1 | BackboneElement | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos Composition is broken into sections DefinitionThe root of the sections that make up the composition.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
title | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.title Label for section (e.g. for ToC) Alternate namesheader, label, caption DefinitionThe 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. Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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.
Administrative information
| |
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.code Classification of section (recommended) DefinitionA code identifying the kind of content contained within the section. This must be consistent with the section title. Provides computable standardized labels to topics within the document. 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. Classification of a section of a composition/document. Document Section Codes (example)Constraints
| |
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.code.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.code.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://loinc.org
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.code.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | codeFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
87504-7
|
display | Σ | 0..1 | stringFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
Administrative information
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.code.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.text Text summary of the section, for human interpretation DefinitionA 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.
|
mode | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.mode working | snapshot | changes DefinitionHow the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. This element is labeled as a modifier because a change list must not be mis-understood as a complete list. The processing mode that applies to this section. ListMode (required)Constraints
|
orderedBy | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.orderedBy Order of section entries DefinitionSpecifies the order applied to the items in the section entries. Important for presentation and rendering. Lists may be sorted to place more important information first or to group related 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. What order applies to the items in the entry. List Order Codes (preferred)Constraints
| |
entry | I | 0..* | Reference(observation-discharge-summary | patient-discharge-summary | encounter-discharge-summary | list-discharge-summary) | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.entry A reference to data that supports this section DefinitionA 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. Reference(observation-discharge-summary | patient-discharge-summary | encounter-discharge-summary | list-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
emptyReason | I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.emptyReason Why the section is empty DefinitionIf the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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. If a section is empty, why it is empty. List Empty Reasons (preferred)Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.emptyReason.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.emptyReason.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.emptyReason.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.emptyReason.coding.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.emptyReason.coding.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uriFixed Value | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.emptyReason.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
http://spms.min-saude.pt/valueset-list-empty-reason
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.emptyReason.coding.version Version of the system - if relevant DefinitionThe 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.
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.emptyReason.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings may not exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.emptyReason.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings may not exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.emptyReason.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. 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.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.emptyReason.text Plain text representation of the concept DefinitionA 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. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
section | I | 0..* | see (section) | There are no (further) constraints on this element Element idComposition.section:sliceSectionIdentificadoresAdministrativos.section Nested Section DefinitionA nested sub-section within this section. Nested sections are primarily used to help human readers navigate to particular portions of the document.
|
Composition | 0..* | |
Composition.id | id | 1..1 |
Composition.meta | Meta | 0..1 |
Composition.implicitRules | uri | 0..1 |
Composition.language | code | 0..1 |
Composition.text | Narrative | 0..1 |
Composition.contained | Resource | 0..* |
Composition.extension | Extension | 0..* |
Composition.extension | Extension | 1..* |
Composition.modifierExtension | Extension | 0..* |
Composition.identifier | Identifier | 1..1 |
Composition.identifier.id | string | 0..1 |
Composition.identifier.extension | Extension | 0..* |
Composition.identifier.use | code | 0..1 |
Composition.identifier.type | CodeableConcept | 0..1 |
Composition.identifier.system | uri | 1..1 |
Composition.identifier.value | string | 1..1 |
Composition.identifier.period | Period | 0..1 |
Composition.identifier.assigner | Reference(Organization) | 0..1 |
Composition.status | code | 1..1 |
Composition.type | CodeableConcept | 1..1 |
Composition.type.id | string | 0..1 |
Composition.type.extension | Extension | 0..* |
Composition.type.coding | Coding | 1..1 |
Composition.type.coding.id | string | 0..1 |
Composition.type.coding.extension | Extension | 0..* |
Composition.type.coding.system | uri | 1..1 |
Composition.type.coding.version | string | 0..1 |
Composition.type.coding.code | code | 1..1 |
Composition.type.coding.display | string | 1..1 |
Composition.type.coding.userSelected | boolean | 0..1 |
Composition.type.text | string | 0..1 |
Composition.class | CodeableConcept | 0..1 |
Composition.subject | Reference(patient-discharge-summary) | 1..1 |
Composition.encounter | Reference(encounter-discharge-summary) | 1..1 |
Composition.date | dateTime | 1..1 |
Composition.author | Reference(practitioner-discharge-summary) | 1..* |
Composition.title | string | 1..1 |
Composition.confidentiality | code | 0..1 |
Composition.attester | BackboneElement | 1..* |
Composition.attester.id | string | 0..1 |
Composition.attester.extension | Extension | 0..* |
Composition.attester.modifierExtension | Extension | 0..* |
Composition.attester.mode | code | 1..* |
Composition.attester.time | dateTime | 0..1 |
Composition.attester.party | Reference(patient-discharge-summary | practitioner-discharge-summary | organization-discharge-summary) | 1..1 |
Composition.custodian | Reference(organization-discharge-summary) | 1..1 |
Composition.relatesTo | BackboneElement | 0..* |
Composition.relatesTo.id | string | 0..1 |
Composition.relatesTo.extension | Extension | 0..* |
Composition.relatesTo.modifierExtension | Extension | 0..* |
Composition.relatesTo.code | code | 1..1 |
Composition.relatesTo.target[x] | Reference(Composition), Identifier | 1..1 |
Composition.event | BackboneElement | 1..* |
Composition.event.id | string | 0..1 |
Composition.event.extension | Extension | 0..* |
Composition.event.modifierExtension | Extension | 0..* |
Composition.event.code | CodeableConcept | 0..* |
Composition.event.period | Period | 0..1 |
Composition.event.detail | Reference(Resource) | 1..* |
Composition.section | BackboneElement | 0..* |
Composition.section.id | string | 0..1 |
Composition.section.extension | Extension | 0..* |
Composition.section.modifierExtension | Extension | 0..* |
Composition.section.title | string | 0..1 |
Composition.section.code | CodeableConcept | 0..1 |
Composition.section.text | Narrative | 0..1 |
Composition.section.mode | code | 0..1 |
Composition.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.entry | Reference(Resource) | 0..* |
Composition.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.section | 0..* | |
Composition.section | BackboneElement | 0..1 |
Composition.section.id | string | 0..1 |
Composition.section.extension | Extension | 0..* |
Composition.section.modifierExtension | Extension | 0..* |
Composition.section.title | string | 0..1 |
Composition.section.code | CodeableConcept | 0..1 |
Composition.section.code.id | string | 0..1 |
Composition.section.code.extension | Extension | 0..* |
Composition.section.code.coding | Coding | 0..* |
Composition.section.code.coding.id | string | 0..1 |
Composition.section.code.coding.extension | Extension | 0..* |
Composition.section.code.coding.system | uri | 0..1 |
Composition.section.code.coding.version | string | 0..1 |
Composition.section.code.coding.code | code | 0..1 |
Composition.section.code.coding.display | string | 0..1 |
Composition.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.code.text | string | 0..1 |
Composition.section.text | Narrative | 0..1 |
Composition.section.mode | code | 0..1 |
Composition.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.entry | Reference(observation-discharge-summary | allergy-intolerance-discharge-summary) | 0..* |
Composition.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.emptyReason.id | string | 0..1 |
Composition.section.emptyReason.extension | Extension | 0..* |
Composition.section.emptyReason.coding | Coding | 0..* |
Composition.section.emptyReason.coding.id | string | 0..1 |
Composition.section.emptyReason.coding.extension | Extension | 0..* |
Composition.section.emptyReason.coding.system | uri | 0..1 |
Composition.section.emptyReason.coding.version | string | 0..1 |
Composition.section.emptyReason.coding.code | code | 0..1 |
Composition.section.emptyReason.coding.display | string | 0..1 |
Composition.section.emptyReason.coding.userSelected | boolean | 0..1 |
Composition.section.emptyReason.text | string | 0..1 |
Composition.section.section | 0..* | |
Composition.section | BackboneElement | 0..1 |
Composition.section.id | string | 0..1 |
Composition.section.extension | Extension | 0..* |
Composition.section.modifierExtension | Extension | 0..* |
Composition.section.title | string | 0..1 |
Composition.section.code | CodeableConcept | 0..1 |
Composition.section.code.id | string | 0..1 |
Composition.section.code.extension | Extension | 0..* |
Composition.section.code.coding | Coding | 0..* |
Composition.section.code.coding.id | string | 0..1 |
Composition.section.code.coding.extension | Extension | 0..* |
Composition.section.code.coding.system | uri | 0..1 |
Composition.section.code.coding.version | string | 0..1 |
Composition.section.code.coding.code | code | 0..1 |
Composition.section.code.coding.display | string | 0..1 |
Composition.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.code.text | string | 0..1 |
Composition.section.text | Narrative | 0..1 |
Composition.section.mode | code | 0..1 |
Composition.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.entry | Reference(observation-discharge-summary) | 0..* |
Composition.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.emptyReason.id | string | 0..1 |
Composition.section.emptyReason.extension | Extension | 0..* |
Composition.section.emptyReason.coding | Coding | 0..* |
Composition.section.emptyReason.coding.id | string | 0..1 |
Composition.section.emptyReason.coding.extension | Extension | 0..* |
Composition.section.emptyReason.coding.system | uri | 0..1 |
Composition.section.emptyReason.coding.version | string | 0..1 |
Composition.section.emptyReason.coding.code | code | 0..1 |
Composition.section.emptyReason.coding.display | string | 0..1 |
Composition.section.emptyReason.coding.userSelected | boolean | 0..1 |
Composition.section.emptyReason.text | string | 0..1 |
Composition.section.section | 0..* | |
Composition.section | BackboneElement | 0..1 |
Composition.section.id | string | 0..1 |
Composition.section.extension | Extension | 0..* |
Composition.section.modifierExtension | Extension | 0..* |
Composition.section.title | string | 0..1 |
Composition.section.code | CodeableConcept | 0..1 |
Composition.section.code.id | string | 0..1 |
Composition.section.code.extension | Extension | 0..* |
Composition.section.code.coding | Coding | 0..* |
Composition.section.code.coding.id | string | 0..1 |
Composition.section.code.coding.extension | Extension | 0..* |
Composition.section.code.coding.system | uri | 0..1 |
Composition.section.code.coding.version | string | 0..1 |
Composition.section.code.coding.code | code | 0..1 |
Composition.section.code.coding.display | string | 0..1 |
Composition.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.code.text | string | 0..1 |
Composition.section.text | Narrative | 0..1 |
Composition.section.mode | code | 0..1 |
Composition.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.entry | Reference(observation-discharge-summary | encounter-discharge-summary) | 0..* |
Composition.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.emptyReason.id | string | 0..1 |
Composition.section.emptyReason.extension | Extension | 0..* |
Composition.section.emptyReason.coding | Coding | 0..* |
Composition.section.emptyReason.coding.id | string | 0..1 |
Composition.section.emptyReason.coding.extension | Extension | 0..* |
Composition.section.emptyReason.coding.system | uri | 0..1 |
Composition.section.emptyReason.coding.version | string | 0..1 |
Composition.section.emptyReason.coding.code | code | 0..1 |
Composition.section.emptyReason.coding.display | string | 0..1 |
Composition.section.emptyReason.coding.userSelected | boolean | 0..1 |
Composition.section.emptyReason.text | string | 0..1 |
Composition.section.section | 0..* | |
Composition.section | BackboneElement | 0..1 |
Composition.section.id | string | 0..1 |
Composition.section.extension | Extension | 0..* |
Composition.section.modifierExtension | Extension | 0..* |
Composition.section.title | string | 0..1 |
Composition.section.code | CodeableConcept | 0..1 |
Composition.section.code.id | string | 0..1 |
Composition.section.code.extension | Extension | 0..* |
Composition.section.code.coding | Coding | 0..* |
Composition.section.code.coding.id | string | 0..1 |
Composition.section.code.coding.extension | Extension | 0..* |
Composition.section.code.coding.system | uri | 0..1 |
Composition.section.code.coding.version | string | 0..1 |
Composition.section.code.coding.code | code | 0..1 |
Composition.section.code.coding.display | string | 0..1 |
Composition.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.code.text | string | 0..1 |
Composition.section.text | Narrative | 0..1 |
Composition.section.mode | code | 0..1 |
Composition.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.entry | Reference(medication-request-discharge-summary) | 0..* |
Composition.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.emptyReason.id | string | 0..1 |
Composition.section.emptyReason.extension | Extension | 0..* |
Composition.section.emptyReason.coding | Coding | 0..* |
Composition.section.emptyReason.coding.id | string | 0..1 |
Composition.section.emptyReason.coding.extension | Extension | 0..* |
Composition.section.emptyReason.coding.system | uri | 0..1 |
Composition.section.emptyReason.coding.version | string | 0..1 |
Composition.section.emptyReason.coding.code | code | 0..1 |
Composition.section.emptyReason.coding.display | string | 0..1 |
Composition.section.emptyReason.coding.userSelected | boolean | 0..1 |
Composition.section.emptyReason.text | string | 0..1 |
Composition.section.section | 0..* | |
Composition.section | BackboneElement | 0..1 |
Composition.section.id | string | 0..1 |
Composition.section.extension | Extension | 0..* |
Composition.section.modifierExtension | Extension | 0..* |
Composition.section.title | string | 0..1 |
Composition.section.code | CodeableConcept | 0..1 |
Composition.section.code.id | string | 0..1 |
Composition.section.code.extension | Extension | 0..* |
Composition.section.code.coding | Coding | 0..* |
Composition.section.code.coding.id | string | 0..1 |
Composition.section.code.coding.extension | Extension | 0..* |
Composition.section.code.coding.system | uri | 0..1 |
Composition.section.code.coding.version | string | 0..1 |
Composition.section.code.coding.code | code | 0..1 |
Composition.section.code.coding.display | string | 0..1 |
Composition.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.code.text | string | 0..1 |
Composition.section.text | Narrative | 0..1 |
Composition.section.mode | code | 0..1 |
Composition.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.entry | Reference(observation-discharge-summary | encounter-discharge-summary) | 0..* |
Composition.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.emptyReason.id | string | 0..1 |
Composition.section.emptyReason.extension | Extension | 0..* |
Composition.section.emptyReason.coding | Coding | 0..* |
Composition.section.emptyReason.coding.id | string | 0..1 |
Composition.section.emptyReason.coding.extension | Extension | 0..* |
Composition.section.emptyReason.coding.system | uri | 0..1 |
Composition.section.emptyReason.coding.version | string | 0..1 |
Composition.section.emptyReason.coding.code | code | 0..1 |
Composition.section.emptyReason.coding.display | string | 0..1 |
Composition.section.emptyReason.coding.userSelected | boolean | 0..1 |
Composition.section.emptyReason.text | string | 0..1 |
Composition.section.section | 0..* | |
Composition.section | BackboneElement | 0..1 |
Composition.section.id | string | 0..1 |
Composition.section.extension | Extension | 0..* |
Composition.section.modifierExtension | Extension | 0..* |
Composition.section.title | string | 0..1 |
Composition.section.code | CodeableConcept | 0..1 |
Composition.section.code.id | string | 0..1 |
Composition.section.code.extension | Extension | 0..* |
Composition.section.code.coding | Coding | 0..* |
Composition.section.code.coding.id | string | 0..1 |
Composition.section.code.coding.extension | Extension | 0..* |
Composition.section.code.coding.system | uri | 0..1 |
Composition.section.code.coding.version | string | 0..1 |
Composition.section.code.coding.code | code | 0..1 |
Composition.section.code.coding.display | string | 0..1 |
Composition.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.code.text | string | 0..1 |
Composition.section.text | Narrative | 0..1 |
Composition.section.mode | code | 0..1 |
Composition.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.entry | Reference(observation-discharge-summary | medication-administration-discharge-summary) | 0..* |
Composition.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.emptyReason.id | string | 0..1 |
Composition.section.emptyReason.extension | Extension | 0..* |
Composition.section.emptyReason.coding | Coding | 0..* |
Composition.section.emptyReason.coding.id | string | 0..1 |
Composition.section.emptyReason.coding.extension | Extension | 0..* |
Composition.section.emptyReason.coding.system | uri | 0..1 |
Composition.section.emptyReason.coding.version | string | 0..1 |
Composition.section.emptyReason.coding.code | code | 0..1 |
Composition.section.emptyReason.coding.display | string | 0..1 |
Composition.section.emptyReason.coding.userSelected | boolean | 0..1 |
Composition.section.emptyReason.text | string | 0..1 |
Composition.section.section | 0..* | |
Composition.section | BackboneElement | 0..1 |
Composition.section.id | string | 0..1 |
Composition.section.extension | Extension | 0..* |
Composition.section.modifierExtension | Extension | 0..* |
Composition.section.title | string | 0..1 |
Composition.section.code | CodeableConcept | 0..1 |
Composition.section.code.id | string | 0..1 |
Composition.section.code.extension | Extension | 0..* |
Composition.section.code.coding | Coding | 0..* |
Composition.section.code.coding.id | string | 0..1 |
Composition.section.code.coding.extension | Extension | 0..* |
Composition.section.code.coding.system | uri | 0..1 |
Composition.section.code.coding.version | string | 0..1 |
Composition.section.code.coding.code | code | 0..1 |
Composition.section.code.coding.display | string | 0..1 |
Composition.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.code.text | string | 0..1 |
Composition.section.text | Narrative | 0..1 |
Composition.section.mode | code | 0..1 |
Composition.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.entry | Reference(observation-discharge-summary) | 0..* |
Composition.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.emptyReason.id | string | 0..1 |
Composition.section.emptyReason.extension | Extension | 0..* |
Composition.section.emptyReason.coding | Coding | 0..* |
Composition.section.emptyReason.coding.id | string | 0..1 |
Composition.section.emptyReason.coding.extension | Extension | 0..* |
Composition.section.emptyReason.coding.system | uri | 0..1 |
Composition.section.emptyReason.coding.version | string | 0..1 |
Composition.section.emptyReason.coding.code | code | 0..1 |
Composition.section.emptyReason.coding.display | string | 0..1 |
Composition.section.emptyReason.coding.userSelected | boolean | 0..1 |
Composition.section.emptyReason.text | string | 0..1 |
Composition.section.section | 0..* | |
Composition.section | BackboneElement | 0..1 |
Composition.section.id | string | 0..1 |
Composition.section.extension | Extension | 0..* |
Composition.section.modifierExtension | Extension | 0..* |
Composition.section.title | string | 0..1 |
Composition.section.code | CodeableConcept | 0..1 |
Composition.section.code.id | string | 0..1 |
Composition.section.code.extension | Extension | 0..* |
Composition.section.code.coding | Coding | 0..* |
Composition.section.code.coding.id | string | 0..1 |
Composition.section.code.coding.extension | Extension | 0..* |
Composition.section.code.coding.system | uri | 0..1 |
Composition.section.code.coding.version | string | 0..1 |
Composition.section.code.coding.code | code | 0..1 |
Composition.section.code.coding.display | string | 0..1 |
Composition.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.code.text | string | 0..1 |
Composition.section.text | Narrative | 0..1 |
Composition.section.mode | code | 0..1 |
Composition.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.entry | Reference(observation-discharge-summary) | 0..* |
Composition.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.emptyReason.id | string | 0..1 |
Composition.section.emptyReason.extension | Extension | 0..* |
Composition.section.emptyReason.coding | Coding | 0..* |
Composition.section.emptyReason.coding.id | string | 0..1 |
Composition.section.emptyReason.coding.extension | Extension | 0..* |
Composition.section.emptyReason.coding.system | uri | 0..1 |
Composition.section.emptyReason.coding.version | string | 0..1 |
Composition.section.emptyReason.coding.code | code | 0..1 |
Composition.section.emptyReason.coding.display | string | 0..1 |
Composition.section.emptyReason.coding.userSelected | boolean | 0..1 |
Composition.section.emptyReason.text | string | 0..1 |
Composition.section.section | 0..* | |
Composition.section | BackboneElement | 0..1 |
Composition.section.id | string | 0..1 |
Composition.section.extension | Extension | 0..* |
Composition.section.modifierExtension | Extension | 0..* |
Composition.section.title | string | 0..1 |
Composition.section.code | CodeableConcept | 0..1 |
Composition.section.code.id | string | 0..1 |
Composition.section.code.extension | Extension | 0..* |
Composition.section.code.coding | Coding | 0..* |
Composition.section.code.coding.id | string | 0..1 |
Composition.section.code.coding.extension | Extension | 0..* |
Composition.section.code.coding.system | uri | 0..1 |
Composition.section.code.coding.version | string | 0..1 |
Composition.section.code.coding.code | code | 0..1 |
Composition.section.code.coding.display | string | 0..1 |
Composition.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.code.text | string | 0..1 |
Composition.section.text | Narrative | 0..1 |
Composition.section.mode | code | 0..1 |
Composition.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.entry | Reference(observation-discharge-summary) | 0..* |
Composition.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.section | 0..* | |
Composition.section.section | 0..1 | |
Composition.section.section.id | string | 0..1 |
Composition.section.section.extension | Extension | 0..* |
Composition.section.section.modifierExtension | Extension | 0..* |
Composition.section.section.title | string | 0..1 |
Composition.section.section.code | CodeableConcept | 0..1 |
Composition.section.section.code.id | string | 0..1 |
Composition.section.section.code.extension | Extension | 0..* |
Composition.section.section.code.coding | Coding | 0..* |
Composition.section.section.code.coding.id | string | 0..1 |
Composition.section.section.code.coding.extension | Extension | 0..* |
Composition.section.section.code.coding.system | uri | 0..1 |
Composition.section.section.code.coding.version | string | 0..1 |
Composition.section.section.code.coding.code | code | 0..1 |
Composition.section.section.code.coding.display | string | 0..1 |
Composition.section.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.section.code.text | string | 0..1 |
Composition.section.section.text | Narrative | 0..1 |
Composition.section.section.mode | code | 0..1 |
Composition.section.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.section.entry | Reference(observation-discharge-summary) | 0..* |
Composition.section.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.section.emptyReason.id | string | 0..1 |
Composition.section.section.emptyReason.extension | Extension | 0..* |
Composition.section.section.emptyReason.coding | Coding | 0..* |
Composition.section.section.emptyReason.coding.id | string | 0..1 |
Composition.section.section.emptyReason.coding.extension | Extension | 0..* |
Composition.section.section.emptyReason.coding.system | uri | 0..1 |
Composition.section.section.emptyReason.coding.version | string | 0..1 |
Composition.section.section.emptyReason.coding.code | code | 0..1 |
Composition.section.section.emptyReason.coding.display | string | 0..1 |
Composition.section.section.emptyReason.coding.userSelected | boolean | 0..1 |
Composition.section.section.emptyReason.text | string | 0..1 |
Composition.section.section.section | 0..* | |
Composition.section.section | 0..1 | |
Composition.section.section.id | string | 0..1 |
Composition.section.section.extension | Extension | 0..* |
Composition.section.section.modifierExtension | Extension | 0..* |
Composition.section.section.title | string | 0..1 |
Composition.section.section.code | CodeableConcept | 0..1 |
Composition.section.section.code.id | string | 0..1 |
Composition.section.section.code.extension | Extension | 0..* |
Composition.section.section.code.coding | Coding | 0..* |
Composition.section.section.code.coding.id | string | 0..1 |
Composition.section.section.code.coding.extension | Extension | 0..* |
Composition.section.section.code.coding.system | uri | 0..1 |
Composition.section.section.code.coding.version | string | 0..1 |
Composition.section.section.code.coding.code | code | 0..1 |
Composition.section.section.code.coding.display | string | 0..1 |
Composition.section.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.section.code.text | string | 0..1 |
Composition.section.section.text | Narrative | 0..1 |
Composition.section.section.mode | code | 0..1 |
Composition.section.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.section.entry | Reference(observation-discharge-summary | appointment-discharge-summary) | 0..* |
Composition.section.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.section.emptyReason.id | string | 0..1 |
Composition.section.section.emptyReason.extension | Extension | 0..* |
Composition.section.section.emptyReason.coding | Coding | 0..* |
Composition.section.section.emptyReason.coding.id | string | 0..1 |
Composition.section.section.emptyReason.coding.extension | Extension | 0..* |
Composition.section.section.emptyReason.coding.system | uri | 0..1 |
Composition.section.section.emptyReason.coding.version | string | 0..1 |
Composition.section.section.emptyReason.coding.code | code | 0..1 |
Composition.section.section.emptyReason.coding.display | string | 0..1 |
Composition.section.section.emptyReason.coding.userSelected | boolean | 0..1 |
Composition.section.section.emptyReason.text | string | 0..1 |
Composition.section.section.section | 0..* | |
Composition.section.section | 0..1 | |
Composition.section.section.id | string | 0..1 |
Composition.section.section.extension | Extension | 0..* |
Composition.section.section.modifierExtension | Extension | 0..* |
Composition.section.section.title | string | 0..1 |
Composition.section.section.code | CodeableConcept | 0..1 |
Composition.section.section.code.id | string | 0..1 |
Composition.section.section.code.extension | Extension | 0..* |
Composition.section.section.code.coding | Coding | 0..* |
Composition.section.section.code.coding.id | string | 0..1 |
Composition.section.section.code.coding.extension | Extension | 0..* |
Composition.section.section.code.coding.system | uri | 0..1 |
Composition.section.section.code.coding.version | string | 0..1 |
Composition.section.section.code.coding.code | code | 0..1 |
Composition.section.section.code.coding.display | string | 0..1 |
Composition.section.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.section.code.text | string | 0..1 |
Composition.section.section.text | Narrative | 0..1 |
Composition.section.section.mode | code | 0..1 |
Composition.section.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.section.entry | Reference(observation-discharge-summary | procedure-request-discharge-summary) | 0..* |
Composition.section.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.section.emptyReason.id | string | 0..1 |
Composition.section.section.emptyReason.extension | Extension | 0..* |
Composition.section.section.emptyReason.coding | Coding | 0..* |
Composition.section.section.emptyReason.coding.id | string | 0..1 |
Composition.section.section.emptyReason.coding.extension | Extension | 0..* |
Composition.section.section.emptyReason.coding.system | uri | 0..1 |
Composition.section.section.emptyReason.coding.version | string | 0..1 |
Composition.section.section.emptyReason.coding.code | code | 0..1 |
Composition.section.section.emptyReason.coding.display | string | 0..1 |
Composition.section.section.emptyReason.coding.userSelected | boolean | 0..1 |
Composition.section.section.emptyReason.text | string | 0..1 |
Composition.section.section.section | 0..* | |
Composition.section | BackboneElement | 0..1 |
Composition.section.id | string | 0..1 |
Composition.section.extension | Extension | 0..* |
Composition.section.modifierExtension | Extension | 0..* |
Composition.section.title | string | 0..1 |
Composition.section.code | CodeableConcept | 0..1 |
Composition.section.code.id | string | 0..1 |
Composition.section.code.extension | Extension | 0..* |
Composition.section.code.coding | Coding | 0..* |
Composition.section.code.coding.id | string | 0..1 |
Composition.section.code.coding.extension | Extension | 0..* |
Composition.section.code.coding.system | uri | 0..1 |
Composition.section.code.coding.version | string | 0..1 |
Composition.section.code.coding.code | code | 0..1 |
Composition.section.code.coding.display | string | 0..1 |
Composition.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.code.text | string | 0..1 |
Composition.section.text | Narrative | 0..1 |
Composition.section.mode | code | 0..1 |
Composition.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.entry | Reference(Resource) | 0..* |
Composition.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.section | 0..* | |
Composition.section.section | 0..1 | |
Composition.section.section.id | string | 0..1 |
Composition.section.section.extension | Extension | 0..* |
Composition.section.section.modifierExtension | Extension | 0..* |
Composition.section.section.title | string | 0..1 |
Composition.section.section.code | CodeableConcept | 0..1 |
Composition.section.section.code.id | string | 0..1 |
Composition.section.section.code.extension | Extension | 0..* |
Composition.section.section.code.coding | Coding | 0..* |
Composition.section.section.code.coding.id | string | 0..1 |
Composition.section.section.code.coding.extension | Extension | 0..* |
Composition.section.section.code.coding.system | uri | 0..1 |
Composition.section.section.code.coding.version | string | 0..1 |
Composition.section.section.code.coding.code | code | 0..1 |
Composition.section.section.code.coding.display | string | 0..1 |
Composition.section.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.section.code.text | string | 0..1 |
Composition.section.section.text | Narrative | 0..1 |
Composition.section.section.mode | code | 0..1 |
Composition.section.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.section.entry | Reference(observation-discharge-summary | condition-discharge-summary) | 0..* |
Composition.section.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.section.emptyReason.id | string | 0..1 |
Composition.section.section.emptyReason.extension | Extension | 0..* |
Composition.section.section.emptyReason.coding | Coding | 0..* |
Composition.section.section.emptyReason.coding.id | string | 0..1 |
Composition.section.section.emptyReason.coding.extension | Extension | 0..* |
Composition.section.section.emptyReason.coding.system | uri | 0..1 |
Composition.section.section.emptyReason.coding.version | string | 0..1 |
Composition.section.section.emptyReason.coding.code | code | 0..1 |
Composition.section.section.emptyReason.coding.display | string | 0..1 |
Composition.section.section.emptyReason.coding.userSelected | boolean | 0..1 |
Composition.section.section.emptyReason.text | string | 0..1 |
Composition.section.section.section | 0..* | |
Composition.section.section | 0..1 | |
Composition.section.section.id | string | 0..1 |
Composition.section.section.extension | Extension | 0..* |
Composition.section.section.modifierExtension | Extension | 0..* |
Composition.section.section.title | string | 0..1 |
Composition.section.section.code | CodeableConcept | 0..1 |
Composition.section.section.code.id | string | 0..1 |
Composition.section.section.code.extension | Extension | 0..* |
Composition.section.section.code.coding | Coding | 0..* |
Composition.section.section.code.coding.id | string | 0..1 |
Composition.section.section.code.coding.extension | Extension | 0..* |
Composition.section.section.code.coding.system | uri | 0..1 |
Composition.section.section.code.coding.version | string | 0..1 |
Composition.section.section.code.coding.code | code | 0..1 |
Composition.section.section.code.coding.display | string | 0..1 |
Composition.section.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.section.code.text | string | 0..1 |
Composition.section.section.text | Narrative | 0..1 |
Composition.section.section.mode | code | 0..1 |
Composition.section.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.section.entry | Reference(observation-discharge-summary | procedure-discharge-summary) | 0..* |
Composition.section.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.section.emptyReason.id | string | 0..1 |
Composition.section.section.emptyReason.extension | Extension | 0..* |
Composition.section.section.emptyReason.coding | Coding | 0..* |
Composition.section.section.emptyReason.coding.id | string | 0..1 |
Composition.section.section.emptyReason.coding.extension | Extension | 0..* |
Composition.section.section.emptyReason.coding.system | uri | 0..1 |
Composition.section.section.emptyReason.coding.version | string | 0..1 |
Composition.section.section.emptyReason.coding.code | code | 0..1 |
Composition.section.section.emptyReason.coding.display | string | 0..1 |
Composition.section.section.emptyReason.coding.userSelected | boolean | 0..1 |
Composition.section.section.emptyReason.text | string | 0..1 |
Composition.section.section.section | 0..* | |
Composition.section | BackboneElement | 0..1 |
Composition.section.id | string | 0..1 |
Composition.section.extension | Extension | 0..* |
Composition.section.modifierExtension | Extension | 0..* |
Composition.section.title | string | 0..1 |
Composition.section.code | CodeableConcept | 0..1 |
Composition.section.code.id | string | 0..1 |
Composition.section.code.extension | Extension | 0..* |
Composition.section.code.coding | Coding | 0..* |
Composition.section.code.coding.id | string | 0..1 |
Composition.section.code.coding.extension | Extension | 0..* |
Composition.section.code.coding.system | uri | 0..1 |
Composition.section.code.coding.version | string | 0..1 |
Composition.section.code.coding.code | code | 0..1 |
Composition.section.code.coding.display | string | 0..1 |
Composition.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.code.text | string | 0..1 |
Composition.section.text | Narrative | 0..1 |
Composition.section.mode | code | 0..1 |
Composition.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.entry | Reference(Resource) | 0..* |
Composition.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.section | 0..* | |
Composition.section.section | 0..1 | |
Composition.section.section.id | string | 0..1 |
Composition.section.section.extension | Extension | 0..* |
Composition.section.section.modifierExtension | Extension | 0..* |
Composition.section.section.title | string | 0..1 |
Composition.section.section.code | CodeableConcept | 0..1 |
Composition.section.section.code.id | string | 0..1 |
Composition.section.section.code.extension | Extension | 0..* |
Composition.section.section.code.coding | Coding | 0..* |
Composition.section.section.code.coding.id | string | 0..1 |
Composition.section.section.code.coding.extension | Extension | 0..* |
Composition.section.section.code.coding.system | uri | 0..1 |
Composition.section.section.code.coding.version | string | 0..1 |
Composition.section.section.code.coding.code | code | 0..1 |
Composition.section.section.code.coding.display | string | 0..1 |
Composition.section.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.section.code.text | string | 0..1 |
Composition.section.section.text | Narrative | 0..1 |
Composition.section.section.mode | code | 0..1 |
Composition.section.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.section.entry | Reference(observation-discharge-summary | device-discharge-summary) | 0..* |
Composition.section.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.section.emptyReason.id | string | 0..1 |
Composition.section.section.emptyReason.extension | Extension | 0..* |
Composition.section.section.emptyReason.coding | Coding | 0..* |
Composition.section.section.emptyReason.coding.id | string | 0..1 |
Composition.section.section.emptyReason.coding.extension | Extension | 0..* |
Composition.section.section.emptyReason.coding.system | uri | 0..1 |
Composition.section.section.emptyReason.coding.version | string | 0..1 |
Composition.section.section.emptyReason.coding.code | code | 0..1 |
Composition.section.section.emptyReason.coding.display | string | 0..1 |
Composition.section.section.emptyReason.coding.userSelected | boolean | 0..1 |
Composition.section.section.emptyReason.text | string | 0..1 |
Composition.section.section.section | 0..* | |
Composition.section.section | 0..1 | |
Composition.section.section.id | string | 0..1 |
Composition.section.section.extension | Extension | 0..* |
Composition.section.section.modifierExtension | Extension | 0..* |
Composition.section.section.title | string | 0..1 |
Composition.section.section.code | CodeableConcept | 0..1 |
Composition.section.section.code.id | string | 0..1 |
Composition.section.section.code.extension | Extension | 0..* |
Composition.section.section.code.coding | Coding | 0..* |
Composition.section.section.code.coding.id | string | 0..1 |
Composition.section.section.code.coding.extension | Extension | 0..* |
Composition.section.section.code.coding.system | uri | 0..1 |
Composition.section.section.code.coding.version | string | 0..1 |
Composition.section.section.code.coding.code | code | 0..1 |
Composition.section.section.code.coding.display | string | 0..1 |
Composition.section.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.section.code.text | string | 0..1 |
Composition.section.section.text | Narrative | 0..1 |
Composition.section.section.mode | code | 0..1 |
Composition.section.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.section.entry | Reference(observation-discharge-summary | procedure-discharge-summary) | 0..* |
Composition.section.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.section.emptyReason.id | string | 0..1 |
Composition.section.section.emptyReason.extension | Extension | 0..* |
Composition.section.section.emptyReason.coding | Coding | 0..* |
Composition.section.section.emptyReason.coding.id | string | 0..1 |
Composition.section.section.emptyReason.coding.extension | Extension | 0..* |
Composition.section.section.emptyReason.coding.system | uri | 0..1 |
Composition.section.section.emptyReason.coding.version | string | 0..1 |
Composition.section.section.emptyReason.coding.code | code | 0..1 |
Composition.section.section.emptyReason.coding.display | string | 0..1 |
Composition.section.section.emptyReason.coding.userSelected | boolean | 0..1 |
Composition.section.section.emptyReason.text | string | 0..1 |
Composition.section.section.section | 0..* | |
Composition.section.section | 0..1 | |
Composition.section.section.id | string | 0..1 |
Composition.section.section.extension | Extension | 0..* |
Composition.section.section.modifierExtension | Extension | 0..* |
Composition.section.section.title | string | 0..1 |
Composition.section.section.code | CodeableConcept | 0..1 |
Composition.section.section.code.id | string | 0..1 |
Composition.section.section.code.extension | Extension | 0..* |
Composition.section.section.code.coding | Coding | 0..* |
Composition.section.section.code.coding.id | string | 0..1 |
Composition.section.section.code.coding.extension | Extension | 0..* |
Composition.section.section.code.coding.system | uri | 0..1 |
Composition.section.section.code.coding.version | string | 0..1 |
Composition.section.section.code.coding.code | code | 0..1 |
Composition.section.section.code.coding.display | string | 0..1 |
Composition.section.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.section.code.text | string | 0..1 |
Composition.section.section.text | Narrative | 0..1 |
Composition.section.section.mode | code | 0..1 |
Composition.section.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.section.entry | Reference(observation-discharge-summary | procedure-discharge-summary) | 0..* |
Composition.section.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.section.emptyReason.id | string | 0..1 |
Composition.section.section.emptyReason.extension | Extension | 0..* |
Composition.section.section.emptyReason.coding | Coding | 0..* |
Composition.section.section.emptyReason.coding.id | string | 0..1 |
Composition.section.section.emptyReason.coding.extension | Extension | 0..* |
Composition.section.section.emptyReason.coding.system | uri | 0..1 |
Composition.section.section.emptyReason.coding.version | string | 0..1 |
Composition.section.section.emptyReason.coding.code | code | 0..1 |
Composition.section.section.emptyReason.coding.display | string | 0..1 |
Composition.section.section.emptyReason.coding.userSelected | boolean | 0..1 |
Composition.section.section.emptyReason.text | string | 0..1 |
Composition.section.section.section | 0..* | |
Composition.section.section | 0..1 | |
Composition.section.section.id | string | 0..1 |
Composition.section.section.extension | Extension | 0..* |
Composition.section.section.modifierExtension | Extension | 0..* |
Composition.section.section.title | string | 0..1 |
Composition.section.section.code | CodeableConcept | 0..1 |
Composition.section.section.code.id | string | 0..1 |
Composition.section.section.code.extension | Extension | 0..* |
Composition.section.section.code.coding | Coding | 0..* |
Composition.section.section.code.coding.id | string | 0..1 |
Composition.section.section.code.coding.extension | Extension | 0..* |
Composition.section.section.code.coding.system | uri | 0..1 |
Composition.section.section.code.coding.version | string | 0..1 |
Composition.section.section.code.coding.code | code | 0..1 |
Composition.section.section.code.coding.display | string | 0..1 |
Composition.section.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.section.code.text | string | 0..1 |
Composition.section.section.text | Narrative | 0..1 |
Composition.section.section.mode | code | 0..1 |
Composition.section.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.section.entry | Reference(observation-discharge-summary | procedure-discharge-summary) | 0..* |
Composition.section.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.section.emptyReason.id | string | 0..1 |
Composition.section.section.emptyReason.extension | Extension | 0..* |
Composition.section.section.emptyReason.coding | Coding | 0..* |
Composition.section.section.emptyReason.coding.id | string | 0..1 |
Composition.section.section.emptyReason.coding.extension | Extension | 0..* |
Composition.section.section.emptyReason.coding.system | uri | 0..1 |
Composition.section.section.emptyReason.coding.version | string | 0..1 |
Composition.section.section.emptyReason.coding.code | code | 0..1 |
Composition.section.section.emptyReason.coding.display | string | 0..1 |
Composition.section.section.emptyReason.coding.userSelected | boolean | 0..1 |
Composition.section.section.emptyReason.text | string | 0..1 |
Composition.section.section.section | 0..* | |
Composition.section.section | 0..1 | |
Composition.section.section.id | string | 0..1 |
Composition.section.section.extension | Extension | 0..* |
Composition.section.section.modifierExtension | Extension | 0..* |
Composition.section.section.title | string | 0..1 |
Composition.section.section.code | CodeableConcept | 0..1 |
Composition.section.section.code.id | string | 0..1 |
Composition.section.section.code.extension | Extension | 0..* |
Composition.section.section.code.coding | Coding | 0..* |
Composition.section.section.code.coding.id | string | 0..1 |
Composition.section.section.code.coding.extension | Extension | 0..* |
Composition.section.section.code.coding.system | uri | 0..1 |
Composition.section.section.code.coding.version | string | 0..1 |
Composition.section.section.code.coding.code | code | 0..1 |
Composition.section.section.code.coding.display | string | 0..1 |
Composition.section.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.section.code.text | string | 0..1 |
Composition.section.section.text | Narrative | 0..1 |
Composition.section.section.mode | code | 0..1 |
Composition.section.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.section.entry | Reference(observation-discharge-summary | procedure-request-discharge-summary) | 0..* |
Composition.section.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.section.emptyReason.id | string | 0..1 |
Composition.section.section.emptyReason.extension | Extension | 0..* |
Composition.section.section.emptyReason.coding | Coding | 0..* |
Composition.section.section.emptyReason.coding.id | string | 0..1 |
Composition.section.section.emptyReason.coding.extension | Extension | 0..* |
Composition.section.section.emptyReason.coding.system | uri | 0..1 |
Composition.section.section.emptyReason.coding.version | string | 0..1 |
Composition.section.section.emptyReason.coding.code | code | 0..1 |
Composition.section.section.emptyReason.coding.display | string | 0..1 |
Composition.section.section.emptyReason.coding.userSelected | boolean | 0..1 |
Composition.section.section.emptyReason.text | string | 0..1 |
Composition.section.section.section | 0..* | |
Composition.section | BackboneElement | 0..1 |
Composition.section.id | string | 0..1 |
Composition.section.extension | Extension | 0..* |
Composition.section.modifierExtension | Extension | 0..* |
Composition.section.title | string | 0..1 |
Composition.section.code | CodeableConcept | 0..1 |
Composition.section.code.id | string | 0..1 |
Composition.section.code.extension | Extension | 0..* |
Composition.section.code.coding | Coding | 0..* |
Composition.section.code.coding.id | string | 0..1 |
Composition.section.code.coding.extension | Extension | 0..* |
Composition.section.code.coding.system | uri | 0..1 |
Composition.section.code.coding.version | string | 0..1 |
Composition.section.code.coding.code | code | 0..1 |
Composition.section.code.coding.display | string | 0..1 |
Composition.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.code.text | string | 0..1 |
Composition.section.text | Narrative | 0..1 |
Composition.section.mode | code | 0..1 |
Composition.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.entry | Reference(observation-discharge-summary) | 0..* |
Composition.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.emptyReason.id | string | 0..1 |
Composition.section.emptyReason.extension | Extension | 0..* |
Composition.section.emptyReason.coding | Coding | 0..* |
Composition.section.emptyReason.coding.id | string | 0..1 |
Composition.section.emptyReason.coding.extension | Extension | 0..* |
Composition.section.emptyReason.coding.system | uri | 0..1 |
Composition.section.emptyReason.coding.version | string | 0..1 |
Composition.section.emptyReason.coding.code | code | 0..1 |
Composition.section.emptyReason.coding.display | string | 0..1 |
Composition.section.emptyReason.coding.userSelected | boolean | 0..1 |
Composition.section.emptyReason.text | string | 0..1 |
Composition.section.section | 0..* | |
Composition.section | BackboneElement | 0..1 |
Composition.section.id | string | 0..1 |
Composition.section.extension | Extension | 0..* |
Composition.section.modifierExtension | Extension | 0..* |
Composition.section.title | string | 0..1 |
Composition.section.code | CodeableConcept | 0..1 |
Composition.section.code.id | string | 0..1 |
Composition.section.code.extension | Extension | 0..* |
Composition.section.code.coding | Coding | 0..* |
Composition.section.code.coding.id | string | 0..1 |
Composition.section.code.coding.extension | Extension | 0..* |
Composition.section.code.coding.system | uri | 0..1 |
Composition.section.code.coding.version | string | 0..1 |
Composition.section.code.coding.code | code | 0..1 |
Composition.section.code.coding.display | string | 0..1 |
Composition.section.code.coding.userSelected | boolean | 0..1 |
Composition.section.code.text | string | 0..1 |
Composition.section.text | Narrative | 0..1 |
Composition.section.mode | code | 0..1 |
Composition.section.orderedBy | CodeableConcept | 0..1 |
Composition.section.entry | Reference(observation-discharge-summary | patient-discharge-summary | encounter-discharge-summary | list-discharge-summary) | 0..* |
Composition.section.emptyReason | CodeableConcept | 0..1 |
Composition.section.emptyReason.id | string | 0..1 |
Composition.section.emptyReason.extension | Extension | 0..* |
Composition.section.emptyReason.coding | Coding | 0..* |
Composition.section.emptyReason.coding.id | string | 0..1 |
Composition.section.emptyReason.coding.extension | Extension | 0..* |
Composition.section.emptyReason.coding.system | uri | 0..1 |
Composition.section.emptyReason.coding.version | string | 0..1 |
Composition.section.emptyReason.coding.code | code | 0..1 |
Composition.section.emptyReason.coding.display | string | 0..1 |
Composition.section.emptyReason.coding.userSelected | boolean | 0..1 |
Composition.section.emptyReason.text | string | 0..1 |
Composition.section.section | 0..* |