Advance Care Plan
Using CarePlan resource as a single comprehensive central record per patient, that links all associated form, worksheet and attachments.
- The status of care plan has
draft,activeandrevoked - Status
activemeans the form is published - If the patient has published form, then it will return the CarePlan with the PDF format of the ACP form stored as a contained Binary resource with its id referenced in an image source data (the src attribute) in the
textelement. ThesupportingInfoshall not be return as this is not summary element If patient does not published form, but has draft form, then the API shall just return those summary elements without thesupportingInfoandtextelement
| AcpCarePlan (CarePlan) | C | CarePlan | There are no (further) constraints on this element Element idCarePlanShort description Healthcare plan for patient or group Alternate namesCare Team DefinitionDescribes the intention of how one or more practitioners intend to deliver care for a particular patient, group or community for a period of time, possibly limited to care for a specific condition or set of conditions.
| |
| id | Σ | 0..1 | id | There are no (further) constraints on this element Element idCarePlan.idShort description 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. Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. |
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idCarePlan.metaShort description Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
| implicitRules | Σ ?! | 0..0 | uri | There are no (further) constraints on this element Element idCarePlan.implicitRulesShort description 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. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
|
| language | 0..0 | codeBinding | There are no (further) constraints on this element Element idCarePlan.languageShort description 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). IETF language tag for a human language
| |
| text | C | 0..0 | Narrative | There are no (further) constraints on this element Element idCarePlan.textShort description 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 can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. The cardinality or value of this element may be affected by these constraints: dom-6 Constraints
|
| contained | C | 0..0 | Resource | There are no (further) constraints on this element Element idCarePlan.containedShort description 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, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels. The cardinality or value of this element may be affected by these constraints: dom-2, dom-4, dom-3, dom-5 Mappings
|
| extension | C | 0..* | Extension | Element idCarePlan.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Constraints
|
| extFormLatestStatus | C | 0..1 | Extension(string) | Element idCarePlan.extension:extFormLatestStatusShort description Latest From Status Alternate namesextensions, user content Definitionwhenever new draft form created, draft form deleted, form published or withdrawn, the status needs to be reflected as updated. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. https://fhir.synapxe.sg/StructureDefinition/ext-careplan-form-latest-status Constraints
|
| id | 0..0 | id | There are no (further) constraints on this element Element idCarePlan.extension:extFormLatestStatus.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idCarePlan.extension:extFormLatestStatus.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idCarePlan.extension:extFormLatestStatus.urlShort description identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.synapxe.sg/StructureDefinition/ext-careplan-form-latest-statusMappings
| |
| value[x] | C | 1..1 | There are no (further) constraints on this element Element idCarePlan.extension:extFormLatestStatus.value[x]Short description Value of extension DefinitionValue of extension - must be one of a constrained set of the data types (see Extensibility for a list). The cardinality or value of this element may be affected by these constraints: ext-1 Constraints
| |
| valueString | string | There are no (further) constraints on this element Data type | ||
| extWorksheetLatestStatus | C | 0..1 | Extension(string) | Element idCarePlan.extension:extWorksheetLatestStatusShort description 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. https://fhir.synapxe.sg/StructureDefinition/ext-careplan-worksheet-latest-status Constraints
|
| id | 0..0 | id | There are no (further) constraints on this element Element idCarePlan.extension:extWorksheetLatestStatus.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idCarePlan.extension:extWorksheetLatestStatus.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idCarePlan.extension:extWorksheetLatestStatus.urlShort description identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.synapxe.sg/StructureDefinition/ext-careplan-worksheet-latest-statusMappings
| |
| value[x] | C | 1..1 | There are no (further) constraints on this element Element idCarePlan.extension:extWorksheetLatestStatus.value[x]Short description Value of extension DefinitionValue of extension - must be one of a constrained set of the data types (see Extensibility for a list). The cardinality or value of this element may be affected by these constraints: ext-1 Constraints
| |
| valueString | string | There are no (further) constraints on this element Data type | ||
| modifierExtension | Σ ?! C | 0..0 | Extension | There are no (further) constraints on this element Element idCarePlan.modifierExtensionShort description 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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| identifier | Σ | 0..0 | Identifier | There are no (further) constraints on this element Element idCarePlan.identifierShort description External Ids for this plan DefinitionBusiness identifiers assigned to this care plan by the performer or other systems which remain constant as the resource is updated and propagates from server to server. Allows identification of the care plan as it is known by various participating systems and in a way that remains consistent across servers. This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.
|
| instantiatesCanonical | Σ | 0..0 | canonical(PlanDefinition | Questionnaire | Measure | ActivityDefinition | OperationDefinition) | There are no (further) constraints on this element Element idCarePlan.instantiatesCanonicalShort description Instantiates FHIR protocol or definition DefinitionThe URL pointing to a FHIR-defined protocol, guideline, questionnaire or other definition that is adhered to in whole or in part by this CarePlan. canonical(PlanDefinition | Questionnaire | Measure | ActivityDefinition | OperationDefinition) Constraints
|
| instantiatesUri | Σ | 0..0 | uri | There are no (further) constraints on this element Element idCarePlan.instantiatesUriShort description Instantiates external protocol or definition DefinitionThe URL pointing to an externally maintained protocol, guideline, questionnaire or other definition that is adhered to in whole or in part by this CarePlan. This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.
|
| basedOn | Σ | 0..0 | Reference(CarePlan | ServiceRequest | RequestOrchestration | NutritionOrder) | There are no (further) constraints on this element Element idCarePlan.basedOnShort description Fulfills plan, proposal or order Alternate namesfulfills DefinitionA higher-level request resource (i.e. a plan, proposal or order) that is fulfilled in whole or in part by this care plan. Allows tracing of the care plan and tracking whether proposals/recommendations were acted upon. Reference(CarePlan | ServiceRequest | RequestOrchestration | NutritionOrder) Constraints
|
| replaces | Σ | 0..0 | Reference(CarePlan) | There are no (further) constraints on this element Element idCarePlan.replacesShort description CarePlan replaced by this CarePlan Alternate namessupersedes DefinitionCompleted or terminated care plan whose function is taken by this new care plan. Allows tracing the continuation of a therapy or administrative process instantiated through multiple care plans. The replacement could be because the initial care plan was immediately rejected (due to an issue) or because the previous care plan was completed, but the need for the action described by the care plan remains ongoing.
|
| partOf | Σ | 0..0 | Reference(CarePlan) | There are no (further) constraints on this element Element idCarePlan.partOfShort description Part of referenced CarePlan DefinitionA larger care plan of which this particular care plan is a component or step. Each care plan is an independent request, such that having a care plan be part of another care plan can cause issues with cascading statuses. As such, this element is still being discussed.
|
| status | Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idCarePlan.statusShort description draft | active | on-hold | revoked | completed | entered-in-error | unknown DefinitionIndicates whether the plan is currently being acted upon, represents future intentions or is now a historical record. Allows clinicians to determine whether the plan is actionable or not. The unknown code is not to be used to convey other statuses. The unknown code should be used when one of the statuses applies, but the authoring system doesn't know the current state of the care plan. This element is labeled as a modifier because the status contains the code entered-in-error that marks the plan as not currently valid. Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record.
|
| intent | Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idCarePlan.intentShort description proposal | plan | order | option | directive DefinitionIndicates the level of authority/intentionality associated with the care plan and where the care plan fits into the workflow chain. Proposals/recommendations, plans and orders all use the same structure and can exist in the same fulfillment chain. This element is labeled as a modifier because the intent alters when and how the resource is actually applicable. This element is expected to be immutable. E.g. A "proposal" instance should never change to be a "plan" instance or "order" instance. Instead, a new instance 'basedOn' the prior instance should be created with the new 'intent' value. Codes indicating the degree of authority/intentionality associated with a care plan.
|
| category | Σ | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idCarePlan.categoryShort description Type of plan DefinitionIdentifies what "kind" of plan this is to support differentiation between multiple co-existing plans; e.g. "Home health", "psychiatric", "asthma", "disease management", "wellness plan", etc. Used for filtering what plan(s) are retrieved and displayed to different types of users. There may be multiple axes of categorization and one plan may serve multiple purposes. In some cases, this may be redundant with references to CarePlan.addresses. Identifies what "kind" of plan this is to support differentiation between multiple co-existing plans; e.g. "Home health", "psychiatric", "asthma", "disease management", etc.
|
| id | 0..0 | id | There are no (further) constraints on this element Element idCarePlan.category.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idCarePlan.category.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. 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 idCarePlan.category.codingShort description Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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..0 | id | There are no (further) constraints on this element Element idCarePlan.category.coding.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idCarePlan.category.coding.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| system | Σ | 1..1 | uri | There are no (further) constraints on this element Element idCarePlan.category.coding.systemShort description 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 be an absolute reference to some definition that establishes the system clearly and unambiguously.
|
| version | Σ | 0..0 | string | There are no (further) constraints on this element Element idCarePlan.category.coding.versionShort description 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 | Σ C | 1..1 | code | There are no (further) constraints on this element Element idCarePlan.category.coding.codeShort description 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. The cardinality or value of this element may be affected by these constraints: cod-1 Constraints
|
| display | Σ C | 0..1 | string | There are no (further) constraints on this element Element idCarePlan.category.coding.displayShort description 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. The cardinality or value of this element may be affected by these constraints: cod-1 Constraints
|
| userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idCarePlan.category.coding.userSelectedShort description If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. 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 idCarePlan.category.textShort description 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.
|
| title | Σ | 0..1 | string | There are no (further) constraints on this element Element idCarePlan.titleShort description Human-friendly name for the care plan DefinitionHuman-friendly name for the care plan.
|
| description | Σ | 0..1 | string | There are no (further) constraints on this element Element idCarePlan.descriptionShort description Summary of nature of plan DefinitionA description of the scope and nature of the plan. Provides more detail than conveyed by category.
|
| subject | Σ | 1..1 | Reference(Patient | Group) | There are no (further) constraints on this element Element idCarePlan.subjectShort description Who the care plan is for Alternate namespatient DefinitionIdentifies the patient or group whose intended care is described by the plan.
|
| encounter | Σ | 0..0 | Reference(Encounter) | There are no (further) constraints on this element Element idCarePlan.encounterShort description The Encounter during which this CarePlan was created DefinitionThe Encounter during which this CarePlan was created or to which the creation of this record is tightly associated. This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. CarePlan activities conducted as a result of the care plan may well occur as part of other encounters.
|
| period | Σ | 0..0 | Period | There are no (further) constraints on this element Element idCarePlan.periodShort description Time period plan covers Alternate namestiming DefinitionIndicates when the plan did (or is intended to) come into effect and end. Allows tracking what plan(s) are in effect at a particular time. Any activities scheduled as part of the plan should be constrained to the specified period regardless of whether the activities are planned within a single encounter/episode or across multiple encounters/episodes (e.g. the longitudinal management of a chronic condition).
|
| created | Σ | 1..1 | dateTime | There are no (further) constraints on this element Element idCarePlan.createdShort description Date record was first recorded Alternate namesauthoredOn DefinitionRepresents when this particular CarePlan record was created in the system, which is often a system-generated date.
|
| custodian | Σ | 0..1 | Reference(Patient | Practitioner | PractitionerRole | Device | RelatedPerson | Organization | CareTeam) | There are no (further) constraints on this element Element idCarePlan.custodianShort description Who is the designated responsible party DefinitionWhen populated, the custodian is responsible for the care plan. The care plan is attributed to the custodian. The custodian might or might not be a contributor. Reference(Patient | Practitioner | PractitionerRole | Device | RelatedPerson | Organization | CareTeam) Constraints
|
| contributor | 0..* | Reference(Patient | Practitioner | PractitionerRole | Device | RelatedPerson | Organization | CareTeam) | There are no (further) constraints on this element Element idCarePlan.contributorShort description Who provided the content of the care plan DefinitionIdentifies the individual(s), organization or device who provided the contents of the care plan. Collaborative care plans may have multiple contributors. Reference(Patient | Practitioner | PractitionerRole | Device | RelatedPerson | Organization | CareTeam) Constraints
| |
| careTeam | 0..0 | Reference(CareTeam) | There are no (further) constraints on this element Element idCarePlan.careTeamShort description Who's involved in plan? DefinitionIdentifies all people and organizations who are expected to be involved in the care envisioned by this plan. Allows representation of care teams, helps scope care plan. In some cases may be a determiner of access permissions.
| |
| addresses | Σ | 0..0 | CodeableReference(Condition) | There are no (further) constraints on this element Element idCarePlan.addressesShort description Health issues this plan addresses DefinitionIdentifies the conditions/problems/concerns/diagnoses/etc. whose management and/or mitigation are handled by this plan. The element can identify risks addressed by the plan as well as concerns. Also scopes plans - multiple plans may exist addressing different concerns. Use CarePlan.addresses.concept when a code sufficiently describes the concern (e.g. condition, problem, diagnosis, risk). Use CarePlan.addresses.reference when referencing a resource, which allows more information to be conveyed, such as onset date. CarePlan.addresses.concept and CarePlan.addresses.reference are not meant to be duplicative. For a single concern, either CarePlan.addresses.concept or CarePlan.addresses.reference can be used. CarePlan.addresses.concept may be a summary code, or CarePlan.addresses.reference may be used to reference a very precise definition of the concern using Condition. Both CarePlan.addresses.concept and CarePlan.addresses.reference can be used if they are describing different concerns for the care plan. Codes that describe the health issues this plan addresses. SNOMEDCTClinicalFindings (example) Constraints
|
| supportingInfo | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idCarePlan.supportingInfoShort description Information considered as part of plan DefinitionIdentifies portions of the patient's record that specifically influenced the formation of the plan. These might include comorbidities, recent procedures, limitations, recent assessments, etc. Identifies barriers and other considerations associated with the care plan. Use "concern" to identify specific conditions addressed by the care plan. supportingInfo can be used to convey one or more Advance Directives or Medical Treatment Consent Directives by referencing Consent or any other request resource with intent = directive.
| |
| id | 0..0 | id | There are no (further) constraints on this element Element idCarePlan.supportingInfo.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idCarePlan.supportingInfo.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| extSummryInfo | C | 0..1 | Extension(Complex) | Element idCarePlan.supportingInfo.extension:extSummryInfoShort description 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. Extension(Complex) Extension URLhttps://fhir.synapxe.sg/StructureDefinition/ext-summary-info Constraints
|
| reference | Σ C | 1..1 | string | There are no (further) constraints on this element Element idCarePlan.supportingInfo.referenceShort description Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. The cardinality or value of this element may be affected by these constraints: ref-2, ref-1 Constraints
|
| type | Σ | 0..0 | uriBinding | There are no (further) constraints on this element Element idCarePlan.supportingInfo.typeShort description Type the reference refers to (e.g. "Patient") - must be a resource in resources DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a known RESTful URL) or by resolving the target of the reference. Aa resource (or, for logical models, the URI of the logical model).
|
| identifier | Σ C | 0..0 | Identifier | There are no (further) constraints on this element Element idCarePlan.supportingInfo.identifierShort description Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the http://hl7.org/fhir/StructureDefinition/additionalIdentifier extension. The cardinality or value of this element may be affected by these constraints: ref-2 Constraints
|
| display | Σ C | 0..0 | string | There are no (further) constraints on this element Element idCarePlan.supportingInfo.displayShort description Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. The cardinality or value of this element may be affected by these constraints: ref-2 Constraints
|
| goal | 0..0 | Reference(Goal) | There are no (further) constraints on this element Element idCarePlan.goalShort description Desired outcome of plan DefinitionDescribes the intended objective(s) of carrying out the care plan. Provides context for plan. Allows plan effectiveness to be evaluated by clinicians. Goal can be achieving a particular change or merely maintaining a current state or even slowing a decline.
| |
| activity | 0..0 | BackboneElement | There are no (further) constraints on this element Element idCarePlan.activityShort description Action to occur or has occurred as part of plan DefinitionIdentifies an action that has occurred or is a planned action to occur as part of the plan. For example, a medication to be used, lab tests to perform, self-monitoring that has occurred, education etc. Allows systems to prompt for performance of planned activities, and validate plans against best practice.
| |
| note | 0..0 | Annotation | There are no (further) constraints on this element Element idCarePlan.noteShort description Comments about the plan DefinitionGeneral notes about the care plan not covered elsewhere. Used to capture information that applies to the plan as a whole that doesn't fit into discrete elements.
|
| AcpQuestionnaire (Questionnaire) | C | Questionnaire | There are no (further) constraints on this element Element idQuestionnaireShort description A structured set of questions Alternate namesForm, CRF, Survey DefinitionA structured set of questions intended to guide the collection of answers from end-users. Questionnaires provide detailed control over order, presentation, phraseology and grouping to allow coherent, consistent data collection.
| |
| id | Σ | 0..1 | id | There are no (further) constraints on this element Element idQuestionnaire.idShort description 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. Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. |
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idQuestionnaire.metaShort description Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
| id | 0..1 | id | There are no (further) constraints on this element Element idQuestionnaire.meta.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idQuestionnaire.meta.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| versionId | Σ | 0..1 | id | There are no (further) constraints on this element Element idQuestionnaire.meta.versionIdShort description Version specific identifier DefinitionThe version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted. The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
|
| lastUpdated | Σ | 0..1 | instant | There are no (further) constraints on this element Element idQuestionnaire.meta.lastUpdatedShort description When the resource version last changed DefinitionWhen the resource last changed - e.g. when the version changed. This element is generally omitted in instances submitted in a PUT or POST. Instead, it is populated in the response instance and when retrieving information using a GET. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a read interaction.
|
| source | Σ | 0..0 | uri | There are no (further) constraints on this element Element idQuestionnaire.meta.sourceShort description Identifies where the resource comes from DefinitionA uri that identifies the source system of the resource. This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc. The exact use of the source (and the possible implied Provenance.entity.role and agent.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. The source may correspond to Provenance.entity.what[x] or Provenance.agent.who[x], though it may be a more general or abstract reference. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.
|
| profile | Σ | 0..0 | canonical(StructureDefinition) | There are no (further) constraints on this element Element idQuestionnaire.meta.profileShort description Profiles this resource claims to conform to DefinitionA list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url. It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set. canonical(StructureDefinition) Constraints
|
| security | Σ | 0..0 | CodingBinding | There are no (further) constraints on this element Element idQuestionnaire.meta.securityShort description Security Labels applied to this resource DefinitionSecurity labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored. Security Labels from the Healthcare Privacy and Security Classification System. AllSecurityLabels (extensible) Constraints
|
| tag | Σ | 0..0 | Coding | There are no (further) constraints on this element Element idQuestionnaire.meta.tagShort description Tags applied to this resource DefinitionTags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource. The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored. Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
|
| implicitRules | Σ ?! | 0..0 | uri | There are no (further) constraints on this element Element idQuestionnaire.implicitRulesShort description 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. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
|
| language | 0..0 | codeBinding | There are no (further) constraints on this element Element idQuestionnaire.languageShort description 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). IETF language tag for a human language
| |
| text | C | 0..1 | Narrative | There are no (further) constraints on this element Element idQuestionnaire.textShort description 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 can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. The cardinality or value of this element may be affected by these constraints: dom-6 Constraints
|
| contained | C | 0..0 | Resource | There are no (further) constraints on this element Element idQuestionnaire.containedShort description 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, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels. The cardinality or value of this element may be affected by these constraints: dom-2, dom-4, dom-3, dom-5 Mappings
|
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idQuestionnaire.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| modifierExtension | Σ ?! C | 0..0 | Extension | There are no (further) constraints on this element Element idQuestionnaire.modifierExtensionShort description 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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| url | Σ C | 0..1 | uri | There are no (further) constraints on this element Element idQuestionnaire.urlShort description Canonical identifier for this questionnaire, represented as an absolute URI (globally unique) DefinitionAn absolute URI that is used to identify this questionnaire when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which an authoritative instance of this questionnaire is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the questionnaire is stored on different servers. Allows the questionnaire to be referenced by a single globally unique identifier. This is the id that will be used to link a QuestionnaireResponse to the Questionnaire the response is for. Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version. The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in Technical and Business Versions. In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the meta.source element to indicate where the current master source of the resource can be found. The name of the referenced questionnaire can be conveyed using the http://hl7.org/fhir/StructureDefinition/display extension.
|
| identifier | Σ | 0..0 | Identifier | There are no (further) constraints on this element Element idQuestionnaire.identifierShort description Business identifier for questionnaire DefinitionA formal identifier that is used to identify this questionnaire when it is represented in other formats, or referenced in a specification, model, design or an instance. Allows externally provided and/or usable business identifiers to be easily associated with the questionnaire. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this questionnaire outside of FHIR, where it is not possible to use the logical URI.
|
| version | Σ | 1..1 | string | There are no (further) constraints on this element Element idQuestionnaire.versionShort description Business version of the questionnaire DefinitionThe identifier that is used to identify this version of the questionnaire when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the questionnaire author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. There may be different questionnaires that have the same url but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the questionnaire with the format. The version SHOULD NOT contain a '#' - see Business Version.
|
| versionAlgorithm[x] | Σ | 0..0 | Binding | There are no (further) constraints on this element Element idQuestionnaire.versionAlgorithm[x]Short description How to compare versions DefinitionIndicates the mechanism used to compare versions to determine which is more current. If set as a string, this is a FHIRPath expression that has two additional context variables passed in - %version1 and %version2 and will return a negative number if version1 is newer, a positive number if version2 and a 0 if the version ordering can't be successfully be determined.
|
| name | Σ C | 0..1 | string | There are no (further) constraints on this element Element idQuestionnaire.nameShort description Name for this questionnaire (computer friendly) DefinitionA natural language name identifying the questionnaire. This name should be usable as an identifier for the module by machine processing applications such as code generation. Supports code generation. The name is not expected to be globally unique. The name should be a simple alphanumeric type no-whitespace name to ensure that it is machine-processing friendly. The cardinality or value of this element may be affected by these constraints: cnl-0 Constraints
|
| title | Σ | 0..1 | string | There are no (further) constraints on this element Element idQuestionnaire.titleShort description Name for this questionnaire (human friendly) DefinitionA short, descriptive, user-friendly title for the questionnaire. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.
|
| derivedFrom | Σ | 0..0 | canonical(Questionnaire) | There are no (further) constraints on this element Element idQuestionnaire.derivedFromShort description Based on Questionnaire DefinitionThe URL of a Questionnaire that this Questionnaire is based on. Allows a Questionnaire to be created based on another Questionnaire. This element covers a broad range of relationships, from 'somewhat inspired by' to 'fully compliant with'. There is a standard extensionthat allows clearer differentiation between the specifics of the derivation relationship where this is needed - e.g. to determine substitutability and validation expectations - http://hl7.org/fhir/StructureDefinition/questionnaire-derivationType.
|
| status | Σ ?! C | 1..1 | codeBinding | There are no (further) constraints on this element Element idQuestionnaire.statusShort description draft | active | retired | unknown DefinitionThe current state of this questionnaire. Enables tracking the lifecycle of the content and filtering of questionnaires that are appropriate for use versus not. A nominal state-transition diagram can be found in the] documentation Unknown does not represent 'other' - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. See guidance around (not) making local changes to elements here. The lifecycle status of an artifact. The cardinality or value of this element may be affected by these constraints: que-1a Constraints
|
| experimental | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idQuestionnaire.experimentalShort description For testing purposes, not real usage DefinitionA Boolean value to indicate that this questionnaire is authored for testing purposes (or education/evaluation/marketing) and is not intended for genuine usage. Enables experimental content to be developed following the same lifecycle that would be used for a production-level questionnaire. Allows filtering of questionnaires that are appropriate for use versus not. If absent, this resource is treated as though it is not experimental.
|
| subjectType | Σ | 0..0 | codeBinding | There are no (further) constraints on this element Element idQuestionnaire.subjectTypeShort description Resource that can be subject of QuestionnaireResponse DefinitionThe types of subjects that can be the subject of responses created for the questionnaire. Allows enforcing that a QuestionnaireResponse only has a .subject element of the appropriate type. If none are specified, then the subject is unlimited. One of the resource types defined as part of this version of FHIR.
|
| date | Σ | 0..0 | dateTime | There are no (further) constraints on this element Element idQuestionnaire.dateShort description Date last changed Alternate namesRevision Date DefinitionThe date (and optionally time) when the questionnaire was last significantly changed. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the questionnaire changes. The date is often not tracked until the resource is published, but may be present on draft content. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the questionnaire. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource. See guidance around (not) making local changes to elements here.
|
| publisher | Σ | 0..0 | string | There are no (further) constraints on this element Element idQuestionnaire.publisherShort description Name of the publisher/steward (organization or individual) DefinitionThe name of the organization or individual responsible for the release and ongoing maintenance of the questionnaire. Helps establish the "authority/credibility" of the questionnaire. May also allow for contact. Usually an organization but may be an individual. The publisher (or steward) of the questionnaire is the organization or individual primarily responsible for the maintenance and upkeep of the questionnaire. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the questionnaire. This item SHOULD be populated unless the information is available from context.
|
| contact | Σ | 0..0 | ContactDetail | There are no (further) constraints on this element Element idQuestionnaire.contactShort description Contact details for the publisher DefinitionContact details to assist a user in finding and communicating with the publisher. May be a web site, an email address, a telephone number, etc. See guidance around (not) making local changes to elements here.
|
| description | Σ | 0..1 | markdown | There are no (further) constraints on this element Element idQuestionnaire.descriptionShort description Natural language description of the questionnaire DefinitionA free text natural language description of the questionnaire from a consumer's perspective. This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the questionnaire as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context. (E.g. the language of the questionnaire is presumed to be the predominant language in the place the questionnaire was created).
|
| useContext | Σ | 0..0 | UsageContext | There are no (further) constraints on this element Element idQuestionnaire.useContextShort description The context that the content is intended to support DefinitionThe content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate questionnaires. Assist in searching for appropriate content. When multiple useContexts are specified, there is no expectation that all or even any of the contexts apply.
|
| jurisdiction | Σ | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idQuestionnaire.jurisdictionShort description Intended jurisdiction for questionnaire (if applicable) DefinitionA legal or geographic region in which the questionnaire is intended to be used. It may be possible for the questionnaire to be used in jurisdictions other than those for which it was originally designed or intended. DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.) Countries and regions within which this artifact is targeted for use. JurisdictionValueSet (extensible) Constraints
|
| purpose | 0..0 | markdown | There are no (further) constraints on this element Element idQuestionnaire.purposeShort description Why this questionnaire is defined DefinitionExplanation of why this questionnaire is needed and why it has been designed as it has. This element does not describe the usage of the questionnaire. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this questionnaire.
| |
| copyright | 0..0 | markdown | There are no (further) constraints on this element Element idQuestionnaire.copyrightShort description Use and/or publishing restrictions Alternate namesLicense, Restrictions DefinitionA copyright statement relating to the questionnaire and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the questionnaire. Consumers of the questionnaire must be able to determine any legal restrictions on the use of the artifact and/or its content.
| |
| copyrightLabel | 0..0 | string | There are no (further) constraints on this element Element idQuestionnaire.copyrightLabelShort description Copyright holder and year(s) DefinitionA short string (<50 characters), suitable for inclusion in a page footer that identifies the copyright holder, effective period, and optionally whether rights are resctricted. (e.g. 'All rights reserved', 'Some rights reserved'). Defines the content expected to be rendered in all representations of the artifact. The (c) symbol should NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general 'copyright' element.
| |
| approvalDate | 0..0 | date | There are no (further) constraints on this element Element idQuestionnaire.approvalDateShort description When the questionnaire was approved by publisher DefinitionThe date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. The 'date' element may be more recent than the approval date because of minor changes or editorial corrections. See guidance around (not) making local changes to elements here.
| |
| lastReviewDate | 0..0 | date | There are no (further) constraints on this element Element idQuestionnaire.lastReviewDateShort description When the questionnaire was last reviewed by the publisher DefinitionThe date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. Gives a sense of how "current" the content is. Resources that have not been reviewed in a long time may have a risk of being less appropriate/relevant. If specified, this date follows the original approval date. See guidance around (not) making local changes to elements here.
| |
| effectivePeriod | Σ | 0..0 | Period | There are no (further) constraints on this element Element idQuestionnaire.effectivePeriodShort description When the questionnaire is expected to be used DefinitionThe period during which the questionnaire content was or is planned to be in active use. Allows establishing a transition before a resource comes into effect and also allows for a sunsetting process when new versions of the questionnaire are or are expected to be used instead. The effective period for a questionnaire determines when the content is applicable for usage and is independent of publication and review dates. For example, a questionnaire intended to be used for the year 2016 might be published in 2015. See guidance around (not) making local changes to elements here.
|
| code | Σ | 1..1 | Coding | There are no (further) constraints on this element Element idQuestionnaire.codeShort description Concept that represents the overall questionnaire DefinitionAn identifier for this collection of questions in a particular terminology such as LOINC. Allows linking of the complete Questionnaire resources to formal terminologies. It's common for "panels" of questions to be identified by a code. Codes for questionnaires, groups and individual questions. QuestionnaireQuestionCodes (example) Constraints
|
| id | 0..1 | id | There are no (further) constraints on this element Element idQuestionnaire.code.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idQuestionnaire.code.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| system | Σ | 0..1 | uri | There are no (further) constraints on this element Element idQuestionnaire.code.systemShort description 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 be an absolute reference to some definition that establishes the system clearly and unambiguously.
|
| version | Σ | 0..1 | string | There are no (further) constraints on this element Element idQuestionnaire.code.versionShort description 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 | Σ C | 1..1 | code | There are no (further) constraints on this element Element idQuestionnaire.code.codeShort description 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. The cardinality or value of this element may be affected by these constraints: cod-1 Constraints
|
| display | Σ C | 0..1 | string | There are no (further) constraints on this element Element idQuestionnaire.code.displayShort description 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. The cardinality or value of this element may be affected by these constraints: cod-1 Constraints
|
| userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idQuestionnaire.code.userSelectedShort description If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. 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.
|
| item | C | 0..* | BackboneElement | There are no (further) constraints on this element Element idQuestionnaire.itemShort description Questions and sections within the Questionnaire DefinitionA particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.
|
| id | 0..1 | string | There are no (further) constraints on this element Element idQuestionnaire.item.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idQuestionnaire.item.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| modifierExtension | Σ ?! C | 0..0 | Extension | There are no (further) constraints on this element Element idQuestionnaire.item.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| linkId | C | 1..1 | string | There are no (further) constraints on this element Element idQuestionnaire.item.linkIdShort description Unique id for item in questionnaire DefinitionAn identifier that is unique within the Questionnaire allowing linkage to the equivalent item in a QuestionnaireResponse resource. QuestionnaireResponse does not require omitted items to be included and may have some items that repeat, so linkage based on position alone is not sufficient. This ''can'' be a meaningful identifier (e.g. a LOINC code) but is not intended to have any meaning. GUIDs or sequential numbers are appropriate here. LinkIds can have whitespaces and slashes by design. Tooling should not rely on linkIds being valid XHTML element IDs, and should not directly embed them as such The cardinality or value of this element may be affected by these constraints: que-2 Constraints
|
| definition | 0..1 | uri | There are no (further) constraints on this element Element idQuestionnaire.item.definitionShort description ElementDefinition - details for the item DefinitionThis element is a URI that refers to an ElementDefinition or to an ObservationDefinition that provides information about this item, including information that might otherwise be included in the instance of the Questionnaire resource. A detailed description of the construction of the URI is shown in Comments, below. A common pattern is to define a set of data elements and then build multiple questionnaires for different circumstances to gather the data. This element provides traceability to the common definition and allows the content for the question to come from the underlying definition. The uri refers to an ElementDefinition in a StructureDefinition or to an ObservationDefinition and always starts with the canonical URL for the target resource. When referring to a StructureDefinition, a fragment identifier is used to specify the element definition by its id Element.id. E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x]. In the absence of a fragment identifier, the first/root element definition in the target is the matching element definition.
| |
| code | C | 0..1 | Coding | There are no (further) constraints on this element Element idQuestionnaire.item.codeShort description Corresponding concept for this item in a terminology DefinitionA terminology code that corresponds to this group or question (e.g. a code from LOINC, which defines many questions and answers). Allows linking of groups of questions to formal terminologies. The value may come from the ElementDefinition referred to by .definition. Codes for questionnaires, groups and individual questions. QuestionnaireQuestionCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: que-3 Constraints
|
| prefix | 0..1 | string | There are no (further) constraints on this element Element idQuestionnaire.item.prefixShort description E.g. "1(a)", "2.5.3" Alternate nameslabel DefinitionA short label for a particular group, question or set of display text within the questionnaire used for reference by the individual completing the questionnaire. Separating the label from the question text allows improved rendering. Also, instructions will often refer to specific prefixes, so there's a need for the questionnaire design to have control over what labels are used. These are generally unique within a questionnaire, though this is not guaranteed. Some questionnaires may have multiple questions with the same label with logic to control which gets exposed. Typically, these won't be used for "display" items, though such use is not prohibited. Systems SHOULD NOT generate their own prefixes if prefixes are defined for any items within a Questionnaire.
| |
| text | 0..1 | string | There are no (further) constraints on this element Element idQuestionnaire.item.textShort description Primary text for the item DefinitionThe name of a section, the text of a question or text content for a display item. When using this element to represent the name of a section, use group type item and also make sure to limit the text element to a short string suitable for display as a section heading. Group item instructions should be included as a display type item within the group.
| |
| type | C | 1..1 | codeBinding | There are no (further) constraints on this element Element idQuestionnaire.item.typeShort description group | display | boolean | decimal | integer | date | dateTime + DefinitionThe type of questionnaire item this is - whether text for display, a grouping of other items or a particular type of data to be captured (string, integer, Coding, etc.). Defines the format in which the user is to be prompted for the answer. Additional constraints on the type of answer can be conveyed by extensions. The value may come from the ElementDefinition referred to by .definition. Distinguishes groups from questions and display text and indicates data type for questions. QuestionnaireItemType (required) ConditionsThe cardinality or value of this element may be affected by these constraints: que-9, que-8, que-6, que-5, que-3, que-10, que-1a, que-1b, que-1c Constraints
|
| enableWhen | ?! C | 0..* | BackboneElement | There are no (further) constraints on this element Element idQuestionnaire.item.enableWhenShort description Only allow data when DefinitionA constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. Allows questionnaires to adapt based on answers to other questions. E.g. If physical gender is specified as a male, no need to capture pregnancy history. Also allows conditional display of instructions or groups of questions. If multiple repetitions of this extension are present, the interpretation is driven by enableBehavior (either all repetitions must evaluate to true for this item to be enabled, or only one must evaluate to true for the item to be enabled). If the enableWhen.question has multiple answers, the condition evaluates to true if any of the answers for the referenced item match the enableWhen condition. This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to. If enableWhen logic depends on an item that is disabled, the logic should proceed as though the item is not valued - even if a default value or other value might be retained in memory in the event of the item being re-enabled. In some cases, the comparison between the indicated answer and the specified value may differ only by precision. For example, the enableWhen might be Q1 > 1970, but the answer to Q1 is 1970-10-15. There is not a clear answer as to whether 1970-10-15 should be considered 'greater' than 1970, given that it is an imprecise value. In these indeterminate situations, the form filler has the option of refusing to render the form. If the form is displayed, items where enableWhen is indeterminate SHOULD be treated as enabled with a warning indicating that the questionnaire logic was faulty and it is possible that the item should not be enabled. Questionnaires SHOULD be designed to take into account challenges around varying precision to minimize non-deterministic situations by setting constraints around expected precision, etc. The cardinality or value of this element may be affected by these constraints: que-12 Constraints
|
| id | 0..1 | string | There are no (further) constraints on this element Element idQuestionnaire.item.enableWhen.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idQuestionnaire.item.enableWhen.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idQuestionnaire.item.enableWhen.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| question | 1..1 | string | There are no (further) constraints on this element Element idQuestionnaire.item.enableWhen.questionShort description The linkId of question that determines whether item is enabled/disabled DefinitionThe linkId for the question whose answer (or lack of answer) governs whether this item is enabled. If multiple question occurrences are present for the same question (same linkId), then this refers to the nearest question occurrence reachable by tracing first the "ancestor" axis and then the "preceding" axis and then the "following" axis. If there are multiple items with the same linkId and all are equadistant (e.g. a question references a question that appears in a separate repeating group), that is an error. (Consider using the enableWhenExpression extension to define logic to handle such a situation.)
| |
| operator | C | 1..1 | codeBinding | There are no (further) constraints on this element Element idQuestionnaire.item.enableWhen.operatorShort description exists | = | != | > | < | >= | <= DefinitionSpecifies the criteria by which the question is enabled. The criteria by which a question is enabled. QuestionnaireItemOperator (required) ConditionsThe cardinality or value of this element may be affected by these constraints: que-7 Constraints
|
| answer[x] | C | 1..1 | There are no (further) constraints on this element Element idQuestionnaire.item.enableWhen.answer[x]Short description Value for question comparison based on operator DefinitionA value that the referenced question is tested using the specified operator in order for the item to be enabled. If there are multiple answers, a match on any of the answers suffices. If different behavior is desired (all must match, at least 2 must match, etc.), consider using the enableWhenExpression extension. Allowed values to answer questions. QuestionnaireAnswerCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: que-7 Constraints
| |
| answerBoolean | boolean | There are no (further) constraints on this element Data type | ||
| answerDecimal | decimal | There are no (further) constraints on this element Data type | ||
| answerInteger | integer | There are no (further) constraints on this element Data type | ||
| answerDate | date | There are no (further) constraints on this element Data type | ||
| answerDateTime | dateTime | There are no (further) constraints on this element Data type | ||
| answerTime | time | There are no (further) constraints on this element Data type | ||
| answerString | string | There are no (further) constraints on this element Data type | ||
| answerCoding | Coding | There are no (further) constraints on this element Data type | ||
| answerQuantity | Quantity | There are no (further) constraints on this element Data type | ||
| answerReference | Reference(Resource) | There are no (further) constraints on this element Data type | ||
| enableBehavior | C | 0..1 | codeBinding | There are no (further) constraints on this element Element idQuestionnaire.item.enableBehaviorShort description all | any DefinitionControls how multiple enableWhen values are interpreted - whether all or any must be true. This element must be specified if more than one enableWhen value is provided. Controls how multiple enableWhen values are interpreted - whether all or any must be true. The cardinality or value of this element may be affected by these constraints: que-12 Constraints
|
| disabledDisplay | 0..1 | codeBinding | There are no (further) constraints on this element Element idQuestionnaire.item.disabledDisplayShort description hidden | protected DefinitionIndicates if and how items that are disabled (because enableWhen evaluates to 'false') should be displayed. If not specified, rendering behavior is up to the client. This element is only meaningful if enableWhen or an equivalent extension is present Defines how disabled elements should be rendered QuestionnaireItemDisabledDisplay (required) Constraints
| |
| required | C | 0..1 | boolean | There are no (further) constraints on this element Element idQuestionnaire.item.requiredShort description Whether the item must be included in data results DefinitionAn indication, if true, that the item must be present in a "completed" QuestionnaireResponse. If false, the item may be skipped when answering the questionnaire. If the required item is a question, it must have a direct answer (i.e. an answer to the question itself, not merely answers to child questions) in order for the QuestionnaireResponse to be complete. If the required item is a group, it must have at least one descendant question which has an answer Questionnaire.item.required only has meaning for elements that are conditionally enabled with enableWhen if the condition evaluates to true. It also only has meaning if the parent element is present. If a non-required 'group' item contains a 'required' question item, it's completely fine to omit the group (because it's not required) despite it having a required child. Similarly, if an item that contains other items is marked as required, that does not automatically make the contained elements required (though required groups must contain at least one descendant item with a populated answer). The value for 'required' may come from the ElementDefinition referred to by .definition. Items are assumed not to be required unless explicitly specified, though extensions may impose additional expectations The cardinality or value of this element may be affected by these constraints: que-6 Constraints
|
| repeats | C | 0..1 | boolean | There are no (further) constraints on this element Element idQuestionnaire.item.repeatsShort description Whether the item may repeat DefinitionAn indication, if true, that a QuestionnaireResponse for this item may include multiple answers associated with a single instance of this item (for question-type items) or multiple repetitions of the item (for group-type items). Items may be used to create set of (related) questions that can be repeated to give multiple answers to such a set. If a question is marked as repeats=true, then multiple answers can be provided for the question in the corresponding QuestionnaireResponse. When rendering the questionnaire, it is up to the rendering software whether to render the question text for each answer repetition (i.e. "repeat the question") or to simply allow entry/selection of multiple answers for the question (repeat the answers). Which is most appropriate visually may depend on the type of answer as well as whether there are nested items. The resulting QuestionnaireResponse will be populated the same way regardless of rendering - one 'question' item with multiple answer values. The value may come from the ElementDefinition referred to by .definition. When repeats=true for a group, it'll be represented with multiple items with the same linkId in the QuestionnaireResponse. For a question, it'll be represented by a single item with that linkId with multiple answers. Items are generally assumed not to repeat unless explicitly specified. Systems SHOULD always populate this value The cardinality or value of this element may be affected by these constraints: que-6, que-13 Constraints
|
| readOnly | C | 0..1 | boolean | There are no (further) constraints on this element Element idQuestionnaire.item.readOnlyShort description Don't allow human editing DefinitionAn indication, when true, that the value cannot be changed by a human respondent to the Questionnaire. Allows certain information to be phrased (and rendered) as a question and an answer, while keeping users from changing it. May also be useful for preventing changes to pre-populated portions of a questionnaire, for calculated values, etc. If specified on a 'group', then all items beneath the specified group are read only. For questions, this only marks the answer associated with the specific item read only. Descendant questions are not impacted. The value of readOnly elements can be established by asserting extensions for defaultValues, linkages that support pre-population and/or extensions that support calculation based on other answers. The cardinality or value of this element may be affected by these constraints: que-9 Constraints
|
| maxLength | C | 0..1 | integer | There are no (further) constraints on this element Element idQuestionnaire.item.maxLengthShort description No more than these many characters DefinitionThe maximum number of characters that are permitted in the answer to be considered a "valid" QuestionnaireResponse. For base64binary, reflects the number of characters representing the encoded data, not the number of bytes of the binary data. The value may come from the ElementDefinition referred to by .definition. The cardinality or value of this element may be affected by these constraints: que-10 Constraints
|
| answerConstraint | C | 0..1 | codeBinding | There are no (further) constraints on this element Element idQuestionnaire.item.answerConstraintShort description optionsOnly | optionsOrType | optionsOrString DefinitionFor items that have a defined set of allowed answers (via answerOption or answerValueSet), indicates whether values other than those specified can be selected. Introduces the ability for questions to have 'other' answers If not specified, answerConstraint is presumed to be 'optionsOnly' Indicates differnt modes for restricting values when options or valueset are specified QuestionnaireAnswerConstraint (required) ConditionsThe cardinality or value of this element may be affected by these constraints: que-10, que-14 Constraints
|
| answerValueSet | C | 0..1 | canonical(ValueSet) | There are no (further) constraints on this element Element idQuestionnaire.item.answerValueSetShort description ValueSet containing permitted answers DefinitionA reference to a value set containing a list of values representing permitted answers for a question. LOINC defines many useful value sets for questionnaire responses. See LOINC Answer Lists. The value may come from the ElementDefinition referred to by .definition. The cardinality or value of this element may be affected by these constraints: que-5, que-4, que-14 Constraints
|
| answerOption | C | 0..* | BackboneElement | There are no (further) constraints on this element Element idQuestionnaire.item.answerOptionShort description Permitted answer DefinitionOne of the permitted answers for the question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes. The cardinality or value of this element may be affected by these constraints: que-5, que-4, que-11, que-14 Constraints
|
| id | 0..1 | string | There are no (further) constraints on this element Element idQuestionnaire.item.answerOption.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idQuestionnaire.item.answerOption.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| modifierExtension | Σ ?! C | 0..0 | Extension | There are no (further) constraints on this element Element idQuestionnaire.item.answerOption.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| value[x] | 1..1 | There are no (further) constraints on this element Element idQuestionnaire.item.answerOption.value[x]Short description Answer value DefinitionA potential answer that's allowed as the answer to this question. The data type of the value must agree with the item.type. Allowed values to answer questions. QuestionnaireAnswerCodes (example) Constraints
| ||
| valueInteger | integer | There are no (further) constraints on this element Data type | ||
| valueDate | date | There are no (further) constraints on this element Data type | ||
| valueTime | time | There are no (further) constraints on this element Data type | ||
| valueString | string | There are no (further) constraints on this element Data type | ||
| valueCoding | Coding | There are no (further) constraints on this element Data type | ||
| valueReference | Reference(Resource) | There are no (further) constraints on this element Data type | ||
| initialSelected | 0..1 | boolean | There are no (further) constraints on this element Element idQuestionnaire.item.answerOption.initialSelectedShort description Whether option is selected by default DefinitionIndicates whether the answer value is selected when the list of possible answers is initially shown. Only selected items explicitly marked to be selected
| |
| initial | C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idQuestionnaire.item.initialShort description Initial value(s) when item is first rendered DefinitionOne or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. In some workflows, having defaults saves time. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created. Note that initial values can influence results. The data type of initial.answer[x] must agree with the item.type, and only repeating items can have more then one initial value. The cardinality or value of this element may be affected by these constraints: que-8, que-13, que-11 Constraints
|
| item | 0..* | see (item) | There are no (further) constraints on this element Element idQuestionnaire.item.itemShort description Nested questionnaire items DefinitionText, questions and other groups to be nested beneath a question or group. Reports can consist of complex nested groups. There is no specified limit to the depth of nesting. However, Questionnaire authors are encouraged to consider the impact on the user and user interface of overly deep nesting.
|
| AcpQuestionnaireResponse (QuestionnaireResponse) | C | QuestionnaireResponse | There are no (further) constraints on this element Element idQuestionnaireResponseShort description A structured set of questions and their answers Alternate namesForm, QuestionnaireAnswers DefinitionA structured set of questions and their answers. The questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the questionnaire being responded to. The QuestionnaireResponse contains enough information about the questions asked and their organization that it can be interpreted somewhat independently from the Questionnaire it is based on. I.e. You don't need access to the Questionnaire in order to extract basic information from a QuestionnaireResponse.
| |
| id | Σ | 0..1 | id | There are no (further) constraints on this element Element idQuestionnaireResponse.idShort description 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. Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. |
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idQuestionnaireResponse.metaShort description Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
| implicitRules | Σ ?! | 0..0 | uri | There are no (further) constraints on this element Element idQuestionnaireResponse.implicitRulesShort description 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. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
|
| language | 0..0 | codeBinding | There are no (further) constraints on this element Element idQuestionnaireResponse.languageShort description 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). IETF language tag for a human language
| |
| text | C | 0..0 | Narrative | There are no (further) constraints on this element Element idQuestionnaireResponse.textShort description 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 can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. The cardinality or value of this element may be affected by these constraints: dom-6 Constraints
|
| contained | C | 0..0 | Resource | There are no (further) constraints on this element Element idQuestionnaireResponse.containedShort description 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, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels. The cardinality or value of this element may be affected by these constraints: dom-2, dom-4, dom-3, dom-5 Mappings
|
| extension | C | 1..* | Extension | Element idQuestionnaireResponse.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Constraints
|
| extBusinessVersion | C | 1..1 | Extension(string) | Element idQuestionnaireResponse.extension:extBusinessVersionShort description 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. https://fhir.synapxe.sg/StructureDefinition/ext-business-version Constraints
|
| extPublishedFormAttachment | C | 0..1 | Extension(Attachment) | Element idQuestionnaireResponse.extension:extPublishedFormAttachmentShort description Generated PDF file based on published ACP form Alternate namesextensions, user content DefinitionThe extension is used by QuestionnaireResponse resource, to store the generated PDF file There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. https://fhir.synapxe.sg/StructureDefinition/ext-questionnaireresponse-form-attachment Constraints
|
| extLinkedForm | C | 0..1 | Extension(Reference()) | Element idQuestionnaireResponse.extension:extLinkedFormShort description 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. https://fhir.synapxe.sg/StructureDefinition/ext-linked-form Constraints
|
| extFormDeleteReason | C | 0..1 | Extension(Coding) | Element idQuestionnaireResponse.extension:extFormDeleteReasonShort description 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. https://fhir.synapxe.sg/StructureDefinition/ext-form-delete-reason Constraints
|
| modifierExtension | Σ ?! C | 0..0 | Extension | There are no (further) constraints on this element Element idQuestionnaireResponse.modifierExtensionShort description 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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| identifier | Σ | 0..0 | Identifier | There are no (further) constraints on this element Element idQuestionnaireResponse.identifierShort description Business identifier for this set of answers DefinitionBusiness identifiers assigned to this questionnaire response by the performer and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server. Allows identification of the questionnaire response as it is known by various participating systems and in a way that remains consistent across servers. Note: This is a business identifier, not a resource identifier (see discussion).
|
| basedOn | Σ | 0..0 | Reference(QuestionnaireResponse) | Element idQuestionnaireResponse.basedOnShort description Request fulfilled by this QuestionnaireResponse Alternate namesorder DefinitionA plan, proposal or order that is fulfilled in whole or in part by this questionnaire response. For example, a ServiceRequest seeking an intake assessment or a decision support recommendation to assess for post-partum depression. Supports traceability of responsibility for the questionnaire response and allows linkage of the response to the proposals/recommendations acted upon. Reference(QuestionnaireResponse) Constraints
|
| partOf | Σ | 0..0 | Reference(Observation | Procedure) | There are no (further) constraints on this element Element idQuestionnaireResponse.partOfShort description Part of referenced event DefinitionA procedure or observation that this questionnaire was performed as part of the execution of. For example, the surgery a checklist was executed as part of. Not to be used to link an questionnaire response to an Encounter - use 'context' for that. Composition of questionnaire responses will be handled using the Assemble operation defined in the SDC IG. For relationships to referrals, and other types of requests, use basedOn. Reference(Observation | Procedure) Constraints
|
| questionnaire | Σ | 1..1 | canonical(Questionnaire) | There are no (further) constraints on this element Element idQuestionnaireResponse.questionnaireShort description Canonical URL of Questionnaire being answered Alternate namesForm DefinitionThe Questionnaire that defines and organizes the questions for which answers are being provided. Needed to allow editing of the questionnaire response in a manner that enforces the constraints of the original form. If a QuestionnaireResponse references a Questionnaire that can be resolved, then the QuestionnaireResponse structure must be consistent with the Questionnaire (i.e. questions must be organized into the same groups, nested questions must still be nested, etc.). It is possible to have a QuestionnaireResponse whose 'questionnaire' element does not resolve. It is also possible for the questionnaire element to not have a value but only extensions (e.g. conveying the title or identifier for the questionnaire). This may happen for legacy data. If there is no formally defined Questionnaire, it is undefined what the 'correct' values for the linkId elements should be and it is possible that linkIds might be inconsistent for QuestionnaireResponses for the same form if captured by distinct systems.
|
| status | Σ ?! | 1..1 | codeBinding | Element idQuestionnaireResponse.statusShort description in-progress | completed | amended | entered-in-error | stopped DefinitionThe current state of the questionnaire response. The information on Questionnaire resources may possibly be gathered during multiple sessions and altered after considered being finished. Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. Lifecycle status of the questionnaire response. QuestionnaireResponseConstrainedStatusVS (required) Constraints
|
| subject | Σ | 1..1 | Reference(Resource) | There are no (further) constraints on this element Element idQuestionnaireResponse.subjectShort description The subject of the questions Alternate namesPatient, Focus DefinitionThe subject of the questionnaire response. This could be a patient, organization, practitioner, device, etc. This is who/what the answers apply to, but is not necessarily the source of information. Links the questionnaire response to the Patient context. May also affect access control. If the Questionnaire declared a subjectType, the resource pointed to by this element must be an instance of one of the listed types.
|
| encounter | Σ | 0..0 | Reference(Encounter) | There are no (further) constraints on this element Element idQuestionnaireResponse.encounterShort description Encounter the questionnaire response is part of DefinitionThe Encounter during which this questionnaire response was created or to which the creation of this record is tightly associated. Links the questionnaire response to the Encounter context. May also affect access control. This will typically be the encounter the questionnaire response was created during, but some questionnaire responses may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission forms). A questionnaire that was initiated during an encounter but not fully completed during the encounter would still generally be associated with the encounter.
|
| authored | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idQuestionnaireResponse.authoredShort description Date the answers were gathered Alternate namesDate Created, Date published, Date Issued, Date updated DefinitionThe date and/or time that this questionnaire response was last modified by the user - e.g. changing answers or revising status. Clinicians need to be able to check the date that the information in the questionnaire was collected, to derive the context of the answers. May be different from the lastUpdateTime of the resource itself, because that reflects when the data was known to the server, not when the data was captured. This element is optional to allow for systems that might not know the value, however it SHOULD be populated if possible.
|
| author | Σ | 0..1 | Reference(Device | Practitioner | PractitionerRole | Patient | RelatedPerson | Organization) | There are no (further) constraints on this element Element idQuestionnaireResponse.authorShort description The individual or device that received and recorded the answers Alternate namesLaboratory, Service, Practitioner, Department, Company, Performer DefinitionThe individual or device that received the answers to the questions in the QuestionnaireResponse and recorded them in the system. Need to know who interpreted the subject's answers to the questions in the questionnaire, and selected the appropriate options for answers. Mapping a subject's answers to multiple choice options and determining what to put in the textual answer is a matter of interpretation. Authoring by device would indicate that some portion of the questionnaire had been auto-populated. Device should only be used if it directly determined the answers, not if it was merely used as a capture tool to record answers provided by others. In the latter case, information about the physical device, software, etc. would be captured using Provenance. Reference(Device | Practitioner | PractitionerRole | Patient | RelatedPerson | Organization) Constraints
|
| source | Σ | 0..1 | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idQuestionnaireResponse.sourceShort description The individual or device that answered the questions DefinitionThe individual or device that answered the questions about the subject. When answering questions about a subject that is minor, incapable of answering or an animal, another human source may answer the questions. If not specified, no inference can be made about who provided the data. Device should only be used if it directly determined the answers, not if it was merely used as a capture tool to record answers provided by others. In the latter case, information about the physical device, software, etc. would be captured using Provenance. Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) Constraints
|
| item | C | 0..* | BackboneElement | There are no (further) constraints on this element Element idQuestionnaireResponse.itemShort description Groups and questions DefinitionA group or question item from the original questionnaire for which answers are provided. Groups cannot have answers and therefore must nest directly within item. When dealing with questions, nesting must occur within each answer because some questions may have multiple answers (and the nesting occurs for each answer).\nWhen dealing with repeating items, each group repetition will be handled by a separate item. However, repeating questions are handled with a single question item and potentially multiple answers.
|
| id | 0..1 | string | There are no (further) constraints on this element Element idQuestionnaireResponse.item.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idQuestionnaireResponse.item.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| modifierExtension | Σ ?! C | 0..0 | Extension | There are no (further) constraints on this element Element idQuestionnaireResponse.item.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| linkId | C | 1..1 | string | There are no (further) constraints on this element Element idQuestionnaireResponse.item.linkIdShort description Pointer to specific item from Questionnaire DefinitionThe item from the Questionnaire that corresponds to this item in the QuestionnaireResponse resource. Items can repeat in the answers, so a direct 1..1 correspondence by position might not exist - requiring correspondence by identifier. The cardinality or value of this element may be affected by these constraints: qrs-2 Constraints
|
| definition | 0..1 | uri | There are no (further) constraints on this element Element idQuestionnaireResponse.item.definitionShort description ElementDefinition - details for the item DefinitionA reference to an ElementDefinition that provides the details for the item. A common pattern is to define a set of data elements, and then build multiple different questionnaires for different circumstances to gather the data. This element provides traceability to the common definition. The ElementDefinition must be in a StructureDefinition, and must have a fragment identifier that identifies the specific data element by its id (Element.id). E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x]. There is no need for this element if the item pointed to by the linkId has a definition listed.
| |
| text | 0..1 | string | There are no (further) constraints on this element Element idQuestionnaireResponse.item.textShort description Name for group or question text DefinitionText that is displayed above the contents of the group or as the text of the question being answered. Allows the questionnaire response to be read without access to the questionnaire. The text for an item SHOULD be identical to the text from the corresponding Questionnaire.item. This can't be strictly enforced because it's possible for the Questionnaire to be updated subsequent to the QuestionnaireResponse having been created, however the intention is that the text in the QuestionnaireResponse reflects what the user saw when completing the Questionnaire.
| |
| answer | C | 0..* | BackboneElement | There are no (further) constraints on this element Element idQuestionnaireResponse.item.answerShort description The response(s) to the question DefinitionThe respondent's answer(s) to the question. The value is nested because we cannot have a repeating structure that has variable type. The cardinality or value of this element may be affected by these constraints: qrs-1, qrs-2 Constraints
|
| id | 0..1 | string | There are no (further) constraints on this element Element idQuestionnaireResponse.item.answer.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idQuestionnaireResponse.item.answer.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| modifierExtension | Σ ?! C | 0..0 | Extension | There are no (further) constraints on this element Element idQuestionnaireResponse.item.answer.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| value[x] | C | 1..1 | There are no (further) constraints on this element Element idQuestionnaireResponse.item.answer.value[x]Short description Single-valued answer to the question DefinitionThe answer (or one of the answers) provided by the respondent to the question. Ability to retain a single-valued answer to a question. More complex structures (Attachment, Resource and Quantity) will typically be limited to electronic forms that can expose an appropriate user interface to capture the components and enforce the constraints of a complex data type. Additional complex types can be introduced through extensions. Must match the datatype specified by Questionnaire.item.type in the corresponding Questionnaire. Note that a question is answered using one of the possible choices defined with answerOption, answerValueSet or some other means and the answer has a complex data type, all elements within the answer in the QuestionnaireResponse SHOULD match the elements defined corresponding choice value in the Questionnaire. However, it is possible that not all elements will be propagated. Also, some systems might use language translations resulting in different displays. Comparison of value to the values defined in the Questionnaire (whether by answerOption, answerValueSet or answerExpression) SHALL NOT pay attention to Coding.display, Reference.display, Quantity.unit unless those are the only elements present. As well, systems are not required to check for a match on any extensions (e.g. ordinal values, translations, etc.). Systems MAY enforce that if extensions such as ordinal values are present in both Questionnaire and QuestionnaireResponse, they match. Binding this is problematic because one value set can't apply to both codes and quantities. QuestionnaireAnswerCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: qrs-2 Constraints
| |
| valueBoolean | boolean | There are no (further) constraints on this element Data type | ||
| valueDecimal | decimal | There are no (further) constraints on this element Data type | ||
| valueInteger | integer | There are no (further) constraints on this element Data type | ||
| valueDate | date | There are no (further) constraints on this element Data type | ||
| valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||
| valueTime | time | There are no (further) constraints on this element Data type | ||
| valueString | string | There are no (further) constraints on this element Data type | ||
| valueUri | uri | There are no (further) constraints on this element Data type | ||
| valueAttachment | Attachment | There are no (further) constraints on this element Data type | ||
| valueCoding | Coding | There are no (further) constraints on this element Data type | ||
| valueQuantity | SimpleQuantity | There are no (further) constraints on this element Data type | ||
| valueReference | Reference(Resource) | There are no (further) constraints on this element Data type | ||
| item | 0..* | see (item) | There are no (further) constraints on this element Element idQuestionnaireResponse.item.answer.itemShort description Child items of question DefinitionNested groups and/or questions found within this particular answer. It is useful to have "sub-questions", questions which normally appear when certain answers are given and which collect additional details. Only used when nesting beneath a question - see item.item for nesting beneath groups
| |
| item | 0..* | see (item) | There are no (further) constraints on this element Element idQuestionnaireResponse.item.itemShort description Child items of group item DefinitionSub-questions, sub-groups or display items nested beneath a group. Reports can consist of complex nested groups. Only used when nesting beneath a group - see item.answer.item for nesting beneath questions
|
| AcpDocumentReference (DocumentReference) | C | DocumentReference | There are no (further) constraints on this element Element idDocumentReferenceShort description A reference to a document DefinitionA reference to a document of any kind for any purpose. While the term “document” implies a more narrow focus, for this resource this "document" encompasses any serialized object with a mime-type, it includes formal patient-centric documents (CDA), clinical notes, scanned paper, non-patient specific documents like policy text, as well as a photo, video, or audio recording acquired or used in healthcare. The DocumentReference resource provides metadata about the document so that the document can be discovered and managed. The actual content may be inline base64 encoded data or provided by direct reference. Usually, this is used for documents other than those defined by FHIR.
| |
| id | Σ | 0..1 | id | There are no (further) constraints on this element Element idDocumentReference.idShort description 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. Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. |
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idDocumentReference.metaShort description Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
| id | 0..0 | id | There are no (further) constraints on this element Element idDocumentReference.meta.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDocumentReference.meta.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| versionId | Σ | 0..1 | id | There are no (further) constraints on this element Element idDocumentReference.meta.versionIdShort description Version specific identifier DefinitionThe version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted. The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
|
| lastUpdated | Σ | 0..1 | instant | There are no (further) constraints on this element Element idDocumentReference.meta.lastUpdatedShort description When the resource version last changed DefinitionWhen the resource last changed - e.g. when the version changed. This element is generally omitted in instances submitted in a PUT or POST. Instead, it is populated in the response instance and when retrieving information using a GET. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a read interaction.
|
| source | Σ | 0..0 | uri | There are no (further) constraints on this element Element idDocumentReference.meta.sourceShort description Identifies where the resource comes from DefinitionA uri that identifies the source system of the resource. This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc. The exact use of the source (and the possible implied Provenance.entity.role and agent.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. The source may correspond to Provenance.entity.what[x] or Provenance.agent.who[x], though it may be a more general or abstract reference. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.
|
| profile | Σ | 0..0 | canonical(StructureDefinition) | There are no (further) constraints on this element Element idDocumentReference.meta.profileShort description Profiles this resource claims to conform to DefinitionA list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url. It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set. canonical(StructureDefinition) Constraints
|
| security | Σ | 0..0 | CodingBinding | There are no (further) constraints on this element Element idDocumentReference.meta.securityShort description Security Labels applied to this resource DefinitionSecurity labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored. Security Labels from the Healthcare Privacy and Security Classification System. AllSecurityLabels (extensible) Constraints
|
| tag | Σ | 0..0 | Coding | There are no (further) constraints on this element Element idDocumentReference.meta.tagShort description Tags applied to this resource DefinitionTags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource. The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored. Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
|
| implicitRules | Σ ?! | 0..0 | uri | There are no (further) constraints on this element Element idDocumentReference.implicitRulesShort description 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. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
|
| language | 0..0 | codeBinding | There are no (further) constraints on this element Element idDocumentReference.languageShort description 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). IETF language tag for a human language
| |
| text | C | 0..0 | Narrative | There are no (further) constraints on this element Element idDocumentReference.textShort description 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 can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. The cardinality or value of this element may be affected by these constraints: dom-6 Constraints
|
| contained | C | 0..0 | Resource | There are no (further) constraints on this element Element idDocumentReference.containedShort description 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, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels. The cardinality or value of this element may be affected by these constraints: dom-2, dom-4, dom-3, dom-5 Mappings
|
| extension | C | 0..* | Extension | Element idDocumentReference.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Constraints
|
| extInstitutionId | C | 0..1 | Extension(integer) | Element idDocumentReference.extension:extInstitutionIdShort description 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. https://fhir.synapxe.sg/StructureDefinition/ext-institution-id Constraints
|
| extBusinessVersion | C | 1..1 | Extension(string) | Element idDocumentReference.extension:extBusinessVersionShort description 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. https://fhir.synapxe.sg/StructureDefinition/ext-business-version Constraints
|
| extLinkedForm | C | 0..1 | Extension(Reference()) | Element idDocumentReference.extension:extLinkedFormShort description 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. https://fhir.synapxe.sg/StructureDefinition/ext-linked-form Constraints
|
| extDocumentDeleteReason | C | 0..1 | Extension(Coding) | Element idDocumentReference.extension:extDocumentDeleteReasonShort description 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. https://fhir.synapxe.sg/StructureDefinition/ext-document-delete-reason Constraints
|
| modifierExtension | Σ ?! C | 0..0 | Extension | There are no (further) constraints on this element Element idDocumentReference.modifierExtensionShort description 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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| identifier | Σ | 0..0 | Identifier | There are no (further) constraints on this element Element idDocumentReference.identifierShort description Business identifiers for the document DefinitionOther business identifiers associated with the document, including version independent identifiers. Document identifiers usually assigned by the source of the document, or other business identifiers such as XDS DocumentEntry.uniqueId and DocumentEntry.entryUUID. These identifiers are specific to this instance of the document. The structure and format of this identifier would be consistent with the specification corresponding to the format of the document. (e.g. for a DICOM standard document, a 64-character numeric UID; for an HL7 CDA format, the CDA Document Id root and extension).
|
| version | Σ | 0..1 | string | There are no (further) constraints on this element Element idDocumentReference.versionShort description An explicitly assigned identifer of a variation of the content in the DocumentReference DefinitionAn explicitly assigned identifer of a variation of the content in the DocumentReference. While each resource, including the DocumentReference itself, has its own version identifier, this is a formal identifier for the logical version of the DocumentReference as a whole. It would remain constant if the resources were moved to a new server, and all got new individual resource versions, for example.
|
| basedOn | 0..0 | Reference(Appointment | AppointmentResponse | CarePlan | Claim | CommunicationRequest | Contract | CoverageEligibilityRequest | DeviceRequest | EnrollmentRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | RequestOrchestration | ServiceRequest | SupplyRequest | VisionPrescription) | There are no (further) constraints on this element Element idDocumentReference.basedOnShort description Procedure that caused this media to be created Alternate namesfulfills DefinitionA procedure that is fulfilled in whole or in part by the creation of this media. Allows tracing of authorization for the event and tracking whether proposals/recommendations were acted upon. Reference(Appointment | AppointmentResponse | CarePlan | Claim | CommunicationRequest | Contract | CoverageEligibilityRequest | DeviceRequest | EnrollmentRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | RequestOrchestration | ServiceRequest | SupplyRequest | VisionPrescription) Constraints
| |
| status | Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idDocumentReference.statusShort description current | superseded | entered-in-error DefinitionThe status of this document reference. This is the status of the DocumentReference object, which might be independent from the docStatus element. This element is labeled as a modifier because the status contains the codes that mark the document or reference as not currently valid. The status of the document reference. DocumentReferenceStatus (required) Constraints
|
| docStatus | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element idDocumentReference.docStatusShort description registered | partial | preliminary | final | amended | corrected | appended | cancelled | entered-in-error | deprecated | unknown DefinitionThe status of the underlying document. The document that is pointed to might be in various lifecycle states. Status of the underlying document.
|
| modality | Σ | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idDocumentReference.modalityShort description Imaging modality used DefinitionImaging modality used. This may include both acquisition and non-acquisition modalities. Type of acquired data in the instance. http://dicom.nema.org/medical/dicom/current/output/chtml/part16/sect_CID_33.html (extensible) Constraints
|
| type | Σ | 1..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idDocumentReference.typeShort description Kind of document (LOINC if possible) DefinitionSpecifies the particular kind of document referenced (e.g. History and Physical, Discharge Summary, Progress Note). This usually equates to the purpose of making the document referenced. Key metadata element describing the document that describes he exact type of document. Helps humans to assess whether the document is of interest when viewing a list of documents. Precise type of clinical document. FHIRDocumentTypeCodes (preferred) Constraints
|
| id | 0..0 | id | There are no (further) constraints on this element Element idDocumentReference.type.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idDocumentReference.type.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| coding | Σ C | 1..1 | Coding | Element idDocumentReference.type.codingShort description Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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..0 | id | There are no (further) constraints on this element Element idDocumentReference.type.coding.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idDocumentReference.type.coding.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| system | Σ | 1..1 | uri | There are no (further) constraints on this element Element idDocumentReference.type.coding.systemShort description 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 be an absolute reference to some definition that establishes the system clearly and unambiguously.
|
| version | Σ | 0..0 | string | There are no (further) constraints on this element Element idDocumentReference.type.coding.versionShort description 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 | Σ C | 1..1 | code | There are no (further) constraints on this element Element idDocumentReference.type.coding.codeShort description 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. The cardinality or value of this element may be affected by these constraints: cod-1 Constraints
|
| display | Σ C | 0..0 | string | There are no (further) constraints on this element Element idDocumentReference.type.coding.displayShort description 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. The cardinality or value of this element may be affected by these constraints: cod-1 Constraints
|
| userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idDocumentReference.type.coding.userSelectedShort description If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. 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..0 | string | There are no (further) constraints on this element Element idDocumentReference.type.textShort description 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.
|
| category | Σ | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idDocumentReference.categoryShort description Categorization of document Alternate namesclass, classCode DefinitionA categorization for the type of document referenced - helps for indexing and searching. This may be implied by or derived from the code specified in the DocumentReference.type. Key metadata element describing the the category or classification of the document. This is a broader perspective that groups similar documents based on how they would be used. This is a primary key used in searching. High-level kind of document at a macro level. ReferencedItemCategoryValueSet (example) Constraints
|
| id | 0..0 | id | There are no (further) constraints on this element Element idDocumentReference.category.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idDocumentReference.category.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. 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 idDocumentReference.category.codingShort description Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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..0 | id | There are no (further) constraints on this element Element idDocumentReference.category.coding.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idDocumentReference.category.coding.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| system | Σ | 1..1 | uriFixed Value | Element idDocumentReference.category.coding.systemShort description 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 be an absolute reference to some definition that establishes the system clearly and unambiguously.
https://fhir.synapxe.sg/ValueSet/acp-documentreference-categoryMappings
|
| version | Σ | 0..0 | string | There are no (further) constraints on this element Element idDocumentReference.category.coding.versionShort description 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 | Σ C | 1..1 | codeBinding | Element idDocumentReference.category.coding.codeShort description 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. acp-documentreference-category (required) ConditionsThe cardinality or value of this element may be affected by these constraints: cod-1 Constraints
|
| display | Σ C | 0..0 | string | There are no (further) constraints on this element Element idDocumentReference.category.coding.displayShort description 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. The cardinality or value of this element may be affected by these constraints: cod-1 Constraints
|
| userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idDocumentReference.category.coding.userSelectedShort description If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. 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..0 | string | There are no (further) constraints on this element Element idDocumentReference.category.textShort description 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.
|
| subject | Σ | 1..1 | Reference(Resource) | There are no (further) constraints on this element Element idDocumentReference.subjectShort description Who/what is the subject of the document DefinitionWho or what the document is about. The document 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 farm animals, or a set of patients that share a common exposure).
|
| context | C | 0..0 | Reference(QuestionnaireResponse) | Element idDocumentReference.contextShort description Context of the document content DefinitionDescribes the clinical encounter or type of care that the document content is associated with. Reference(QuestionnaireResponse) ConditionsThe cardinality or value of this element may be affected by these constraints: docRef-1, docRef-2 Constraints
|
| event | 0..0 | CodeableReference() | There are no (further) constraints on this element Element idDocumentReference.eventShort description Main clinical acts 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 type Code, 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 type, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more event codes are included, they shall not conflict with the values inherent in the class or type elements as such a conflict would create an ambiguous situation. This list of codes represents the main clinical acts being documented. http://terminology.hl7.org/ValueSet/v3-ActCode (example) Constraints
| |
| bodySite | Σ | 0..0 | CodeableReference(BodyStructure) | There are no (further) constraints on this element Element idDocumentReference.bodySiteShort description Body part included DefinitionThe anatomic structures included in the document. CodeableReference(BodyStructure) BindingSNOMED CT Body site concepts SNOMEDCTBodyStructures (example) Constraints
|
| facilityType | C | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idDocumentReference.facilityTypeShort description Kind of facility where patient was seen DefinitionThe kind of facility where the patient was seen. XDS Facility Type. FacilityTypeCodeValueSet (example) ConditionsThe cardinality or value of this element may be affected by these constraints: docRef-1 Constraints
|
| practiceSetting | C | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idDocumentReference.practiceSettingShort description Additional details about where the content was created (e.g. clinical specialty) DefinitionThis property may convey specifics about the practice setting where the content was created, often reflecting the clinical specialty. This is an important piece of metadata that providers often rely upon to quickly sort and/or filter out to find specific content. This element should be based on a coarse classification system for the class of specialty practice. Recommend the use of the classification system for Practice Setting, such as that described by the Subject Matter Domain in LOINC. Additional details about where the content was created (e.g. clinical specialty). PracticeSettingCodeValueSet (example) ConditionsThe cardinality or value of this element may be affected by these constraints: docRef-2 Constraints
|
| period | Σ | 0..0 | Period | There are no (further) constraints on this element Element idDocumentReference.periodShort description Time of service that is being documented DefinitionThe time period over which the service that is described by the document was provided.
|
| date | Σ | 0..1 | instant | There are no (further) constraints on this element Element idDocumentReference.dateShort description When this document reference was created Alternate namesindexed DefinitionWhen the document reference was created. Referencing/indexing time is used for tracking, organizing versions and searching.
|
| author | Σ | 0..1 | Reference(Practitioner | PractitionerRole | Organization | Device | Patient | RelatedPerson | CareTeam) | There are no (further) constraints on this element Element idDocumentReference.authorShort description Who and/or what authored the document DefinitionIdentifies who is responsible for adding the information to the document. Not necessarily who did the actual data entry (i.e. typist) or who was the source (informant). Reference(Practitioner | PractitionerRole | Organization | Device | Patient | RelatedPerson | CareTeam) Constraints
|
| attester | 0..0 | BackboneElement | There are no (further) constraints on this element Element idDocumentReference.attesterShort description Attests to accuracy of the document DefinitionA participant who has authenticated the accuracy of the document. Identifies responsibility for the accuracy of the document content. Only list each attester once.
| |
| custodian | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element idDocumentReference.custodianShort description Organization which maintains the document DefinitionIdentifies the organization or group who is responsible for ongoing maintenance of and access to the document. Identifies the logical organization (software system, vendor, or department) to go to find the current version, where to report issues, etc. This is different from the physical location (URL, disk drive, or server) of the document, which is the technical location of the document, which host may be delegated to the management of some other organization.
| |
| relatesTo | Σ | 0..0 | BackboneElement | There are no (further) constraints on this element Element idDocumentReference.relatesToShort description Relationships to other documents DefinitionRelationships that this document has with other document references that already exist. This element is labeled as a modifier because documents that append to other documents are incomplete on their own.
|
| description | Σ | 0..1 | markdown | There are no (further) constraints on this element Element idDocumentReference.descriptionShort description Human-readable description DefinitionHuman-readable description of the source document. Helps humans to assess whether the document is of interest. What the document is about, a terse summary of the document.
|
| securityLabel | Σ | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idDocumentReference.securityLabelShort description Document security-tags DefinitionA set of Security-Tag codes specifying the level of privacy/security of the Document found at DocumentReference.content.attachment.url. Note that DocumentReference.meta.security contains the security labels of the data elements in DocumentReference, while DocumentReference.securityLabel contains the security labels for the document the reference refers to. The distinction recognizes that the document may contain sensitive information, while the DocumentReference is metadata about the document and thus might not be as sensitive as the document. For example: a psychotherapy episode may contain highly sensitive information, while the metadata may simply indicate that some episode happened. Use of the Health Care Privacy/Security Classification (HCS) system of security-tag use is recommended. The confidentiality codes can carry multiple vocabulary items. HL7 has developed an understanding of security and privacy tags that might be desirable in a Document Sharing environment, called HL7 Healthcare Privacy and Security Classification System (HCS). The following specification is recommended but not mandated, as the vocabulary bindings are an administrative domain responsibility. The use of this method is up to the policy domain such as the XDS Affinity Domain or other Trust Domain where all parties including sender and recipients are trusted to appropriately tag and enforce. In the HL7 Healthcare Privacy and Security Classification (HCS) there are code systems specific to Confidentiality, Sensitivity, Integrity, and Handling Caveats. Some values would come from a local vocabulary as they are related to workflow roles and special projects. Example Security Labels from the Healthcare Privacy and Security Classification System. SecurityLabelExamples (example) Constraints
|
| content | Σ | 1..1 | BackboneElement | There are no (further) constraints on this element Element idDocumentReference.contentShort description Document referenced DefinitionThe document and format referenced. If there are multiple content element repetitions, these must all represent the same document in different format, or attachment metadata. Note that .relatesTo may also include references to other DocumentReference with a transforms relationship to represent the same document in multiple formats. content element shall not contain different versions of the same content. For version handling use multiple DocumentReference with .relatesTo.
|
| id | 0..0 | string | There are no (further) constraints on this element Element idDocumentReference.content.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idDocumentReference.content.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| modifierExtension | Σ ?! C | 0..0 | Extension | There are no (further) constraints on this element Element idDocumentReference.content.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| attachment | Σ | 1..1 | Attachment | There are no (further) constraints on this element Element idDocumentReference.content.attachmentShort description Where to access the document DefinitionThe document or URL of the document along with critical metadata to prove content has integrity.
|
| profile | Σ | 0..0 | BackboneElement | There are no (further) constraints on this element Element idDocumentReference.content.profileShort description Content profile rules for the document Alternate namesformat, formatCode DefinitionAn identifier of the document constraints, encoding, structure, and template that the document conforms to beyond the base format indicated in the mimeType. Note that IHE often issues URNs for formatCode codes, not all documents can be identified by a URI. For FHIR content, .profile should indicate the structureDefinition profile canonical URI(s) that the content complies with.
|
| AcpPatient (Patient) | C | Patient | There are no (further) constraints on this element Element idPatientShort description Information about an individual or animal receiving health care services Alternate namesSubjectOfCare Client Resident DefinitionDemographics and other administrative information about an individual or animal receiving care or other health-related services.
| |
| id | Σ | 0..1 | id | There are no (further) constraints on this element Element idPatient.idShort description 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. Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. |
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idPatient.metaShort description Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
| id | 0..0 | id | There are no (further) constraints on this element Element idPatient.meta.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idPatient.meta.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| versionId | Σ | 0..1 | id | There are no (further) constraints on this element Element idPatient.meta.versionIdShort description Version specific identifier DefinitionThe version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted. The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
|
| lastUpdated | Σ | 0..1 | instant | There are no (further) constraints on this element Element idPatient.meta.lastUpdatedShort description When the resource version last changed DefinitionWhen the resource last changed - e.g. when the version changed. This element is generally omitted in instances submitted in a PUT or POST. Instead, it is populated in the response instance and when retrieving information using a GET. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a read interaction.
|
| source | Σ | 0..0 | uri | There are no (further) constraints on this element Element idPatient.meta.sourceShort description Identifies where the resource comes from DefinitionA uri that identifies the source system of the resource. This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc. The exact use of the source (and the possible implied Provenance.entity.role and agent.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. The source may correspond to Provenance.entity.what[x] or Provenance.agent.who[x], though it may be a more general or abstract reference. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.
|
| profile | Σ | 0..0 | canonical(StructureDefinition) | There are no (further) constraints on this element Element idPatient.meta.profileShort description Profiles this resource claims to conform to DefinitionA list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url. It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set. canonical(StructureDefinition) Constraints
|
| security | Σ | 0..0 | CodingBinding | There are no (further) constraints on this element Element idPatient.meta.securityShort description Security Labels applied to this resource DefinitionSecurity labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored. Security Labels from the Healthcare Privacy and Security Classification System. AllSecurityLabels (extensible) Constraints
|
| tag | Σ | 0..0 | Coding | There are no (further) constraints on this element Element idPatient.meta.tagShort description Tags applied to this resource DefinitionTags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource. The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored. Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
|
| implicitRules | Σ ?! | 0..0 | uri | There are no (further) constraints on this element Element idPatient.implicitRulesShort description 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. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
|
| language | 0..0 | codeBinding | There are no (further) constraints on this element Element idPatient.languageShort description 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). IETF language tag for a human language
| |
| text | C | 0..0 | Narrative | There are no (further) constraints on this element Element idPatient.textShort description 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 can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. The cardinality or value of this element may be affected by these constraints: dom-6 Constraints
|
| contained | C | 0..0 | Resource | There are no (further) constraints on this element Element idPatient.containedShort description 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, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels. The cardinality or value of this element may be affected by these constraints: dom-2, dom-4, dom-3, dom-5 Mappings
|
| extension | C | 1..* | Extension | Element idPatient.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Constraints
|
| extPatientCitizenship | C | 1..1 | Extension(CodeableConcept) | Element idPatient.extension:extPatientCitizenshipShort description 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://hl7.org/fhir/StructureDefinition/patient-citizenship Constraints
|
| id | 0..0 | id | There are no (further) constraints on this element Element idPatient.extension:extPatientCitizenship.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idPatient.extension:extPatientCitizenship.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idPatient.extension:extPatientCitizenship.urlShort description identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/StructureDefinition/patient-citizenshipMappings
| |
| value[x] | C | 1..1 | There are no (further) constraints on this element Element idPatient.extension:extPatientCitizenship.value[x]Short description Value of extension DefinitionValue of extension - must be one of a constrained set of the data types (see Extensibility for a list). The cardinality or value of this element may be affected by these constraints: ext-1 Constraints
| |
| valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
| id | 0..0 | id | There are no (further) constraints on this element Element idPatient.extension:extPatientCitizenship.value[x].idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idPatient.extension:extPatientCitizenship.value[x].extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. 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 idPatient.extension:extPatientCitizenship.value[x].codingShort description Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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..0 | id | There are no (further) constraints on this element Element idPatient.extension:extPatientCitizenship.value[x].coding.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idPatient.extension:extPatientCitizenship.value[x].coding.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. 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 idPatient.extension:extPatientCitizenship.value[x].coding.systemShort description 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 be an absolute reference to some definition that establishes the system clearly and unambiguously.
https://fhir.synapxe.sg/ValueSet/acp-citizenshipMappings
|
| version | Σ | 0..0 | string | There are no (further) constraints on this element Element idPatient.extension:extPatientCitizenship.value[x].coding.versionShort description 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 | Σ C | 1..1 | codeBinding | There are no (further) constraints on this element Element idPatient.extension:extPatientCitizenship.value[x].coding.codeShort description 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. The cardinality or value of this element may be affected by these constraints: cod-1 Constraints
|
| display | Σ C | 1..1 | string | There are no (further) constraints on this element Element idPatient.extension:extPatientCitizenship.value[x].coding.displayShort description 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. The cardinality or value of this element may be affected by these constraints: cod-1 Constraints
|
| userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idPatient.extension:extPatientCitizenship.value[x].coding.userSelectedShort description If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. 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 idPatient.extension:extPatientCitizenship.value[x].textShort description 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.
|
| extPatientRace | C | 0..1 | Extension(CodeableConcept) | Element idPatient.extension:extPatientRaceShort description 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. https://fhir.synapxe.sg/StructureDefinition/ext-patient-race Constraints
|
| id | 0..0 | id | There are no (further) constraints on this element Element idPatient.extension:extPatientRace.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idPatient.extension:extPatientRace.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idPatient.extension:extPatientRace.urlShort description identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.synapxe.sg/StructureDefinition/ext-patient-raceMappings
| |
| value[x] | C | 1..1 | There are no (further) constraints on this element Element idPatient.extension:extPatientRace.value[x]Short description Value of extension DefinitionValue of extension - must be one of a constrained set of the data types (see Extensibility for a list). The cardinality or value of this element may be affected by these constraints: ext-1 Constraints
| |
| valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
| id | 0..0 | id | There are no (further) constraints on this element Element idPatient.extension:extPatientRace.value[x].idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idPatient.extension:extPatientRace.value[x].extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. 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 idPatient.extension:extPatientRace.value[x].codingShort description Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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..0 | id | There are no (further) constraints on this element Element idPatient.extension:extPatientRace.value[x].coding.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idPatient.extension:extPatientRace.value[x].coding.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. 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 idPatient.extension:extPatientRace.value[x].coding.systemShort description 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 be an absolute reference to some definition that establishes the system clearly and unambiguously.
https://fhir.synapxe.sg/ValueSet/acp-raceMappings
|
| version | Σ | 0..0 | string | There are no (further) constraints on this element Element idPatient.extension:extPatientRace.value[x].coding.versionShort description 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 | Σ C | 0..1 | codeBinding | There are no (further) constraints on this element Element idPatient.extension:extPatientRace.value[x].coding.codeShort description 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. The cardinality or value of this element may be affected by these constraints: cod-1 Constraints
|
| display | Σ C | 0..1 | string | There are no (further) constraints on this element Element idPatient.extension:extPatientRace.value[x].coding.displayShort description 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. The cardinality or value of this element may be affected by these constraints: cod-1 Constraints
|
| userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idPatient.extension:extPatientRace.value[x].coding.userSelectedShort description If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. 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..0 | string | There are no (further) constraints on this element Element idPatient.extension:extPatientRace.value[x].textShort description 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.
|
| extDeceasedInfo | C | 0..1 | Extension(Complex) | Element idPatient.extension:extDeceasedInfoShort description 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. Extension(Complex) Extension URLhttps://fhir.synapxe.sg/StructureDefinition/ext-deceased-info Constraints
|
| extPatientReligion | C | 0..1 | Extension(CodeableConcept) | Element idPatient.extension:extPatientReligionShort description 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. https://fhir.synapxe.sg/StructureDefinition/ext-patient-religion Constraints
|
| extStatusChangeReason | C | 0..1 | Extension(CodeableConcept) | Element idPatient.extension:extStatusChangeReasonShort description 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. https://fhir.synapxe.sg/StructureDefinition/ext-patient-status-change-reason Constraints
|
| modifierExtension | Σ ?! C | 0..0 | Extension | There are no (further) constraints on this element Element idPatient.modifierExtensionShort description 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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| identifier | Σ | 1..* | Identifier | Element idPatient.identifierShort description An identifier for this patient DefinitionAn identifier for this patient. Patients are almost always assigned specific numerical identifiers. Unordered, Open, by system(Pattern) Constraints
|
| primaryIdentifier | Σ | 1..1 | IdentifierPattern | Element idPatient.identifier:primaryIdentifierShort description An identifier for this patient DefinitionAn identifier for this patient. Patients are almost always assigned specific numerical identifiers.
{
"system": "https://fhir.synapxe.sg/NamingSystem/nric"
}Mappings
|
| id | 0..1 | id | There are no (further) constraints on this element Element idPatient.identifier:primaryIdentifier.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idPatient.identifier:primaryIdentifier.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| use | Σ ?! | 0..0 | codeBinding | There are no (further) constraints on this element Element idPatient.identifier:primaryIdentifier.useShort description usual | official | temp | secondary | old (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. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known .
|
| type | Σ | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idPatient.identifier:primaryIdentifier.typeShort description 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. IdentifierTypeCodes (extensible) Constraints
|
| system | Σ | 1..1 | uriFixed ValuePattern | Element idPatient.identifier:primaryIdentifier.systemShort description The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, an absolute 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. Identifier.system is always case sensitive.
https://fhir.synapxe.sg/NamingSystem/nricPattern https://fhir.synapxe.sg/NamingSystem/nricExamples General http://www.acme.com/identifiers/patientMappings
|
| value | Σ C | 1..1 | string | Element idPatient.identifier:primaryIdentifier.valueShort description 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 http://hl7.org/fhir/StructureDefinition/rendered-value). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe. The cardinality or value of this element may be affected by these constraints: ident-1 Constraints
General 123456Mappings
|
| period | Σ | 0..0 | Period | There are no (further) constraints on this element Element idPatient.identifier:primaryIdentifier.periodShort description Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use.
|
| assigner | Σ | 0..0 | Reference(Organization) | There are no (further) constraints on this element Element idPatient.identifier:primaryIdentifier.assignerShort description 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.
|
| secondaryIdentifier | Σ | 0..1 | IdentifierPattern | Element idPatient.identifier:secondaryIdentifierShort description An identifier for this patient DefinitionAn identifier for this patient. Patients are almost always assigned specific numerical identifiers.
{
"system": "https://fhir.synapxe.sg/NamingSystem/acp-id"
}Mappings
|
| id | 0..1 | id | There are no (further) constraints on this element Element idPatient.identifier:secondaryIdentifier.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idPatient.identifier:secondaryIdentifier.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| use | Σ ?! | 0..0 | codeBinding | There are no (further) constraints on this element Element idPatient.identifier:secondaryIdentifier.useShort description usual | official | temp | secondary | old (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. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known .
|
| type | Σ | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idPatient.identifier:secondaryIdentifier.typeShort description 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. IdentifierTypeCodes (extensible) Constraints
|
| system | Σ | 1..1 | uriFixed ValuePattern | Element idPatient.identifier:secondaryIdentifier.systemShort description The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, an absolute 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. Identifier.system is always case sensitive.
https://fhir.synapxe.sg/NamingSystem/acp-idPattern https://fhir.synapxe.sg/NamingSystem/acp-idExamples General http://www.acme.com/identifiers/patientMappings
|
| value | Σ C | 1..1 | string | There are no (further) constraints on this element Element idPatient.identifier:secondaryIdentifier.valueShort description 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 http://hl7.org/fhir/StructureDefinition/rendered-value). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe. The cardinality or value of this element may be affected by these constraints: ident-1 Constraints
General 123456Mappings
|
| period | Σ | 0..0 | Period | There are no (further) constraints on this element Element idPatient.identifier:secondaryIdentifier.periodShort description Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use.
|
| assigner | Σ | 0..0 | Reference(Organization) | There are no (further) constraints on this element Element idPatient.identifier:secondaryIdentifier.assignerShort description 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.
|
| active | Σ ?! | 1..1 | boolean | There are no (further) constraints on this element Element idPatient.activeShort description Whether this patient's record is in active use DefinitionWhether this patient record is in active use. Many systems use this property to mark as non-current patients, such as those that have not been seen for a period of time based on an organization's business rules. It is often used to filter patient lists to exclude inactive patients Deceased patients may also be marked as inactive for the same reasons, but may be active for some time after death. Need to be able to mark a patient record as not to be used because it was created in error. If a record is inactive, and linked to an active record, then future patient/record updates should occur on the other patient. This resource is generally assumed to be active if no value is provided for the active element
|
| name | Σ | 1..1 | HumanName | There are no (further) constraints on this element Element idPatient.nameShort description A name associated with the patient DefinitionA name associated with the individual. Need to be able to track the patient by multiple names. Examples are your official name and a partner name. A patient may have multiple names with different uses or applicable periods. For animals, the name is a "HumanName" in the sense that is assigned and used by humans and has the same patterns. Animal names may be communicated as given names, and optionally may include a family name.
|
| id | 0..0 | id | There are no (further) constraints on this element Element idPatient.name.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idPatient.name.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| use | Σ ?! | 0..0 | codeBinding | There are no (further) constraints on this element Element idPatient.name.useShort description usual | official | temp | nickname | anonymous | old | maiden DefinitionIdentifies the purpose for this name. Allows the appropriate name for a particular context of use to be selected from among a set of names. Applications can assume that a name is current unless it explicitly says that it is temporary or old. The use of a human name.
|
| text | Σ | 1..1 | string | There are no (further) constraints on this element Element idPatient.name.textShort description Text representation of the full name DefinitionSpecifies the entire name as it should be displayed e.g. on an application UI. This may be provided instead of or as well as the specific parts. A renderable, unencoded form. Can provide both a text representation and parts. Applications updating a name SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
|
| family | Σ | 0..0 | string | There are no (further) constraints on this element Element idPatient.name.familyShort description Family name (often called 'Surname') Alternate namessurname DefinitionThe part of a name that links to the genealogy. In some cultures (e.g. Eritrea) the family name of a son is the first name of his father. Family Name may be decomposed into specific parts using extensions (de, nl, es related cultures).
|
| given | Σ | 0..0 | string | There are no (further) constraints on this element Element idPatient.name.givenShort description Given names (not always 'first'). Includes middle names Alternate namesfirst name, middle name DefinitionGiven name. If only initials are recorded, they may be used in place of the full name parts. Initials may be separated into multiple given names but often aren't due to paractical limitations. This element is not called "first name" since given names do not always come first.
|
| prefix | Σ | 0..0 | string | There are no (further) constraints on this element Element idPatient.name.prefixShort description Parts that come before the name DefinitionPart of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the start of the name.
|
| suffix | Σ | 0..0 | string | There are no (further) constraints on this element Element idPatient.name.suffixShort description Parts that come after the name DefinitionPart of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the end of the name.
|
| period | Σ | 0..0 | Period | There are no (further) constraints on this element Element idPatient.name.periodShort description Time period when name was/is in use DefinitionIndicates the period of time when this name was valid for the named person. Allows names to be placed in historical context.
|
| telecom | Σ | 0..* | ContactPoint | There are no (further) constraints on this element Element idPatient.telecomShort description A contact detail for the individual DefinitionA contact detail (e.g. a telephone number or an email address) by which the individual may be contacted. People have (primary) ways to contact them in some way such as phone, email. A Patient may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and also to help with identification. The address might not go directly to the individual, but may reach another party that is able to proxy for the patient (i.e. home phone, or pet owner's phone).
|
| id | 0..0 | id | There are no (further) constraints on this element Element idPatient.telecom.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idPatient.telecom.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| system | Σ C | 0..1 | codeBinding | There are no (further) constraints on this element Element idPatient.telecom.systemShort description phone | fax | email | pager | url | sms | other DefinitionTelecommunications form for contact point - what communications system is required to make use of the contact. Telecommunications form for contact point. The cardinality or value of this element may be affected by these constraints: cpt-2 Constraints
|
| value | Σ C | 0..1 | string | There are no (further) constraints on this element Element idPatient.telecom.valueShort description The actual contact point details DefinitionThe actual contact point details, in a form that is meaningful to the designated communication system (i.e. phone number or email address). Need to support legacy numbers that are not in a tightly controlled format. Additional text data such as phone extension numbers, or notes about use of the contact are sometimes included in the value. The cardinality or value of this element may be affected by these constraints: cpt-2 Constraints
|
| use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idPatient.telecom.useShort description home | work | temp | old | mobile - purpose of this contact point DefinitionIdentifies the purpose for the contact point. Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose. Applications can assume that a contact is current unless it explicitly says that it is temporary or old. Use of contact point.
|
| rank | Σ | 0..0 | positiveInt | There are no (further) constraints on this element Element idPatient.telecom.rankShort description Specify preferred order of use (1 = highest) DefinitionSpecifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values. Note that rank does not necessarily follow the order in which the contacts are represented in the instance. Ranks need not be unique. E.g. it's possible to have multiple contacts with rank=1. If the ranks have different systems or uses, this would be interpreted to mean "X is my most preferred phone number, Y is my most preferred email address" or "X is my preferred home email and Y is my preferred work email". If the system and use for equally-ranked contacts are the same, then the level of preference is equivalent for both repetitions. Ranks need not be sequential and not all repetitions must have a rank. For example, it's possible to have 4 contacts with ranks of 2, 5 and two with no rank specified. That would be interpreted to mean the first is preferred over the second and no preference stated for the remaining contacts.
|
| period | Σ | 0..0 | Period | There are no (further) constraints on this element Element idPatient.telecom.periodShort description Time period when the contact point was/is in use DefinitionTime period when the contact point was/is in use.
|
| gender | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element idPatient.genderShort description male | female | other | unknown DefinitionAdministrative Gender - the gender that the patient is considered to have for administration and record keeping purposes. Needed for identification of the individual, in combination with (at least) name and birth date. The gender might not match the biological sex as determined by genetics or the individual's preferred identification. Note that for both humans and particularly animals, there are other legitimate possibilities than male and female, though the vast majority of systems and contexts only support male and female. Systems providing decision support or enforcing business rules should ideally do this on the basis of Observations dealing with the specific sex or gender aspect of interest (anatomical, chromosomal, social, etc.) However, because these observations are infrequently recorded, defaulting to the administrative gender is common practice. Where such defaulting occurs, rule enforcement should allow for the variation between administrative and biological, chromosomal and other gender aspects. For example, an alert about a hysterectomy on a male should be handled as a warning or overridable error, not a "hard" error. See the Patient Gender and Sex section for additional information about communicating patient gender and sex. The gender of a person used for administrative purposes. AdministrativeGender (required) Constraints
|
| birthDate | Σ | 1..1 | date | There are no (further) constraints on this element Element idPatient.birthDateShort description The date of birth for the individual DefinitionThe date of birth for the individual. Age of the individual drives many clinical processes. Partial dates are allowed if the specific date of birth is unknown. There is a standard extension "patient-birthTime" available that should be used where Time is required (such as in maternity/infant care systems).
|
| deceased[x] | Σ ?! | 0..1 | There are no (further) constraints on this element Element idPatient.deceased[x]Short description Indicates if the individual is deceased or not DefinitionIndicates if the individual is deceased or not. The fact that a patient is deceased influences the clinical process. Also, in human communication and relation management it is necessary to know whether the person is alive. If there's no value in the instance, it means there is no statement on whether or not the individual is deceased. Most systems will interpret the absence of a value as a sign of the person being alive.
| |
| deceasedBoolean | boolean | There are no (further) constraints on this element Data type | ||
| deceasedDateTime | dateTime | There are no (further) constraints on this element Data type | ||
| address | Σ | 1..1 | Address | There are no (further) constraints on this element Element idPatient.addressShort description An address for the individual DefinitionAn address for the individual. May need to keep track of patient addresses for contacting, billing or reporting requirements and also to help with identification. Patient may have multiple addresses with different uses or applicable periods.
|
| id | 0..1 | id | There are no (further) constraints on this element Element idPatient.address.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idPatient.address.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. 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 idPatient.address.useShort description home | work | temp | old | billing - purpose of this address DefinitionThe purpose of this address. Allows an appropriate address to be chosen from a list of many. Applications can assume that an address is current unless it explicitly says that it is temporary or old. The use of an address (home / work / etc.).
General homeMappings
|
| type | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element idPatient.address.typeShort description postal | physical | both DefinitionDistinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both. The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource). The type of an address (physical / postal).
General bothMappings
|
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idPatient.address.textShort description Text representation of the address DefinitionSpecifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts. A renderable, unencoded form. Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
General 137 Nowhere Street, Erewhon 9132Mappings
|
| line | Σ | 0..* | string | There are no (further) constraints on this element Element idPatient.address.lineShort description Street name, number, direction & P.O. Box etc. DefinitionThis component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.
General 137 Nowhere StreetMappings
|
| city | Σ | 0..1 | string | There are no (further) constraints on this element Element idPatient.address.cityShort description Name of city, town etc. Alternate namesMunicpality DefinitionThe name of the city, town, suburb, village or other community or delivery center.
General ErewhonMappings
|
| district | Σ | 0..1 | string | There are no (further) constraints on this element Element idPatient.address.districtShort description District name (aka county) Alternate namesCounty DefinitionThe name of the administrative area (county). District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.
General MadisonMappings
|
| state | Σ | 0..1 | string | There are no (further) constraints on this element Element idPatient.address.stateShort description Sub-unit of country (abbreviations ok) Alternate namesProvince, Territory DefinitionSub-unit of a country with limited sovereignty in a federally organized country. A code may be used if codes are in common use (e.g. US 2 letter state codes).
|
| postalCode | Σ | 1..1 | string | There are no (further) constraints on this element Element idPatient.address.postalCodeShort description Postal code for area Alternate namesZip DefinitionA postal code designating a region defined by the postal service.
General 9132Mappings
|
| country | Σ | 0..1 | string | There are no (further) constraints on this element Element idPatient.address.countryShort description Country (e.g. may be ISO 3166 2 or 3 letter code) DefinitionCountry - a nation as commonly understood or generally accepted. ISO 3166 2- or 3- letter codes MAY be used in place of a human readable country name.
|
| period | Σ | 0..0 | Period | There are no (further) constraints on this element Element idPatient.address.periodShort description Time period when address was/is in use DefinitionTime period when address was/is in use. Allows addresses to be placed in historical context.
General {
"start": "2010-03-23",
"end": "2010-07-01"
}Mappings
|
| maritalStatus | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idPatient.maritalStatusShort description Marital (civil) status of a patient DefinitionThis field contains a patient's most recent marital (civil) status. Most, if not all systems capture it. The domestic partnership status of a person. MaritalStatusCodes (extensible) Constraints
| |
| id | 0..0 | id | There are no (further) constraints on this element Element idPatient.maritalStatus.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idPatient.maritalStatus.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| coding | Σ | 0..1 | Coding | There are no (further) constraints on this element Element idPatient.maritalStatus.codingShort description Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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..0 | id | There are no (further) constraints on this element Element idPatient.maritalStatus.coding.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idPatient.maritalStatus.coding.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| system | Σ | 0..1 | uri | There are no (further) constraints on this element Element idPatient.maritalStatus.coding.systemShort description 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 be an absolute reference to some definition that establishes the system clearly and unambiguously.
|
| version | Σ | 0..0 | string | There are no (further) constraints on this element Element idPatient.maritalStatus.coding.versionShort description 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 | Σ C | 1..1 | code | There are no (further) constraints on this element Element idPatient.maritalStatus.coding.codeShort description 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. The cardinality or value of this element may be affected by these constraints: cod-1 Constraints
|
| display | Σ C | 1..1 | string | There are no (further) constraints on this element Element idPatient.maritalStatus.coding.displayShort description 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. The cardinality or value of this element may be affected by these constraints: cod-1 Constraints
|
| userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idPatient.maritalStatus.coding.userSelectedShort description If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. 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..0 | string | There are no (further) constraints on this element Element idPatient.maritalStatus.textShort description 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.
|
| multipleBirth[x] | 0..0 | There are no (further) constraints on this element Element idPatient.multipleBirth[x]Short description Whether patient is part of a multiple birth DefinitionIndicates whether the patient is part of a multiple (boolean) or indicates the actual birth order (integer). For disambiguation of multiple-birth children, especially relevant where the care provider doesn't meet the patient, such as labs. Where the valueInteger is provided, the number is the birth number in the sequence. E.g. The middle birth in triplets would be valueInteger=2 and the third born would have valueInteger=3 If a boolean value was provided for this triplets example, then all 3 patient records would have valueBoolean=true (the ordering is not indicated).
| ||
| photo | 0..0 | Attachment | There are no (further) constraints on this element Element idPatient.photoShort description Image of the patient DefinitionImage of the patient. Many EHR systems have the capability to capture an image of the patient. Fits with newer social media usage too. Guidelines:
| |
| contact | C | 0..0 | BackboneElement | There are no (further) constraints on this element Element idPatient.contactShort description A contact party (e.g. guardian, partner, friend) for the patient DefinitionA contact party (e.g. guardian, partner, friend) for the patient. Need to track people you can contact about the patient. Contact covers all kinds of contact parties: family members, business contacts, guardians, caregivers. Not applicable to register pedigree and family ties beyond use of having contact.
|
| communication | 0..0 | BackboneElement | There are no (further) constraints on this element Element idPatient.communicationShort description A language which may be used to communicate with the patient about his or her health DefinitionA language which may be used to communicate with the patient about his or her health. If a patient does not speak the local language, interpreters may be required, so languages spoken and proficiency are important things to keep track of both for patient and other persons of interest. If no language is specified, this implies that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple Patient.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.
| |
| generalPractitioner | 0..0 | Reference(Organization | Practitioner | PractitionerRole) | There are no (further) constraints on this element Element idPatient.generalPractitionerShort description Patient's nominated primary care provider Alternate namescareProvider DefinitionPatient's nominated care provider. This may be the primary care provider (in a GP context), or it may be a patient nominated care manager in a community/disability setting, or even organization that will provide people to perform the care provider roles. It is not to be used to record Care Teams, these should be in a CareTeam resource that may be linked to the CarePlan or EpisodeOfCare resources. Multiple GPs may be recorded against the patient for various reasons, such as a student that has his home GP listed along with the GP at university during the school semesters, or a "fly-in/fly-out" worker that has the onsite GP also included with his home GP to remain aware of medical issues. Jurisdictions may decide that they can profile this down to 1 if desired, or 1 per type. Reference(Organization | Practitioner | PractitionerRole) Constraints
| |
| managingOrganization | Σ | 1..1 | Reference(Organization) | There are no (further) constraints on this element Element idPatient.managingOrganizationShort description Organization that is the custodian of the patient record DefinitionOrganization that is the custodian of the patient record. Need to know who recognizes this patient record, manages and updates it. There is only one managing organization for a specific patient record. Other organizations will have their own Patient record, and may use the Link property to join the records together (or a Person resource which can include confidence ratings for the association).
|
| id | 0..0 | id | There are no (further) constraints on this element Element idPatient.managingOrganization.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. The cardinality or value of this element may be affected by these constraints: ele-1 Mappings
| |
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idPatient.managingOrganization.extensionShort description 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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| reference | Σ C | 1..1 | string | There are no (further) constraints on this element Element idPatient.managingOrganization.referenceShort description Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. The cardinality or value of this element may be affected by these constraints: ref-2, ref-1 Constraints
|
| type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element idPatient.managingOrganization.typeShort description Type the reference refers to (e.g. "Patient") - must be a resource in resources DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a known RESTful URL) or by resolving the target of the reference. Aa resource (or, for logical models, the URI of the logical model).
|
| identifier | Σ C | 0..0 | Identifier | There are no (further) constraints on this element Element idPatient.managingOrganization.identifierShort description Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the http://hl7.org/fhir/StructureDefinition/additionalIdentifier extension. The cardinality or value of this element may be affected by these constraints: ref-2 Constraints
|
| display | Σ C | 0..1 | string | There are no (further) constraints on this element Element idPatient.managingOrganization.displayShort description Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. The cardinality or value of this element may be affected by these constraints: ref-2 Constraints
|
| link | Σ ?! | 0..0 | BackboneElement | There are no (further) constraints on this element Element idPatient.linkShort description Link to a Patient or RelatedPerson resource that concerns the same actual individual DefinitionLink to a Patient or RelatedPerson resource that concerns the same actual individual. There are multiple use cases:
There is no assumption that linked patient records have mutual links.
|