Profile: CareConnect-GPC-Encounter-1
| CareConnect-GPC-Encounter-1 (Encounter) | C | Encounter | |
| id | Σ | 0..1 | id |
| meta | Σ | 0..1 | Meta |
| id | 0..1 | string | |
| extension | 0..* | Extension | |
| versionId | Σ | 0..1 | id |
| lastUpdated | Σ | 0..1 | instant |
| profile | Σ | 1..* | uri |
| security | Σ | 0..* | CodingBinding |
| tag | Σ | 0..* | Coding |
| implicitRules | Σ ?! | 0..1 | uri |
| language | 0..1 | codeBinding | |
| text | C | 0..1 | Narrative |
| contained | 0..* | Resource | |
| extension | 0..* | Extension | |
| encounterTransport | C | 0..1 | Extension(Complex) |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| transportType | C | 1..1 | Extension |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| url | 1..1 | uriFixed Value | |
| valueCodeableConcept | 0..1 | CodeableConcept | |
| transportPeriod | C | 0..1 | Extension |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| url | 1..1 | uriFixed Value | |
| valuePeriod | 0..1 | Period | |
| reasonForTransport | C | 0..1 | Extension |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| url | 1..1 | uriFixed Value | |
| valueString | 0..1 | string | |
| url | 1..1 | uriFixed Value | |
| value[x] | 0..0 | ||
| outcomeOfAttendance | C | 0..1 | Extension(CodeableConcept) |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| url | 1..1 | uriFixed Value | |
| valueCodeableConcept | 1..1 | CodeableConceptBinding | |
| emergencyCareDischargeStatus | C | 0..1 | Extension(CodeableConcept) |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| url | 1..1 | uriFixed Value | |
| valueCodeableConcept | 1..1 | CodeableConceptBinding | |
| modifierExtension | ?! | 0..* | Extension |
| identifier | Σ | 1..* | Identifier |
| id | 0..1 | string | |
| extension | 0..* | Extension | |
| use | Σ ?! | 0..1 | codeBinding |
| type | Σ | 0..1 | CodeableConceptBinding |
| system | Σ | 1..1 | uri |
| value | Σ | 1..1 | string |
| period | Σ | 0..1 | Period |
| assigner | Σ | 0..1 | Reference(CareConnect-Organization-1) |
| status | Σ ?! | 1..1 | codeBinding |
| statusHistory | 0..1 | BackboneElement | |
| id | 0..1 | string | |
| extension | 0..* | Extension | |
| modifierExtension | Σ ?! | 0..* | Extension |
| status | 1..1 | codeBinding | |
| period | 1..1 | Period | |
| class | Σ | 0..1 | CodingBinding |
| classHistory | 0..* | BackboneElement | |
| id | 0..1 | string | |
| extension | 0..* | Extension | |
| modifierExtension | Σ ?! | 0..* | Extension |
| class | 1..1 | CodingBinding | |
| period | 1..1 | Period | |
| type | Σ | 1..1 | CodeableConcept |
| id | 0..1 | string | |
| extension | 0..* | Extension | |
| coding | Σ | 0..1 | Coding |
| snomedCT | Σ | 0..* | CodingBinding |
| id | 0..1 | string | |
| extension | 0..* | Extension | |
| snomedCTDescriptionID | C | 0..1 | Extension(Complex) |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| descriptionId | C | 1..1 | Extension |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| url | 1..1 | uriFixed Value | |
| valueId | 0..1 | id | |
| descriptionDisplay | C | 1..1 | Extension |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| url | 1..1 | uriFixed Value | |
| valueString | 0..1 | string | |
| url | 1..1 | uriFixed Value | |
| value[x] | 0..0 | ||
| system | Σ | 1..1 | uriFixed Value |
| version | Σ | 0..1 | string |
| code | Σ | 1..1 | code |
| display | Σ | 1..1 | string |
| userSelected | Σ | 0..1 | boolean |
| text | Σ | 0..1 | string |
| priority | 0..1 | CodeableConcept | |
| subject | Σ | 1..1 | Reference(CareConnect-GPC-Patient-1) |
| episodeOfCare | Σ | 0..* | Reference(EpisodeOfCare) |
| incomingReferral | 0..* | Reference(CareConnect-ReferralRequest-1) | |
| participant | Σ | 1..* | BackboneElement |
| id | 0..1 | string | |
| extension | 0..* | Extension | |
| modifierExtension | Σ ?! | 0..* | Extension |
| type | S Σ | 0..* | CodeableConceptBinding |
| period | 0..1 | Period | |
| individual | Σ | 1..1 | Reference(RelatedPerson | CareConnect-GPC-Practitioner-1) |
| appointment | Σ | 0..1 | Reference(Appointment) |
| period | S | 0..1 | Period |
| id | 0..1 | string | |
| extension | 0..* | Extension | |
| start | Σ C | 1..1 | dateTime |
| end | Σ C | 0..1 | dateTime |
| length | 0..1 | Duration | |
| reason | Σ | 0..* | CodeableConceptBinding |
| id | 0..1 | string | |
| extension | 0..* | Extension | |
| coding | Σ | 0..* | Coding |
| snomedCT | Σ | 0..1 | Coding |
| id | 0..1 | string | |
| extension | 0..* | Extension | |
| snomedCTDescriptionID | C | 0..1 | Extension(Complex) |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| descriptionId | C | 1..1 | Extension |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| url | 1..1 | uriFixed Value | |
| valueId | 0..1 | id | |
| descriptionDisplay | C | 1..1 | Extension |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| url | 1..1 | uriFixed Value | |
| valueString | 0..1 | string | |
| url | 1..1 | uriFixed Value | |
| value[x] | 0..0 | ||
| system | Σ | 1..1 | uriFixed Value |
| version | Σ | 0..1 | string |
| code | Σ | 1..1 | code |
| display | Σ | 1..1 | string |
| userSelected | Σ | 0..1 | boolean |
| text | Σ | 0..1 | string |
| diagnosis | Σ | 0..* | BackboneElement |
| id | 0..1 | string | |
| extension | 0..* | Extension | |
| modifierExtension | Σ ?! | 0..* | Extension |
| condition | 1..1 | Reference(CareConnect-Procedure-1 | CareConnect-Condition-1) | |
| role | 0..1 | CodeableConceptBinding | |
| rank | 0..1 | positiveInt | |
| account | 0..* | Reference(Account) | |
| hospitalization | 0..1 | BackboneElement | |
| id | 0..1 | string | |
| extension | 0..* | Extension | |
| admissionMethod | C | 0..1 | Extension(CodeableConcept) |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| url | 1..1 | uriFixed Value | |
| valueCodeableConcept | 1..1 | CodeableConceptBinding | |
| dischargeMethod | C | 0..1 | Extension(CodeableConcept) |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| url | 1..1 | uriFixed Value | |
| valueCodeableConcept | 1..1 | CodeableConceptBinding | |
| modifierExtension | Σ ?! | 0..* | Extension |
| preAdmissionIdentifier | 0..1 | Identifier | |
| id | 0..1 | string | |
| extension | 0..* | Extension | |
| use | Σ ?! | 0..1 | codeBinding |
| type | Σ | 0..1 | CodeableConceptBinding |
| system | Σ | 1..1 | uri |
| value | Σ | 1..1 | string |
| period | Σ | 0..1 | Period |
| assigner | Σ | 0..1 | Reference(CareConnect-Organization-1) |
| origin | 0..1 | Reference(CareConnect-Location-1) | |
| admitSource | 0..1 | CodeableConceptBinding | |
| reAdmission | 0..1 | CodeableConcept | |
| id | 0..1 | string | |
| extension | 0..* | Extension | |
| coding | Σ | 0..* | Coding |
| snomedCT | Σ | 0..1 | Coding |
| id | 0..1 | string | |
| extension | 0..* | Extension | |
| snomedCTDescriptionID | C | 0..1 | Extension(Complex) |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| descriptionId | C | 1..1 | Extension |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| url | 1..1 | uriFixed Value | |
| valueId | 0..1 | id | |
| descriptionDisplay | C | 1..1 | Extension |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| url | 1..1 | uriFixed Value | |
| valueString | 0..1 | string | |
| url | 1..1 | uriFixed Value | |
| value[x] | 0..0 | ||
| system | Σ | 1..1 | uriFixed Value |
| version | Σ | 0..1 | string |
| code | Σ | 1..1 | code |
| display | Σ | 1..1 | string |
| userSelected | Σ | 0..1 | boolean |
| text | Σ | 0..1 | string |
| dietPreference | 0..* | CodeableConceptBinding | |
| specialCourtesy | 0..* | CodeableConceptBinding | |
| specialArrangement | 0..* | CodeableConceptBinding | |
| destination | 0..1 | Reference(CareConnect-Location-1) | |
| dischargeDisposition | 0..1 | CodeableConcept | |
| location | 0..* | BackboneElement | |
| id | 0..1 | string | |
| extension | 0..* | Extension | |
| modifierExtension | Σ ?! | 0..* | Extension |
| location | 1..1 | Reference(CareConnect-Location-1) | |
| status | 0..1 | codeBinding | |
| period | 0..1 | Period | |
| serviceProvider | S | 0..1 | Reference(CareConnect-GPC-Organization-1) |
| partOf | 0..1 | Reference(CareConnect-Encounter-1) |
| Encounter | |||
| Short | An interaction during which services are provided to the patient | ||
| Definition | An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient. | ||
| Cardinality | 0..* | ||
| Alias | Visit | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.id | |||
| Short | Logical id of this artifact | ||
| Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. | ||
| Cardinality | 0..1 | ||
| Type | id | ||
| Summary | True | ||
| Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | ||
| Encounter.meta | |||
| Short | Metadata about the resource | ||
| Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource. | ||
| Cardinality | 0..1 | ||
| Type | Meta | ||
| Summary | True | ||
| Encounter.meta.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Encounter.meta.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Mappings |
| ||
| Encounter.meta.versionId | |||
| Short | Version specific identifier | ||
| Definition | The version specific identifier, as it appears in the version portion of the URL. This values changes when the resource is created, updated, or deleted. | ||
| Cardinality | 0..1 | ||
| Type | id | ||
| Summary | True | ||
| Comments | 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. | ||
| Encounter.meta.lastUpdated | |||
| Short | When the resource version last changed | ||
| Definition | When the resource last changed - e.g. when the version changed. | ||
| Cardinality | 0..1 | ||
| Type | instant | ||
| Summary | True | ||
| Comments | This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. | ||
| Encounter.meta.profile | |||
| Short | Profiles this resource claims to conform to | ||
| Definition | A list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url. | ||
| Cardinality | 1..* | ||
| Type | uri | ||
| Summary | True | ||
| Comments | 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. | ||
| Encounter.meta.security | |||
| Short | Security Labels applied to this resource | ||
| Definition | Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. | ||
| Cardinality | 0..* | ||
| Type | Coding | ||
| Binding | Security Labels from the Healthcare Privacy and Security Classification System. | ||
| Summary | True | ||
| Comments | 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. | ||
| Encounter.meta.tag | |||
| Short | Tags applied to this resource | ||
| Definition | Tags 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. | ||
| Cardinality | 0..* | ||
| Type | Coding | ||
| Binding | Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones" | ||
| Summary | True | ||
| Comments | 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. | ||
| Encounter.implicitRules | |||
| Short | A set of rules under which this content was created | ||
| Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. | ||
| Cardinality | 0..1 | ||
| Type | uri | ||
| Modifier | True | ||
| Summary | True | ||
| Comments | Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. | ||
| Encounter.language | |||
| Short | Language of the resource content | ||
| Definition | The base language in which the resource is written. | ||
| Cardinality | 0..1 | ||
| Type | code | ||
| Binding | A human language. Binding extensions
| ||
| Comments | 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). | ||
| Encounter.text | |||
| Short | Text summary of the resource, for human interpretation | ||
| Definition | A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. | ||
| Cardinality | 0..1 | ||
| Type | Narrative | ||
| Alias | narrative, html, xhtml, display | ||
| Comments | Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: dom-1 | ||
| Mappings |
| ||
| Encounter.contained | |||
| Short | Contained, inline Resources | ||
| Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. | ||
| Cardinality | 0..* | ||
| Type | Resource | ||
| Alias | inline resources, anonymous resources, contained resources | ||
| Comments | 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. | ||
| Mappings |
| ||
| Encounter.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the resource. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) | ||
| Mappings |
| ||
| Encounter.extension:encounterTransport | |||
| Short | Encounter transport | ||
| Definition | Encounter transport. | ||
| Cardinality | 0..1 | ||
| Type | Extension(Complex) | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:encounterTransport.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:encounterTransport.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:encounterTransport.extension:transportType | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 1..1 | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:encounterTransport.extension:transportType.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:encounterTransport.extension:transportType.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:encounterTransport.extension:transportType.url | |||
| Short | identifies the meaning of the extension | ||
| Definition | Source of the definition for the extension code - a logical name or a URL. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Comments | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | transportType | ||
| Mappings |
| ||
| Encounter.extension:encounterTransport.extension:transportType.value[x]:valueCodeableConcept | |||
| Short | Transport Type | ||
| Definition | Transport Type. | ||
| Cardinality | 0..1 | ||
| Type | CodeableConcept | ||
| Comments | A stream of bytes, base64 encoded | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:encounterTransport.extension:transportPeriod | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..1 | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:encounterTransport.extension:transportPeriod.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:encounterTransport.extension:transportPeriod.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:encounterTransport.extension:transportPeriod.url | |||
| Short | identifies the meaning of the extension | ||
| Definition | Source of the definition for the extension code - a logical name or a URL. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Comments | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | transportPeriod | ||
| Mappings |
| ||
| Encounter.extension:encounterTransport.extension:transportPeriod.value[x]:valuePeriod | |||
| Short | Transport Period | ||
| Definition | Transport Period. | ||
| Cardinality | 0..1 | ||
| Type | Period | ||
| Comments | A stream of bytes, base64 encoded | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:encounterTransport.extension:reasonForTransport | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..1 | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:encounterTransport.extension:reasonForTransport.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:encounterTransport.extension:reasonForTransport.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:encounterTransport.extension:reasonForTransport.url | |||
| Short | identifies the meaning of the extension | ||
| Definition | Source of the definition for the extension code - a logical name or a URL. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Comments | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | reasonForTransport | ||
| Mappings |
| ||
| Encounter.extension:encounterTransport.extension:reasonForTransport.value[x]:valueString | |||
| Short | Reason for transport | ||
| Definition | Reason for transport. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Comments | A stream of bytes, base64 encoded | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:encounterTransport.url | |||
| Short | identifies the meaning of the extension | ||
| Definition | Source of the definition for the extension code - a logical name or a URL. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Comments | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | https://fhir.hl7.org.uk/STU3/StructureDefinition/Extension-CareConnect-EncounterTransport-1 | ||
| Mappings |
| ||
| Encounter.extension:encounterTransport.value[x] | |||
| Short | Value of extension | ||
| Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||
| Cardinality | 0..0 | ||
| Type | Reference(), base64Binary, boolean, code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, SampledData, Signature, Timing, Meta | ||
| Comments | A stream of bytes, base64 encoded | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:outcomeOfAttendance | |||
| Short | An extension to the Encounter resource to record the outcome of an Out-Patient attendance. | ||
| Definition | Optional Extension Element - found in all resources. | ||
| Cardinality | 0..1 | ||
| Type | Extension(CodeableConcept) | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:outcomeOfAttendance.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:outcomeOfAttendance.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:outcomeOfAttendance.url | |||
| Short | identifies the meaning of the extension | ||
| Definition | Source of the definition for the extension code - a logical name or a URL. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Comments | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | https://fhir.hl7.org.uk/STU3/StructureDefinition/Extension-CareConnect-OutcomeOfAttendance-1 | ||
| Mappings |
| ||
| Encounter.extension:outcomeOfAttendance.value[x]:valueCodeableConcept | |||
| Short | This records the outcome of an Out-Patient Attendance Consultant. | ||
| Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||
| Cardinality | 1..1 | ||
| Type | CodeableConcept | ||
| Binding | This records the outcome of an Out-Patient Attendance Consultant. NHS Data Model and Dictionary Outcome Of Attendance (required) | ||
| Comments | A stream of bytes, base64 encoded | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:emergencyCareDischargeStatus | |||
| Short | An extension to the Encounter resource which is used indicate the status of the Patient on discharge from an Emergency Care Department. | ||
| Definition | Optional Extension Element - found in all resources. | ||
| Cardinality | 0..1 | ||
| Type | Extension(CodeableConcept) | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:emergencyCareDischargeStatus.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:emergencyCareDischargeStatus.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.extension:emergencyCareDischargeStatus.url | |||
| Short | identifies the meaning of the extension | ||
| Definition | Source of the definition for the extension code - a logical name or a URL. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Comments | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | https://fhir.hl7.org.uk/STU3/StructureDefinition/Extension-CareConnect-EmergencyCareDischargeStatus-1 | ||
| Mappings |
| ||
| Encounter.extension:emergencyCareDischargeStatus.value[x]:valueCodeableConcept | |||
| Short | The status of the Patient on discharge from an Emergency Care Department. | ||
| Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||
| Cardinality | 1..1 | ||
| Type | CodeableConcept | ||
| Binding | The status of the Patient on discharge from an Emergency Care Department. | ||
| Comments | A stream of bytes, base64 encoded | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.modifierExtension | |||
| Short | Extensions that cannot be ignored | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Mappings |
| ||
| Encounter.identifier | |||
| Short | Identifier(s) by which this encounter is known | ||
| Definition | Identifier(s) by which this encounter is known. | ||
| Cardinality | 1..* | ||
| Type | Identifier | ||
| Summary | True | ||
| Mappings |
| ||
| Encounter.identifier.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Encounter.identifier.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Mappings |
| ||
| Encounter.identifier.use | |||
| Short | usual | official | temp | secondary (If known) | ||
| Definition | The purpose of this identifier. | ||
| Cardinality | 0..1 | ||
| Type | code | ||
| Binding | Identifies the purpose for this identifier, if known . | ||
| Modifier | True | ||
| Summary | True | ||
| Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. | ||
| Comments | This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. | ||
| Mappings |
| ||
| Encounter.identifier.type | |||
| Short | Description of identifier | ||
| Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. | ||
| Cardinality | 0..1 | ||
| Type | CodeableConcept | ||
| Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. | ||
| Summary | True | ||
| Requirements | Allows users to make use of identifiers when the identifier system is not known. | ||
| Comments | 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. | ||
| Mappings |
| ||
| Encounter.identifier.system | |||
| Short | The namespace for the identifier value | ||
| Definition | Establishes the namespace for the value - that is, a URL that describes a set values that are unique. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Summary | True | ||
| Requirements | 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. | ||
| Examples | Generalhttp://www.acme.com/identifiers/patient | ||
| Mappings |
| ||
| Encounter.identifier.value | |||
| Short | The value that is unique | ||
| Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. | ||
| Cardinality | 1..1 | ||
| Type | string | ||
| Summary | True | ||
| Comments | If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. | ||
| Examples | General123456 | ||
| Mappings |
| ||
| Encounter.identifier.period | |||
| Short | Time period when id is/was valid for use | ||
| Definition | Time period during which identifier is/was valid for use. | ||
| Cardinality | 0..1 | ||
| Type | Period | ||
| Summary | True | ||
| Mappings |
| ||
| Encounter.identifier.assigner | |||
| Short | Organization that issued id (may be just text) | ||
| Definition | Organization that issued/manages the identifier. | ||
| Cardinality | 0..1 | ||
| Type | Reference(CareConnect-Organization-1) | ||
| Summary | True | ||
| Comments | 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. | ||
| Mappings |
| ||
| Encounter.status | |||
| Short | planned | arrived | triaged | in-progress | onleave | finished | cancelled + | ||
| Definition | planned | arrived | triaged | in-progress | onleave | finished | cancelled +. | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Binding | Current state of the encounter | ||
| Modifier | True | ||
| Summary | True | ||
| Comments | Note that internal business rules will detemine the appropraite transitions that may occur between statuses (and also classes). This element is labeled as a modifier because the status contains codes that mark the encounter as not currently valid. | ||
| Mappings |
| ||
| Encounter.statusHistory | |||
| Short | List of past encounter statuses | ||
| Definition | The status history permits the encounter resource to contain the status history without needing to read through the historical versions of the resource, or even have the server store them. | ||
| Cardinality | 0..1 | ||
| Type | BackboneElement | ||
| Comments | The current status is always found in the current version of the resource, not the status history. | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.statusHistory.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Encounter.statusHistory.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Mappings |
| ||
| Encounter.statusHistory.modifierExtension | |||
| Short | Extensions that cannot be ignored | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Mappings |
| ||
| Encounter.statusHistory.status | |||
| Short | planned | arrived | triaged | in-progress | onleave | finished | cancelled + | ||
| Definition | planned | arrived | triaged | in-progress | onleave | finished | cancelled +. | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Binding | Current state of the encounter | ||
| Mappings |
| ||
| Encounter.statusHistory.period | |||
| Short | The time that the episode was in the specified status | ||
| Definition | The time that the episode was in the specified status. | ||
| Cardinality | 1..1 | ||
| Type | Period | ||
| Mappings |
| ||
| Encounter.class | |||
| Short | inpatient | outpatient | ambulatory | emergency + | ||
| Definition | inpatient | outpatient | ambulatory | emergency +. | ||
| Cardinality | 0..1 | ||
| Type | Coding | ||
| Binding | Classification of the encounter | ||
| Summary | True | ||
| Mappings |
| ||
| Encounter.classHistory | |||
| Short | List of past encounter classes | ||
| Definition | The class history permits the tracking of the encounters transitions without needing to go through the resource history. This would be used for a case where an admission starts of as an emergency encounter, then transisions into an inpatient scenario. Doing this and not restarting a new encounter ensures that any lab/diagnostic results can more easily follow the patient and not require re-processing and not get lost or cancelled during a kindof discharge from emergency to inpatient. | ||
| Cardinality | 0..* | ||
| Type | BackboneElement | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.classHistory.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Encounter.classHistory.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Mappings |
| ||
| Encounter.classHistory.modifierExtension | |||
| Short | Extensions that cannot be ignored | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Mappings |
| ||
| Encounter.classHistory.class | |||
| Short | Classification of the encounter | ||
| Definition | Classification of the encounter. | ||
| Cardinality | 1..1 | ||
| Type | Coding | ||
| Binding | Classification of the encounter | ||
| Mappings |
| ||
| Encounter.classHistory.period | |||
| Short | The time that the episode was in the specified class | ||
| Definition | The time that the episode was in the specified class. | ||
| Cardinality | 1..1 | ||
| Type | Period | ||
| Mappings |
| ||
| Encounter.type | |||
| Short | Specific type of encounter | ||
| Definition | Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation). | ||
| Cardinality | 1..1 | ||
| Type | CodeableConcept | ||
| Binding | The type of encounter | ||
| Summary | True | ||
| Comments | Since there are many ways to further classify encounters, this element is 0..*. | ||
| Mappings |
| ||
| Encounter.type.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Encounter.type.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Mappings |
| ||
| Encounter.type.coding | |||
| Short | Code defined by a terminology system | ||
| Definition | A reference to a code defined by a terminology system. | ||
| Cardinality | 0..1 | ||
| Type | Coding | ||
| Summary | True | ||
| Requirements | Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. | ||
| Comments | 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. | ||
| Slicing | Unordered, Open, by system(Value) | ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT | |||
| Short | Code defined by a terminology system | ||
| Definition | A reference to a code defined by a terminology system. | ||
| Cardinality | 0..* | ||
| Type | Coding | ||
| Binding | A code from the SNOMED Clinical Terminology UK coding system that describes an encounter between a care professional and the patient (or patient's record). | ||
| Summary | True | ||
| Requirements | Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. | ||
| Comments | 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. | ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT.extension:snomedCTDescriptionID | |||
| Short | The SNOMED CT Description ID for the display | ||
| Definition | The SNOMED CT Description ID for the display. | ||
| Cardinality | 0..1 | ||
| Type | Extension(Complex) | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT.extension:snomedCTDescriptionID.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT.extension:snomedCTDescriptionID.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionId | |||
| Short | The SNOMED CT Description ID | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 1..1 | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionId.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionId.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionId.url | |||
| Short | identifies the meaning of the extension | ||
| Definition | Source of the definition for the extension code - a logical name or a URL. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Comments | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | descriptionId | ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionId.value[x]:valueId | |||
| Short | The SNOMED CT Description ID | ||
| Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||
| Cardinality | 0..1 | ||
| Type | id | ||
| Comments | A stream of bytes, base64 encoded | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionDisplay | |||
| Short | The SNOMED CT display for the description ID | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 1..1 | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionDisplay.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionDisplay.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionDisplay.url | |||
| Short | identifies the meaning of the extension | ||
| Definition | Source of the definition for the extension code - a logical name or a URL. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Comments | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | descriptionDisplay | ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionDisplay.value[x]:valueString | |||
| Short | The SNOMED CT display for the description ID | ||
| Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Comments | A stream of bytes, base64 encoded | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT.extension:snomedCTDescriptionID.url | |||
| Short | identifies the meaning of the extension | ||
| Definition | Source of the definition for the extension code - a logical name or a URL. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Comments | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | https://fhir.hl7.org.uk/STU3/StructureDefinition/Extension-coding-sctdescid | ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT.extension:snomedCTDescriptionID.value[x] | |||
| Short | Value of extension | ||
| Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||
| Cardinality | 0..0 | ||
| Type | Reference(), base64Binary, boolean, code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, SampledData, Signature, Timing | ||
| Comments | A stream of bytes, base64 encoded | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT.system | |||
| Short | Identity of the terminology system | ||
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Summary | True | ||
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | ||
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. | ||
| Fixed Value | http://snomed.info/sct | ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT.version | |||
| Short | Version of the system - if relevant | ||
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Summary | True | ||
| Comments | 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. | ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT.code | |||
| Short | Symbol in syntax defined by the system | ||
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Summary | True | ||
| Requirements | Need to refer to a particular code in the system. | ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT.display | |||
| Short | Representation defined by the system | ||
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | ||
| Cardinality | 1..1 | ||
| Type | string | ||
| Summary | True | ||
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | ||
| Mappings |
| ||
| Encounter.type.coding:snomedCT.userSelected | |||
| Short | If this coding was chosen directly by the user | ||
| Definition | Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). | ||
| Cardinality | 0..1 | ||
| Type | boolean | ||
| Summary | True | ||
| Requirements | 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. | ||
| Comments | 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. | ||
| Mappings |
| ||
| Encounter.type.text | |||
| Short | Plain text representation of the consultation type as displayed by system | ||
| Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Summary | True | ||
| Requirements | 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. | ||
| Comments | Very often the text is the same as a displayName of one of the codings. | ||
| Mappings |
| ||
| Encounter.priority | |||
| Short | Indicates the urgency of the encounter | ||
| Definition | Indicates the urgency of the encounter. | ||
| Cardinality | 0..1 | ||
| Type | CodeableConcept | ||
| Binding | Indicates the urgency of the encounter. | ||
| Mappings |
| ||
| Encounter.subject | |||
| Short | Reference to Patient resource representing the Patient against whom the source consultation/encounter was recorded. | ||
| Definition | The patient present at the encounter. | ||
| Cardinality | 1..1 | ||
| Type | Reference(CareConnect-GPC-Patient-1) | ||
| Summary | True | ||
| Alias | patient | ||
| Comments | While the encounter is always about the patient, the patient may not actually be known in all contexts of use, and there may be a group of patients that could be anonymous (such as in a group therapy for Alcoholics Anonymous - where the recording of the encounter could be used for billing on the number of people/staff and not important to the context of the specific patients) or alternately in veterinary care a herd of sheep receiving treatment (where the animals are not individually tracked). | ||
| Mappings |
| ||
| Encounter.episodeOfCare | |||
| Short | Episode(s) of care that this encounter should be recorded against | ||
| Definition | Where a specific encounter should be classified as a part of a specific episode(s) of care this field should be used. This association can facilitate grouping of related encounters together for a specific purpose, such as government reporting, issue tracking, association via a common problem. The association is recorded on the encounter as these are typically created after the episode of care, and grouped on entry rather than editing the episode of care to append another encounter to it (the episode of care could span years). | ||
| Cardinality | 0..* | ||
| Type | Reference(EpisodeOfCare) | ||
| Summary | True | ||
| Mappings |
| ||
| Encounter.incomingReferral | |||
| Short | The ReferralRequest that initiated this encounter | ||
| Definition | The referral request this encounter satisfies (incoming referral). | ||
| Cardinality | 0..* | ||
| Type | Reference(CareConnect-ReferralRequest-1) | ||
| Mappings |
| ||
| Encounter.participant | |||
| Short | List of participants involved in the encounter | ||
| Definition | The list of people responsible for providing the service. | ||
| Cardinality | 1..* | ||
| Type | BackboneElement | ||
| Summary | True | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.participant.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Encounter.participant.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Mappings |
| ||
| Encounter.participant.modifierExtension | |||
| Short | Extensions that cannot be ignored | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Mappings |
| ||
| Encounter.participant.type | |||
| Short | Role of participant in encounter | ||
| Definition | Role of participant in encounter. | ||
| Cardinality | 0..* | ||
| Type | CodeableConcept | ||
| Binding | Role of participant in encounter | ||
| Must Support | True | ||
| Summary | True | ||
| Comments | The participant type indicates how an individual partitipates in an encounter. It includes non-practitioner participants, and for practitioners this is to describe the action type in the context of this encounter (e.g. Admitting Dr, Attending Dr, Translator, Consulting Dr). This is different to the practitioner roles which are functional roles, derived from terms of employment, education, licensing, etc. | ||
| Mappings |
| ||
| Encounter.participant.period | |||
| Short | Period of time during the encounter that the participant participated | ||
| Definition | The period of time that the specified participant participated in the encounter. These can overlap or be sub-sets of the overall encounter's period. | ||
| Cardinality | 0..1 | ||
| Type | Period | ||
| Mappings |
| ||
| Encounter.participant.individual | |||
| Short | Persons involved in the encounter other than the patient | ||
| Definition | Persons involved in the encounter other than the patient. | ||
| Cardinality | 1..1 | ||
| Type | Reference(RelatedPerson | CareConnect-GPC-Practitioner-1) | ||
| Summary | True | ||
| Mappings |
| ||
| Encounter.appointment | |||
| Short | The appointment that scheduled this encounter | ||
| Definition | The appointment that scheduled this encounter. | ||
| Cardinality | 0..1 | ||
| Type | Reference(Appointment) | ||
| Summary | True | ||
| Mappings |
| ||
| Encounter.period | |||
| Short | The start and end time of the encounter | ||
| Definition | The start and end time of the encounter. | ||
| Cardinality | 0..1 | ||
| Type | Period | ||
| Must Support | True | ||
| Comments | If not (yet) known, the end of the Period may be omitted. | ||
| Mappings |
| ||
| Encounter.period.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Encounter.period.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Mappings |
| ||
| Encounter.period.start | |||
| Short | Starting time with inclusive boundary | ||
| Definition | The start of the period. The boundary is inclusive. This should be populated with the displayed consultation date and time. | ||
| Cardinality | 1..1 | ||
| Type | dateTime | ||
| Summary | True | ||
| Comments | If the low element is missing, the meaning is that the low boundary is not known. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: per-1 | ||
| Mappings |
| ||
| Encounter.period.end | |||
| Short | End time with inclusive boundary, if not ongoing | ||
| Definition | The end of the period. If the end of the period is missing, it means that the period is ongoing. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. This should be populated where the encounter end date and time is known or calculated and populated where the duration is known. | ||
| Cardinality | 0..1 | ||
| Type | dateTime | ||
| Summary | True | ||
| Comments | The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has a end value of 2012-02-03. | ||
| Meaning when missing | If the end of the period is missing, it means that the period is ongoing | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: per-1 | ||
| Mappings |
| ||
| Encounter.length | |||
| Short | Quantity of time the encounter lasted (less time absent) | ||
| Definition | Quantity of time the encounter lasted. This excludes the time during leaves of absence. | ||
| Cardinality | 0..1 | ||
| Type | Duration | ||
| Comments | May differ from the time the Encounter.period lasted because of leave of absence. | ||
| Mappings |
| ||
| Encounter.reason | |||
| Short | Reason the encounter takes place (code) | ||
| Definition | Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis. | ||
| Cardinality | 0..* | ||
| Type | CodeableConcept | ||
| Binding | Reason why the encounter takes place. | ||
| Summary | True | ||
| Alias | Indication, Admission diagnosis | ||
| Comments | For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis). | ||
| Mappings |
| ||
| Encounter.reason.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Encounter.reason.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Mappings |
| ||
| Encounter.reason.coding | |||
| Short | Code defined by a terminology system | ||
| Definition | A reference to a code defined by a terminology system. | ||
| Cardinality | 0..* | ||
| Type | Coding | ||
| Summary | True | ||
| Requirements | Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. | ||
| Comments | 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. | ||
| Slicing | Unordered, Open, by system(Value) | ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT | |||
| Short | Code defined by a terminology system | ||
| Definition | A reference to a code defined by a terminology system. | ||
| Cardinality | 0..1 | ||
| Type | Coding | ||
| Summary | True | ||
| Requirements | Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. | ||
| Comments | 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. | ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT.extension:snomedCTDescriptionID | |||
| Short | The SNOMED CT Description ID for the display | ||
| Definition | The SNOMED CT Description ID for the display. | ||
| Cardinality | 0..1 | ||
| Type | Extension(Complex) | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT.extension:snomedCTDescriptionID.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT.extension:snomedCTDescriptionID.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionId | |||
| Short | The SNOMED CT Description ID | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 1..1 | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionId.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionId.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionId.url | |||
| Short | identifies the meaning of the extension | ||
| Definition | Source of the definition for the extension code - a logical name or a URL. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Comments | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | descriptionId | ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionId.value[x]:valueId | |||
| Short | The SNOMED CT Description ID | ||
| Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||
| Cardinality | 0..1 | ||
| Type | id | ||
| Comments | A stream of bytes, base64 encoded | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionDisplay | |||
| Short | The SNOMED CT display for the description ID | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 1..1 | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionDisplay.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionDisplay.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionDisplay.url | |||
| Short | identifies the meaning of the extension | ||
| Definition | Source of the definition for the extension code - a logical name or a URL. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Comments | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | descriptionDisplay | ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionDisplay.value[x]:valueString | |||
| Short | The SNOMED CT display for the description ID | ||
| Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Comments | A stream of bytes, base64 encoded | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT.extension:snomedCTDescriptionID.url | |||
| Short | identifies the meaning of the extension | ||
| Definition | Source of the definition for the extension code - a logical name or a URL. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Comments | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | https://fhir.hl7.org.uk/STU3/StructureDefinition/Extension-coding-sctdescid | ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT.extension:snomedCTDescriptionID.value[x] | |||
| Short | Value of extension | ||
| Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||
| Cardinality | 0..0 | ||
| Type | Reference(), base64Binary, boolean, code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, SampledData, Signature, Timing | ||
| Comments | A stream of bytes, base64 encoded | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT.system | |||
| Short | Identity of the terminology system | ||
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Summary | True | ||
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | ||
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. | ||
| Fixed Value | http://snomed.info/sct | ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT.version | |||
| Short | Version of the system - if relevant | ||
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Summary | True | ||
| Comments | 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. | ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT.code | |||
| Short | Symbol in syntax defined by the system | ||
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Summary | True | ||
| Requirements | Need to refer to a particular code in the system. | ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT.display | |||
| Short | Representation defined by the system | ||
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | ||
| Cardinality | 1..1 | ||
| Type | string | ||
| Summary | True | ||
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | ||
| Mappings |
| ||
| Encounter.reason.coding:snomedCT.userSelected | |||
| Short | If this coding was chosen directly by the user | ||
| Definition | Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). | ||
| Cardinality | 0..1 | ||
| Type | boolean | ||
| Summary | True | ||
| Requirements | 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. | ||
| Comments | 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. | ||
| Mappings |
| ||
| Encounter.reason.text | |||
| Short | Plain text representation of the concept | ||
| Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Summary | True | ||
| Requirements | 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. | ||
| Comments | Very often the text is the same as a displayName of one of the codings. | ||
| Mappings |
| ||
| Encounter.diagnosis | |||
| Short | The list of diagnosis relevant to this encounter | ||
| Definition | The list of diagnosis relevant to this encounter. | ||
| Cardinality | 0..* | ||
| Type | BackboneElement | ||
| Summary | True | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.diagnosis.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Encounter.diagnosis.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Mappings |
| ||
| Encounter.diagnosis.modifierExtension | |||
| Short | Extensions that cannot be ignored | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Mappings |
| ||
| Encounter.diagnosis.condition | |||
| Short | Reason the encounter takes place (resource) | ||
| Definition | Reason the encounter takes place, as specified using information from another resource. For admissions, this is the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure. | ||
| Cardinality | 1..1 | ||
| Type | Reference(CareConnect-Procedure-1 | CareConnect-Condition-1) | ||
| Alias | Admission diagnosis, discharge diagnosis, indication | ||
| Comments | For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis). | ||
| Mappings |
| ||
| Encounter.diagnosis.role | |||
| Short | Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …) | ||
| Definition | Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …). | ||
| Cardinality | 0..1 | ||
| Type | CodeableConcept | ||
| Binding | The type of diagnosis this condition represents | ||
| Mappings |
| ||
| Encounter.diagnosis.rank | |||
| Short | Ranking of the diagnosis (for each role type) | ||
| Definition | Ranking of the diagnosis (for each role type). | ||
| Cardinality | 0..1 | ||
| Type | positiveInt | ||
| Mappings |
| ||
| Encounter.account | |||
| Short | The set of accounts that may be used for billing for this Encounter | ||
| Definition | The set of accounts that may be used for billing for this Encounter. | ||
| Cardinality | 0..* | ||
| Type | Reference(Account) | ||
| Comments | The billing system may choose to allocate billable items associated with the Encounter to different referenced Accounts based on internal business rules. | ||
| Mappings |
| ||
| Encounter.hospitalization | |||
| Short | Details about the admission to a healthcare service | ||
| Definition | Details about the admission to a healthcare service. | ||
| Cardinality | 0..1 | ||
| Type | BackboneElement | ||
| Comments | An Encounter may cover more than just the inpatient stay. Contexts such as outpatients, community clinics, and aged care facilities are also included. The duration recorded in the period of this encounter covers the entire scope of this hospitalization record. | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.hospitalization.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Encounter.hospitalization.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) | ||
| Mappings |
| ||
| Encounter.hospitalization.extension:admissionMethod | |||
| Short | An extension to the Encounter resource to record how a Patient was admitted to hospital. | ||
| Definition | Optional Extension Element - found in all resources. | ||
| Cardinality | 0..1 | ||
| Type | Extension(CodeableConcept) | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.hospitalization.extension:admissionMethod.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.hospitalization.extension:admissionMethod.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.hospitalization.extension:admissionMethod.url | |||
| Short | identifies the meaning of the extension | ||
| Definition | Source of the definition for the extension code - a logical name or a URL. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Comments | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | https://fhir.hl7.org.uk/STU3/StructureDefinition/Extension-CareConnect-AdmissionMethod-1 | ||
| Mappings |
| ||
| Encounter.hospitalization.extension:admissionMethod.value[x]:valueCodeableConcept | |||
| Short | The method of admission to a Hospital Provider Spell. | ||
| Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||
| Cardinality | 1..1 | ||
| Type | CodeableConcept | ||
| Binding | The method of admission to a Hospital Provider Spell. | ||
| Comments | A stream of bytes, base64 encoded | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.hospitalization.extension:dischargeMethod | |||
| Short | An extension to the Encounter resource to record the method of discharge from hospital. | ||
| Definition | Optional Extension Element - found in all resources. | ||
| Cardinality | 0..1 | ||
| Type | Extension(CodeableConcept) | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.hospitalization.extension:dischargeMethod.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.hospitalization.extension:dischargeMethod.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.hospitalization.extension:dischargeMethod.url | |||
| Short | identifies the meaning of the extension | ||
| Definition | Source of the definition for the extension code - a logical name or a URL. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Comments | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | https://fhir.hl7.org.uk/STU3/StructureDefinition/Extension-CareConnect-DischargeMethod-1 | ||
| Mappings |
| ||
| Encounter.hospitalization.extension:dischargeMethod.value[x]:valueCodeableConcept | |||
| Short | The method of discharge from a Hospital Provider Spell. | ||
| Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||
| Cardinality | 1..1 | ||
| Type | CodeableConcept | ||
| Binding | The method of discharge from a Hospital Provider Spell. | ||
| Comments | A stream of bytes, base64 encoded | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.hospitalization.modifierExtension | |||
| Short | Extensions that cannot be ignored | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Mappings |
| ||
| Encounter.hospitalization.preAdmissionIdentifier | |||
| Short | Pre-admission identifier | ||
| Definition | Pre-admission identifier. | ||
| Cardinality | 0..1 | ||
| Type | Identifier | ||
| Mappings |
| ||
| Encounter.hospitalization.preAdmissionIdentifier.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Encounter.hospitalization.preAdmissionIdentifier.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Mappings |
| ||
| Encounter.hospitalization.preAdmissionIdentifier.use | |||
| Short | usual | official | temp | secondary (If known) | ||
| Definition | The purpose of this identifier. | ||
| Cardinality | 0..1 | ||
| Type | code | ||
| Binding | Identifies the purpose for this identifier, if known . | ||
| Modifier | True | ||
| Summary | True | ||
| Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. | ||
| Comments | This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. | ||
| Mappings |
| ||
| Encounter.hospitalization.preAdmissionIdentifier.type | |||
| Short | Description of identifier | ||
| Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. | ||
| Cardinality | 0..1 | ||
| Type | CodeableConcept | ||
| Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. | ||
| Summary | True | ||
| Requirements | Allows users to make use of identifiers when the identifier system is not known. | ||
| Comments | 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. | ||
| Mappings |
| ||
| Encounter.hospitalization.preAdmissionIdentifier.system | |||
| Short | The namespace for the identifier value | ||
| Definition | Establishes the namespace for the value - that is, a URL that describes a set values that are unique. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Summary | True | ||
| Requirements | 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. | ||
| Examples | Generalhttp://www.acme.com/identifiers/patient | ||
| Mappings |
| ||
| Encounter.hospitalization.preAdmissionIdentifier.value | |||
| Short | The value that is unique | ||
| Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. | ||
| Cardinality | 1..1 | ||
| Type | string | ||
| Summary | True | ||
| Comments | If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. | ||
| Examples | General123456 | ||
| Mappings |
| ||
| Encounter.hospitalization.preAdmissionIdentifier.period | |||
| Short | Time period when id is/was valid for use | ||
| Definition | Time period during which identifier is/was valid for use. | ||
| Cardinality | 0..1 | ||
| Type | Period | ||
| Summary | True | ||
| Mappings |
| ||
| Encounter.hospitalization.preAdmissionIdentifier.assigner | |||
| Short | Organization that issued id (may be just text) | ||
| Definition | Organization that issued/manages the identifier. | ||
| Cardinality | 0..1 | ||
| Type | Reference(CareConnect-Organization-1) | ||
| Summary | True | ||
| Comments | 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. | ||
| Mappings |
| ||
| Encounter.hospitalization.origin | |||
| Short | The location from which the patient came before admission | ||
| Definition | The location from which the patient came before admission. | ||
| Cardinality | 0..1 | ||
| Type | Reference(CareConnect-Location-1) | ||
| Mappings |
| ||
| Encounter.hospitalization.admitSource | |||
| Short | From where patient was admitted (physician referral, transfer) | ||
| Definition | From where patient was admitted (physician referral, transfer). | ||
| Cardinality | 0..1 | ||
| Type | CodeableConcept | ||
| Binding | The source of admission to a Hospital Provider Spell or a Nursing Episode when the Patient is in a Hospital Site or a Care Home. NHS Data Model and Dictionary Source Of Admission (preferred) | ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission | |||
| Short | The type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission | ||
| Definition | Whether this hospitalization is a readmission and why if known. | ||
| Cardinality | 0..1 | ||
| Type | CodeableConcept | ||
| Binding | The reason for re-admission of this hospitalization encounter. | ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding | |||
| Short | Code defined by a terminology system | ||
| Definition | A reference to a code defined by a terminology system. | ||
| Cardinality | 0..* | ||
| Type | Coding | ||
| Summary | True | ||
| Requirements | Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. | ||
| Comments | 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. | ||
| Slicing | Unordered, Open, by system(Value) | ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT | |||
| Short | Code defined by a terminology system | ||
| Definition | A reference to a code defined by a terminology system. | ||
| Cardinality | 0..1 | ||
| Type | Coding | ||
| Summary | True | ||
| Requirements | Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. | ||
| Comments | 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. | ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT.extension:snomedCTDescriptionID | |||
| Short | The SNOMED CT Description ID for the display | ||
| Definition | The SNOMED CT Description ID for the display. | ||
| Cardinality | 0..1 | ||
| Type | Extension(Complex) | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT.extension:snomedCTDescriptionID.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT.extension:snomedCTDescriptionID.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionId | |||
| Short | The SNOMED CT Description ID | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 1..1 | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionId.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionId.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionId.url | |||
| Short | identifies the meaning of the extension | ||
| Definition | Source of the definition for the extension code - a logical name or a URL. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Comments | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | descriptionId | ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionId.value[x]:valueId | |||
| Short | The SNOMED CT Description ID | ||
| Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||
| Cardinality | 0..1 | ||
| Type | id | ||
| Comments | A stream of bytes, base64 encoded | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionDisplay | |||
| Short | The SNOMED CT display for the description ID | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 1..1 | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionDisplay.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Comments | Note that FHIR strings may not exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionDisplay.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionDisplay.url | |||
| Short | identifies the meaning of the extension | ||
| Definition | Source of the definition for the extension code - a logical name or a URL. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Comments | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | descriptionDisplay | ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT.extension:snomedCTDescriptionID.extension:descriptionDisplay.value[x]:valueString | |||
| Short | The SNOMED CT display for the description ID | ||
| Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Comments | A stream of bytes, base64 encoded | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT.extension:snomedCTDescriptionID.url | |||
| Short | identifies the meaning of the extension | ||
| Definition | Source of the definition for the extension code - a logical name or a URL. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Comments | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | https://fhir.hl7.org.uk/STU3/StructureDefinition/Extension-coding-sctdescid | ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT.extension:snomedCTDescriptionID.value[x] | |||
| Short | Value of extension | ||
| Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). | ||
| Cardinality | 0..0 | ||
| Type | Reference(), base64Binary, boolean, code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, SampledData, Signature, Timing | ||
| Comments | A stream of bytes, base64 encoded | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT.system | |||
| Short | Identity of the terminology system | ||
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Summary | True | ||
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | ||
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. | ||
| Fixed Value | http://snomed.info/sct | ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT.version | |||
| Short | Version of the system - if relevant | ||
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Summary | True | ||
| Comments | 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. | ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT.code | |||
| Short | Symbol in syntax defined by the system | ||
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Summary | True | ||
| Requirements | Need to refer to a particular code in the system. | ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT.display | |||
| Short | Representation defined by the system | ||
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | ||
| Cardinality | 1..1 | ||
| Type | string | ||
| Summary | True | ||
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.coding:snomedCT.userSelected | |||
| Short | If this coding was chosen directly by the user | ||
| Definition | Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). | ||
| Cardinality | 0..1 | ||
| Type | boolean | ||
| Summary | True | ||
| Requirements | 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. | ||
| Comments | 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. | ||
| Mappings |
| ||
| Encounter.hospitalization.reAdmission.text | |||
| Short | Plain text representation of the concept | ||
| Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Summary | True | ||
| Requirements | 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. | ||
| Comments | Very often the text is the same as a displayName of one of the codings. | ||
| Mappings |
| ||
| Encounter.hospitalization.dietPreference | |||
| Short | Diet preferences reported by the patient | ||
| Definition | Diet preferences reported by the patient. | ||
| Cardinality | 0..* | ||
| Type | CodeableConcept | ||
| Binding | Medical, cultural or ethical food preferences to help with catering requirements. | ||
| Requirements | Used to track patient's diet restrictions and/or preference. For a complete description of the nutrition needs of a patient during their stay, one should use the nutritionOrder resource which links to Encounter. | ||
| Comments | For example a patient may request both a dairy-free and nut-free diet preference (not mutually exclusive). | ||
| Mappings |
| ||
| Encounter.hospitalization.specialCourtesy | |||
| Short | Special courtesies (VIP, board member) | ||
| Definition | Special courtesies (VIP, board member). | ||
| Cardinality | 0..* | ||
| Type | CodeableConcept | ||
| Binding | Special courtesies | ||
| Mappings |
| ||
| Encounter.hospitalization.specialArrangement | |||
| Short | Wheelchair, translator, stretcher, etc. | ||
| Definition | Any special requests that have been made for this hospitalization encounter, such as the provision of specific equipment or other things. | ||
| Cardinality | 0..* | ||
| Type | CodeableConcept | ||
| Binding | Special arrangements | ||
| Mappings |
| ||
| Encounter.hospitalization.destination | |||
| Short | Location to which the patient is discharged | ||
| Definition | Location to which the patient is discharged. | ||
| Cardinality | 0..1 | ||
| Type | Reference(CareConnect-Location-1) | ||
| Mappings |
| ||
| Encounter.hospitalization.dischargeDisposition | |||
| Short | Category or kind of location after discharge | ||
| Definition | Category or kind of location after discharge. | ||
| Cardinality | 0..1 | ||
| Type | CodeableConcept | ||
| Binding | The destination of a Patient on completion of a Hospital Provider Spell, or a note that the Patient died or was a still birth. NHS Data Model and Dictionary Discharge Destination (example) | ||
| Mappings |
| ||
| Encounter.location | |||
| Short | List of locations where the patient has been | ||
| Definition | List of locations where the patient has been during this encounter. | ||
| Cardinality | 0..* | ||
| Type | BackboneElement | ||
| Comments | Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual". | ||
| Constraints |
| ||
| Mappings |
| ||
| Encounter.location.id | |||
| Short | xml:id (or equivalent in JSON) | ||
| Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Encounter.location.extension | |||
| Short | Additional Content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user content | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Mappings |
| ||
| Encounter.location.modifierExtension | |||
| Short | Extensions that cannot be ignored | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||
| Mappings |
| ||
| Encounter.location.location | |||
| Short | Location the encounter takes place | ||
| Definition | The location where the encounter takes place. | ||
| Cardinality | 1..1 | ||
| Type | Reference(CareConnect-Location-1) | ||
| Mappings |
| ||
| Encounter.location.status | |||
| Short | planned | active | reserved | completed | ||
| Definition | The status of the participants' presence at the specified location during the period specified. If the participant is is no longer at the location, then the period will have an end date/time. | ||
| Cardinality | 0..1 | ||
| Type | code | ||
| Binding | The status of the location. | ||
| Comments | When the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed. | ||
| Mappings |
| ||
| Encounter.location.period | |||
| Short | Time period during which the patient was present at the location | ||
| Definition | Time period during which the patient was present at the location. | ||
| Cardinality | 0..1 | ||
| Type | Period | ||
| Mappings |
| ||
| Encounter.serviceProvider | |||
| Short | The custodian organization of this Encounter record | ||
| Definition | An organization that is in charge of maintaining the information of this Encounter (e.g. who maintains the report or the master service catalog item, etc.). This MAY be the same as the organization on the Patient record, however it could be different. This MAY not be not the Service Delivery Location's Organization. | ||
| Cardinality | 0..1 | ||
| Type | Reference(CareConnect-GPC-Organization-1) | ||
| Must Support | True | ||
| Mappings |
| ||
| Encounter.partOf | |||
| Short | Another Encounter this encounter is part of | ||
| Definition | Another Encounter of which this encounter is a part of (administratively or in time). | ||
| Cardinality | 0..1 | ||
| Type | Reference(CareConnect-Encounter-1) | ||
| Comments | This is also used for associating a child's encounter back to the mother's encounter. Refer to the Notes section in the Patient resource for further details. | ||
| Mappings |
| ||
Related links
See CareConnect-GPC-AllergyIntolerance-1 for details on how to populate the profile.