Velferdsteknologisk knutepunkt

vkp-digital-Encounter profile

The full profile documentation is published here: vkp-digital-Encounter-v06

Examples

Example	Information
Encounter - Event / Hendelse	Example of an event, reported as an encounter
Encounter - Digitalt tilsyn ett apparat	Example of digital encounter (digitalt tilsyn) with one device
Encounter - Digitalt tilsyn to apparater	Example of digital encounter (digitalt tilsyn) with two devices

Overview

vkp-digital-Encounter-v06 (Encounter)	I		Encounter	Element id Encounter Short description An digital/virtual interaction during which services are provided to the patient Alternate names Visit, digitalt tilsyn Definition The digital (virtual) Encounter is caracterized as an encounter that uses some technological mean to perform the encounter instead of a face-to-face meeting. 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. Comments The use-case in question is performing a virtual encounter using a camera device to perform the encounter. Data type Encounter Constraints dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources `contained.contained.empty()` dom-1: If the resource is contained in another resource, it SHALL NOT contain any narrative `contained.text.empty()` dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated `contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()` dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource `contained.where(('#'+id in %resource.descendants().reference).not()).empty()` Mappings rim: Entity. Role, or Act rim: Encounter[@moodCode='EVN'] w5: workflow.encounter
id	Σ	0..1	id	There are no (further) constraints on this element Element id Encounter.id Short description 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. 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. Data type id
meta	Σ	0..1	Meta	There are no (further) constraints on this element Element id Encounter.meta Short description 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. Data type Meta
implicitRules	Σ ?!	0..1	uri	There are no (further) constraints on this element Element id Encounter.implicitRules Short description 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. 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. Data type uri
language		0..1	codeBinding	There are no (further) constraints on this element Element id Encounter.language Short description Language of the resource content Definition The base language in which the resource is written. 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). Data type code Binding A human language. Common Languages (extensible)
text	I	0..1	Narrative	There are no (further) constraints on this element Element id Encounter.text Short description Text summary of the resource, for human interpretation Alternate names narrative, html, xhtml, display 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. 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. Data type Narrative Mappings rim: Act.text?
contained		0..*	Resource	There are no (further) constraints on this element Element id Encounter.contained Short description Contained, inline Resources Alternate names inline resources, anonymous resources, contained 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. 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. Data type Resource Mappings rim: N/A
extension		0..*	Extension	Element id Encounter.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Mappings rim: N/A
note	I	0..1	Extension(Annotation)	Element id Encounter.extension:note Short description A journal note Alternate names extensions, user content Definition A journal note to document the digital encounter. Can be XHTML formatted text. In the VKP project in Norway the note is used for: Response summary: A text describing the resolution of the digital-Encounter event Example: `{ "url":"http://ehelse.no/fhir/StructureDefinition/vkp-annotation-v06", "extension": [ { "url":"note", "valueAnnotation":{ "authorReference":{ "identifier":{ "system":"urn:oid:2.16.578.1.12.4.1.4.1", "value":"04056600324" }, "display":"Magnar Koman" }, "time":"2018-06-25T08:00:00.936Z", "text":"Selve teksten til journalnotatet." } } ] }` 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. Data type Extension(Annotation) Extension URL http://ehelse.no/fhir/StructureDefinition/vkp-annotation-v06 Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: N/A rim: n/a
signature	I	0..1	Extension(Annotation)	Element id Encounter.extension:signature Short description Signature for the journal note Alternate names extensions, user content Definition When a journal note is to document the digital encounter in the EHR it needs a string identifying who registered the note. A signature of who registered the information should be present in all events, even when there is no text in the journal note. Can be XHTML formatted text. In the VKP project in Norway the signature is used for: Signature: Name of author plus a system specific signature identifying the user who submitted the Composition (user name in the system). Example: `{ "url":"http://ehelse.no/fhir/StructureDefinition/vkp-annotation-v06", "extension": [ { "url":"signature", "valueAnnotation":{ "time":"2018-06-25T08:00:00.936Z", "text":"Magnar Koman (signatur)" } } ] }` 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. Data type Extension(Annotation) Extension URL http://ehelse.no/fhir/StructureDefinition/vkp-annotation-v06 Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: N/A rim: n/a
device	I	1..*	Extension(Complex)	Element id Encounter.extension:device Short description logical reference to the device Alternate names extensions, user content Definition The device used in the patient encounter. For example, a particular camera device VKP-norway: Should be a logical reference containing the IMEI/serial number of the device. display value should contain the name of the device type. Could also contain a display name of the device 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. Data type Extension(Complex) Extension URL http://ehelse.no/fhir/StructureDefinition/vkp-encounterDevice-v06 Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: N/A rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id Encounter.extension:device.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	Element id Encounter.extension:device.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
deviceIdentifier		0..1	Extension	There are no (further) constraints on this element Element id Encounter.extension:device.extension:deviceIdentifier Short description logical reference to the device Alternate names extensions, user content Definition The device used in the patient encounter. For example, a particular camera device VKP-norway: Should be a logical reference containing the IMEI/serial number of the device. display value should contain the name of the device type. 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. Data type Extension Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id Encounter.extension:device.extension:deviceIdentifier.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.extension:device.extension:deviceIdentifier.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
url		1..1	uriFixed Value	There are no (further) constraints on this element Element id Encounter.extension:device.extension:deviceIdentifier.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. 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. Data type uri Fixed value deviceIdentifier Mappings rim: N/A
valueIdentifier		0..1	Identifier	There are no (further) constraints on this element Element id Encounter.extension:device.extension:deviceIdentifier.value[x]:valueIdentifier Short description Logical reference to the device Definition Logical reference to the device. VKP-norway: Should be a logical reference containing the IMEI/serial number of the device. display value should contain the name of the device type. VKP uses serial numbers decided by the manufacturer of the device Data type Identifier Mappings rim: N/A
id		0..1	string	There are no (further) constraints on this element Element id Encounter.extension:device.extension:deviceIdentifier.value[x]:valueIdentifier.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.extension:device.extension:deviceIdentifier.value[x]:valueIdentifier.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
use	Σ ?!	0..1	codeBinding	There are no (further) constraints on this element Element id Encounter.extension:device.extension:deviceIdentifier.value[x]:valueIdentifier.use Short description usual \| official \| temp \| secondary (If known) Definition The purpose of this identifier. 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. Data type code Binding Identifies the purpose for this identifier, if known . IdentifierUse (required) Mappings v2: N/A rim: Role.code or implied by context
type	Σ	0..1	CodeableConceptBinding	There are no (further) constraints on this element Element id Encounter.extension:device.extension:deviceIdentifier.value[x]:valueIdentifier.type Short description Description of identifier Definition A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. 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. Data type CodeableConcept Binding A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Mappings v2: CX.5 rim: Role.code or implied by context
system	Σ	1..1	uri	There are no (further) constraints on this element Element id Encounter.extension:device.extension:deviceIdentifier.value[x]:valueIdentifier.system Short description 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. 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. Data type uri Examples General http://www.acme.com/identifiers/patient Mappings v2: CX.4 / EI-2-4 rim: II.root or Role.id.root servd: ./IdentifierType
value	Σ	1..1	string	There are no (further) constraints on this element Element id Encounter.extension:device.extension:deviceIdentifier.value[x]:valueIdentifier.value Short description 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. 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. Data type string Examples General 123456 Mappings v2: CX.1 / EI.1 rim: II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root) servd: ./Value
period	Σ	0..1	Period	There are no (further) constraints on this element Element id Encounter.extension:device.extension:deviceIdentifier.value[x]:valueIdentifier.period Short description Time period when id is/was valid for use Definition Time period during which identifier is/was valid for use. Data type Period Mappings v2: CX.7 + CX.8 rim: Role.effectiveTime or implied by context servd: ./StartDate and ./EndDate
assigner	Σ	0..1	Reference(Organization)	There are no (further) constraints on this element Element id Encounter.extension:device.extension:deviceIdentifier.value[x]:valueIdentifier.assigner Short description Organization that issued id (may be just text) Definition Organization that issued/manages the identifier. 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. Data type Reference(Organization) Mappings v2: CX.4 / (CX.4,CX.9,CX.10) rim: II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper servd: ./IdentifierIssuingAuthority
display		0..1	Extension	There are no (further) constraints on this element Element id Encounter.extension:device.extension:display Short description displayname of the device Alternate names extensions, user content Definition Plain text narrative that identifies the device 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. Data type Extension Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id Encounter.extension:device.extension:display.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.extension:device.extension:display.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
url		1..1	uriFixed Value	There are no (further) constraints on this element Element id Encounter.extension:device.extension:display.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. 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. Data type uri Fixed value display Mappings rim: N/A
valueString		0..1	string	There are no (further) constraints on this element Element id Encounter.extension:device.extension:display.value[x]:valueString Short description displayname of the device Definition Plain text narrative that identifies the device Data type string Mappings rim: N/A
type		0..1	Extension	There are no (further) constraints on this element Element id Encounter.extension:device.extension:type Short description Generic type of the device Alternate names extensions, user content Definition Generic type of the device, e.g. Trykknapp, Snortrekk, Roommate. 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. Data type Extension Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id Encounter.extension:device.extension:type.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.extension:device.extension:type.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
url		1..1	uriFixed Value	There are no (further) constraints on this element Element id Encounter.extension:device.extension:type.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. 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. Data type uri Fixed value type Mappings rim: N/A
valueString		0..1	string	There are no (further) constraints on this element Element id Encounter.extension:device.extension:type.value[x]:valueString Short description 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). Data type string Mappings rim: N/A
typeName		0..1	Extension	There are no (further) constraints on this element Element id Encounter.extension:device.extension:typeName Short description Specific type of the device Alternate names extensions, user content Definition Specific typename/model, specified by the client 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. Data type Extension Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id Encounter.extension:device.extension:typeName.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.extension:device.extension:typeName.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
url		1..1	uriFixed Value	There are no (further) constraints on this element Element id Encounter.extension:device.extension:typeName.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. 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. Data type uri Fixed value typeName Mappings rim: N/A
valueString		0..1	string	There are no (further) constraints on this element Element id Encounter.extension:device.extension:typeName.value[x]:valueString Short description 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). Data type string Mappings rim: N/A
url		1..1	uriFixed Value	There are no (further) constraints on this element Element id Encounter.extension:device.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. 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. Data type uri Fixed value http://ehelse.no/fhir/StructureDefinition/vkp-encounterDevice-v06 Mappings rim: N/A
value[x]		0..0		There are no (further) constraints on this element Element id Encounter.extension:device.value[x] Short description 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). Mappings rim: N/A
modifierExtension	?!	0..*	Extension	There are no (further) constraints on this element Element id Encounter.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content 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. 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. Data type Extension Mappings rim: N/A
identifier	S Σ	0..*	Identifier	Element id Encounter.identifier Short description Identifier(s) by which this encounter is known Definition Unique code or number identifying the Encounter VKP project uses UUID. Example: `"identifier": [ { "system":"urn:ietf:rfc:3986", "value":"urn:uuid:a76d9bbf-f293-4fb7-ad4c-2851cac77162" } ]` Data type Identifier Mappings v2: PV1-19 rim: .id w5: id
id		0..1	string	There are no (further) constraints on this element Element id Encounter.identifier.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.identifier.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
use	Σ ?!	0..1	codeBinding	There are no (further) constraints on this element Element id Encounter.identifier.use Short description usual \| official \| temp \| secondary (If known) Definition The purpose of this identifier. 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. Data type code Binding Identifies the purpose for this identifier, if known . IdentifierUse (required) Mappings v2: N/A rim: Role.code or implied by context
type	Σ	0..1	CodeableConceptBinding	There are no (further) constraints on this element Element id Encounter.identifier.type Short description Description of identifier Definition A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. 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. Data type CodeableConcept Binding A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Mappings v2: CX.5 rim: Role.code or implied by context
system	Σ	0..1	uriFixed Value	Element id Encounter.identifier.system Short description 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. 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. Data type uri Fixed value urn:ietf:rfc:3986 Mappings v2: CX.4 / EI-2-4 rim: II.root or Role.id.root servd: ./IdentifierType
value	Σ	0..1	string	Element id Encounter.identifier.value Short description The value that is unique Definition The actual uniqe identifier (UUID) The portion of the identifier typically relevant to the user and which is unique within the context of the system. 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. Data type string Examples General 123456 Mappings v2: CX.1 / EI.1 rim: II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root) servd: ./Value
period	Σ	0..1	Period	There are no (further) constraints on this element Element id Encounter.identifier.period Short description Time period when id is/was valid for use Definition Time period during which identifier is/was valid for use. Data type Period Mappings v2: CX.7 + CX.8 rim: Role.effectiveTime or implied by context servd: ./StartDate and ./EndDate
assigner	Σ	0..1	Reference(Organization)	There are no (further) constraints on this element Element id Encounter.identifier.assigner Short description Organization that issued id (may be just text) Definition Organization that issued/manages the identifier. 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. Data type Reference(Organization) Mappings v2: CX.4 / (CX.4,CX.9,CX.10) rim: II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper servd: ./IdentifierIssuingAuthority
status	Σ ?!	1..1	codeBinding	There are no (further) constraints on this element Element id Encounter.status Short description planned \| arrived \| triaged \| in-progress \| onleave \| finished \| cancelled + Definition planned \| arrived \| triaged \| in-progress \| onleave \| finished \| cancelled +. 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. Data type code Binding Current state of the encounter EncounterStatus (required) Mappings v2: No clear equivalent in HL7 v2; active/finished could be inferred from PV1-44, PV1-45, PV2-24; inactive could be inferred from PV2-16 rim: .statusCode w5: status
statusHistory		0..*	BackboneElement	There are no (further) constraints on this element Element id Encounter.statusHistory Short description 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. Comments The current status is always found in the current version of the resource, not the status history. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id Encounter.statusHistory.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.statusHistory.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Mappings rim: n/a
modifierExtension	Σ ?!	0..*	Extension	There are no (further) constraints on this element Element id Encounter.statusHistory.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content, modifiers 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. 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. Data type Extension Mappings rim: N/A
status		1..1	codeBinding	There are no (further) constraints on this element Element id Encounter.statusHistory.status Short description planned \| arrived \| triaged \| in-progress \| onleave \| finished \| cancelled + Definition planned \| arrived \| triaged \| in-progress \| onleave \| finished \| cancelled +. Data type code Binding Current state of the encounter EncounterStatus (required) Mappings rim: n/a
period		1..1	Period	There are no (further) constraints on this element Element id Encounter.statusHistory.period Short description The time that the episode was in the specified status Definition The time that the episode was in the specified status. Data type Period Mappings rim: n/a
class	Σ	0..1	CodingBinding	Element id Encounter.class Short description Encounter class for digital Encounter Definition VKP uses a valueset for encounter class for digital Encounter http://ehelse.no/fhir/ValueSet/vkp-encounter-class-v06 Data type Coding Binding Classification of the encounter vkp-encounter-class-v06.valueset (extensible) Mappings v2: PV1-2 rim: .inboundRelationship[typeCode=SUBJ].source[classCode=LIST].code w5: class
id		0..1	string	There are no (further) constraints on this element Element id Encounter.class.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.class.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
system	Σ	0..1	uriFixed Value	Element id Encounter.class.system Short description Identity of the terminology system Definition VKP uses http://ehelse.no/fhir/CodeSystem/vkp-encounter-class-v06 The identification of the code system that defines the meaning of the symbol in the code. 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. Data type uri Fixed value http://ehelse.no/fhir/CodeSystem/vkp-encounter-class-v06 Mappings v2: CE.3 rim:* ./codeSystem orim: fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
version	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.class.version Short description 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. 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. Data type string Mappings v2: CE.7 rim:* ./codeSystemVersion orim: fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
code	Σ	0..1	code	There are no (further) constraints on this element Element id Encounter.class.code Short description 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). Requirements Need to refer to a particular code in the system. Data type code Mappings v2: CE.1 rim:* ./code orim: fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
display	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.class.display Short description Representation defined by the system Definition A representation of the meaning of the code in the system, following the rules of the system. Requirements Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Data type string Mappings v2: CE.2 - but note this is not well followed rim:* CV.displayName orim: fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
userSelected	Σ	0..1	boolean	There are no (further) constraints on this element Element id Encounter.class.userSelected Short description 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). 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. Data type boolean Mappings v2: Sometimes implied by being first rim: CD.codingRationale orim: fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
classHistory	S	0..*	BackboneElement	There are no (further) constraints on this element Element id Encounter.classHistory Short description 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. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id Encounter.classHistory.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	Element id Encounter.classHistory.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Mappings rim: n/a
device	I	0..1	Extension(Complex)	Element id Encounter.classHistory.extension:device Short description logical reference to the device Alternate names extensions, user content Definition Devices used during the patient encounter. For example, a particular camera device. VKP-norway: Should contain a displaynames of the devices 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. Data type Extension(Complex) Extension URL http://ehelse.no/fhir/StructureDefinition/vkp-encounterDevice-v06 Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
id		0..1	string	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	Element id Encounter.classHistory.extension:device.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
deviceIdentifier		0..*	Extension	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:deviceIdentifier Short description logical reference to the device Alternate names extensions, user content Definition The device used in the patient encounter. For example, a particular camera device VKP-norway: Should be a logical reference containing the IMEI/serial number of the device. display value should contain the name of the device type. 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. Data type Extension Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:deviceIdentifier.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:deviceIdentifier.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
url		1..1	uriFixed Value	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:deviceIdentifier.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. 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. Data type uri Fixed value deviceIdentifier Mappings rim: N/A
valueIdentifier		0..1	Identifier	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:deviceIdentifier.value[x]:valueIdentifier Short description Logical reference to the device Definition Logical reference to the device. VKP-norway: Should be a logical reference containing the IMEI/serial number of the device. display value should contain the name of the device type. VKP uses serial numbers decided by the manufacturer of the device Data type Identifier Mappings rim: N/A
id		0..1	string	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:deviceIdentifier.value[x]:valueIdentifier.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:deviceIdentifier.value[x]:valueIdentifier.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
use	Σ ?!	0..1	codeBinding	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:deviceIdentifier.value[x]:valueIdentifier.use Short description usual \| official \| temp \| secondary (If known) Definition The purpose of this identifier. 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. Data type code Binding Identifies the purpose for this identifier, if known . IdentifierUse (required) Mappings v2: N/A rim: Role.code or implied by context
type	Σ	0..1	CodeableConceptBinding	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:deviceIdentifier.value[x]:valueIdentifier.type Short description Description of identifier Definition A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. 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. Data type CodeableConcept Binding A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Mappings v2: CX.5 rim: Role.code or implied by context
system	Σ	1..1	uri	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:deviceIdentifier.value[x]:valueIdentifier.system Short description 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. 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. Data type uri Examples General http://www.acme.com/identifiers/patient Mappings v2: CX.4 / EI-2-4 rim: II.root or Role.id.root servd: ./IdentifierType
value	Σ	1..1	string	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:deviceIdentifier.value[x]:valueIdentifier.value Short description 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. 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. Data type string Examples General 123456 Mappings v2: CX.1 / EI.1 rim: II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root) servd: ./Value
period	Σ	0..1	Period	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:deviceIdentifier.value[x]:valueIdentifier.period Short description Time period when id is/was valid for use Definition Time period during which identifier is/was valid for use. Data type Period Mappings v2: CX.7 + CX.8 rim: Role.effectiveTime or implied by context servd: ./StartDate and ./EndDate
assigner	Σ	0..1	Reference(Organization)	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:deviceIdentifier.value[x]:valueIdentifier.assigner Short description Organization that issued id (may be just text) Definition Organization that issued/manages the identifier. 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. Data type Reference(Organization) Mappings v2: CX.4 / (CX.4,CX.9,CX.10) rim: II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper servd: ./IdentifierIssuingAuthority
display		0..1	Extension	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:display Short description displayname of the device Alternate names extensions, user content Definition Plain text narrative that identifies the device 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. Data type Extension Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:display.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:display.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
url		1..1	uriFixed Value	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:display.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. 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. Data type uri Fixed value display Mappings rim: N/A
valueString		0..1	string	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:display.value[x]:valueString Short description displayname of the device Definition Plain text narrative that identifies the device Data type string Mappings rim: N/A
type		0..1	Extension	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:type Short description Generic type of the device Alternate names extensions, user content Definition Generic type of the device, e.g. Trykknapp, Snortrekk, Roommate. 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. Data type Extension Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:type.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:type.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
url		1..1	uriFixed Value	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:type.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. 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. Data type uri Fixed value type Mappings rim: N/A
valueString		0..1	string	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:type.value[x]:valueString Short description 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). Data type string Mappings rim: N/A
typeName		0..1	Extension	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:typeName Short description Specific type of the device Alternate names extensions, user content Definition Specific typename/model, specified by the client 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. Data type Extension Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:typeName.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:typeName.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
url		1..1	uriFixed Value	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:typeName.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. 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. Data type uri Fixed value typeName Mappings rim: N/A
valueString		0..1	string	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.extension:typeName.value[x]:valueString Short description 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). Data type string Mappings rim: N/A
url		1..1	uriFixed Value	There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. 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. Data type uri Fixed value http://ehelse.no/fhir/StructureDefinition/vkp-encounterDevice-v06 Mappings rim: N/A
value[x]		0..0		There are no (further) constraints on this element Element id Encounter.classHistory.extension:device.value[x] Short description 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). Mappings rim: N/A
modifierExtension	Σ ?!	0..*	Extension	There are no (further) constraints on this element Element id Encounter.classHistory.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content, modifiers 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. 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. Data type Extension Mappings rim: N/A
class	S	1..1	CodingBinding	Element id Encounter.classHistory.class Short description Encounter class for digital Encounter Definition VKP uses a valueset for encounter class for digital Encounter http://ehelse.no/fhir/ValueSet/vkp-encounter-class-v06 Data type Coding Binding Classification of the encounter vkp-encounter-class-v06.valueset (extensible) Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id Encounter.classHistory.class.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.classHistory.class.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
system	S Σ	0..1	uriFixed Value	Element id Encounter.classHistory.class.system Short description Identity of the terminology system Definition The identification of the code system that defines the meaning of the symbol in the code. 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. Data type uri Fixed value http://ehelse.no/fhir/CodeSystem/vkp-encounter-class-v06 Mappings v2: CE.3 rim:* ./codeSystem orim: fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
version	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.classHistory.class.version Short description 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. 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. Data type string Mappings v2: CE.7 rim:* ./codeSystemVersion orim: fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
code	S Σ	0..1	code	There are no (further) constraints on this element Element id Encounter.classHistory.class.code Short description 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). Requirements Need to refer to a particular code in the system. Data type code Mappings v2: CE.1 rim:* ./code orim: fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
display	Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.classHistory.class.display Short description Representation defined by the system Definition A representation of the meaning of the code in the system, following the rules of the system. Requirements Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Data type string Mappings v2: CE.2 - but note this is not well followed rim:* CV.displayName orim: fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
userSelected	Σ	0..1	boolean	There are no (further) constraints on this element Element id Encounter.classHistory.class.userSelected Short description 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). 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. Data type boolean Mappings v2: Sometimes implied by being first rim: CD.codingRationale orim: fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
period	S	1..1	Period	Element id Encounter.classHistory.period Short description The time that the episode was in the specified class Definition Time period for the digital encounter, the system should provide both start and end times. If the start-time is not known a single end time can be provided as a timestamp for the Encounter. Example code: `"period":{ "start":"2018-06-25T09:56:23.945+02:00", "end":"2018-06-25T10:01:03.936+02:00" }` Data type Period Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id Encounter.classHistory.period.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.classHistory.period.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
start	S Σ I	0..1	dateTime	There are no (further) constraints on this element Element id Encounter.classHistory.period.start Short description Starting time with inclusive boundary Definition The start of the period. The boundary is inclusive. Comments If the low element is missing, the meaning is that the low boundary is not known. Data type dateTime Mappings v2: DR.1 rim: ./low
end	S Σ I	0..1	dateTime	There are no (further) constraints on this element Element id Encounter.classHistory.period.end Short description 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. 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 Data type dateTime Mappings v2: DR.2 rim: ./high
type	S Σ	1..1	CodeableConceptBinding	Element id Encounter.type Short description Event type Definition Encounter type tilsyn\|hendelse Comments Since there are many ways to further classify encounters, this element is 0... Data type* CodeableConcept Binding The type of encounter vkp-encounter-type-v05.valueset (required) Mappings v2: PV1-4 / PV1-18 rim: .code w5: class
priority		0..1	CodeableConcept	There are no (further) constraints on this element Element id Encounter.priority Short description Indicates the urgency of the encounter Definition Indicates the urgency of the encounter. Data type CodeableConcept Binding Indicates the urgency of the encounter. v3 Code System ActPriority (example) Mappings v2: PV2-25 rim: .priorityCode w5: grade
subject	S Σ	0..1	Reference(Patient \| Group \| no-basis-Patient \| vkp-Patient-v06)	Element id Encounter.subject Short description The patient or group present at the encounter Alternate names patient Definition Reference to the patient that is subject to the encounter, identified by Norwegian national id number (Fødselsnummer or DNR). A link to a resource representing the person or the group to whom the medication will be given. VKP always references a Patient Resource using a norwegian national id number (Fødslesnummer or DNR) in a logical identifier in the subject.identifier element. The Name of the patient should be given in the subject.display element. Example: `"subject":{ "identifier":{ "system":"urn:oid:2.16.578.1.12.4.1.4.1", "value":"05073500186" }, "display":"Ærlend Sørgård" }` 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). Data type Reference(Patient \| Group \| no-basis-Patient \| vkp-Patient-v06) Mappings v2: PID-3 rim: .participation[typeCode=SBJ]/role[classCode=PAT] w5: who.focus
id		0..1	string	There are no (further) constraints on this element Element id Encounter.subject.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.subject.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
reference	Σ I	0..1	string	There are no (further) constraints on this element Element id Encounter.subject.reference Short description Literal reference, Relative, internal or absolute URL Definition A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Comments Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. Data type string Mappings rim: N/A
identifier	S Σ	1..1	Identifier	There are no (further) constraints on this element Element id Encounter.subject.identifier Short description Logical reference, when literal reference is not known Definition An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. Comments When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Data type Identifier Mappings rim: .identifier
id		0..1	string	There are no (further) constraints on this element Element id Encounter.subject.identifier.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.subject.identifier.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
use	Σ ?!	0..1	codeBinding	There are no (further) constraints on this element Element id Encounter.subject.identifier.use Short description usual \| official \| temp \| secondary (If known) Definition The purpose of this identifier. 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. Data type code Binding Identifies the purpose for this identifier, if known . IdentifierUse (required) Mappings v2: N/A rim: Role.code or implied by context
type	Σ	0..1	CodeableConceptBinding	There are no (further) constraints on this element Element id Encounter.subject.identifier.type Short description Description of identifier Definition A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. 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. Data type CodeableConcept Binding A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Mappings v2: CX.5 rim: Role.code or implied by context
system	S Σ	0..1	uri	There are no (further) constraints on this element Element id Encounter.subject.identifier.system Short description 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. 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. Data type uri Examples General http://www.acme.com/identifiers/patient Mappings v2: CX.4 / EI-2-4 rim: II.root or Role.id.root servd: ./IdentifierType
value	S Σ	0..1	string	There are no (further) constraints on this element Element id Encounter.subject.identifier.value Short description 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. 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. Data type string Examples General 123456 Mappings v2: CX.1 / EI.1 rim: II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root) servd: ./Value
period	Σ	0..1	Period	There are no (further) constraints on this element Element id Encounter.subject.identifier.period Short description Time period when id is/was valid for use Definition Time period during which identifier is/was valid for use. Data type Period Mappings v2: CX.7 + CX.8 rim: Role.effectiveTime or implied by context servd: ./StartDate and ./EndDate
assigner	Σ	0..1	Reference(Organization)	There are no (further) constraints on this element Element id Encounter.subject.identifier.assigner Short description Organization that issued id (may be just text) Definition Organization that issued/manages the identifier. 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. Data type Reference(Organization) Mappings v2: CX.4 / (CX.4,CX.9,CX.10) rim: II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper servd: ./IdentifierIssuingAuthority
display	S Σ	1..1	string	There are no (further) constraints on this element Element id Encounter.subject.display Short description Text alternative for the resource Definition Plain text narrative that identifies the resource in addition to the resource reference. Comments This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. Data type string Mappings rim: N/A
episodeOfCare	Σ	0..*	Reference(EpisodeOfCare)	There are no (further) constraints on this element Element id Encounter.episodeOfCare Short description 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). Data type Reference(EpisodeOfCare) Mappings v2: PV1-54, PV1-53 rim: n/a w5: context
incomingReferral		0..*	Reference(ReferralRequest)	There are no (further) constraints on this element Element id Encounter.incomingReferral Short description The ReferralRequest that initiated this encounter Definition The referral request this encounter satisfies (incoming referral). Data type Reference(ReferralRequest) Mappings rim: .reason.ClinicalDocument
participant	S Σ	0..*	BackboneElement	Element id Encounter.participant Short description List of participants involved in the encounter Definition Refernce to the individual that participated in the encounter, usually health care provider. Identified using Norwegian national id number (fødselsnummer). The Name of the participant should be given in the subject.display element. Example: `"participant": [ { "individual":{ "identifier":{ "system":"urn:oid:2.16.578.1.12.4.1.4.1", "value":"04056600324" }, "display":"Magnar Koman" } } ]` Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings v2: ROL rim: .participation[typeCode=PFM]
id		0..1	string	There are no (further) constraints on this element Element id Encounter.participant.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.participant.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Mappings rim: n/a
modifierExtension	Σ ?!	0..*	Extension	There are no (further) constraints on this element Element id Encounter.participant.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content, modifiers 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. 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. Data type Extension Mappings rim: N/A
type	Σ	0..*	CodeableConceptBinding	There are no (further) constraints on this element Element id Encounter.participant.type Short description Role of participant in encounter Definition Role of participant in encounter. 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. Data type CodeableConcept Binding Role of participant in encounter ParticipantType (extensible) Mappings v2: ROL-3 (or maybe PRT-4) rim: .functionCode
period		0..1	Period	There are no (further) constraints on this element Element id Encounter.participant.period Short description 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. Data type Period Mappings v2: ROL-5, ROL-6 (or maybe PRT-5) rim: .time
individual	S Σ	0..1	Reference(Practitioner \| RelatedPerson \| no-basis-Practitioner)	Element id Encounter.participant.individual Short description Refernce to the individual that participated in the encounter Definition Refernce to the individual that participated in the encounter, usually health care provider. Identified using Norwegian national id number (fødselsnummer). The Name of the participant should be given in the subject.display element. Data type Reference(Practitioner \| RelatedPerson \| no-basis-Practitioner) Mappings v2: ROL-4 rim: .role w5: who
id		0..1	string	There are no (further) constraints on this element Element id Encounter.participant.individual.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.participant.individual.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
reference	Σ I	0..1	string	There are no (further) constraints on this element Element id Encounter.participant.individual.reference Short description Literal reference, Relative, internal or absolute URL Definition A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Comments Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. Data type string Mappings rim: N/A
identifier	S Σ	0..1	Identifier	Element id Encounter.participant.individual.identifier Short description Logical reference, when literal reference is not known Definition Logical refernce to the individual that participated in the encounter, usually health care provider. Identified using Norwegian national id number (fødselsnummer). The Name of the participant should be given in the subject.display element. An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. Comments When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Data type Identifier Mappings rim: .identifier
id		0..1	string	There are no (further) constraints on this element Element id Encounter.participant.individual.identifier.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.participant.individual.identifier.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
use	Σ ?!	0..1	codeBinding	There are no (further) constraints on this element Element id Encounter.participant.individual.identifier.use Short description usual \| official \| temp \| secondary (If known) Definition The purpose of this identifier. 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. Data type code Binding Identifies the purpose for this identifier, if known . IdentifierUse (required) Mappings v2: N/A rim: Role.code or implied by context
type	Σ	0..1	CodeableConceptBinding	There are no (further) constraints on this element Element id Encounter.participant.individual.identifier.type Short description Description of identifier Definition A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. 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. Data type CodeableConcept Binding A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Mappings v2: CX.5 rim: Role.code or implied by context
system	S Σ	0..1	uriFixed Value	Element id Encounter.participant.individual.identifier.system Short description The official name of the FNR namespace Definition The official name of the FNR namespace, identified by its oid value Establishes the namespace for the value - that is, a URL that describes a set values that are unique. 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. Data type uri Fixed value urn:oid:2.16.578.1.12.4.1.4.1 Mappings v2: CX.4 / EI-2-4 rim: II.root or Role.id.root servd: ./IdentifierType
value	S Σ	0..1	string	Element id Encounter.participant.individual.identifier.value Short description The FNR of the individual Definition The FNR value identifying the participant The portion of the identifier typically relevant to the user and which is unique within the context of the system. 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. Data type string Examples General 123456 Mappings v2: CX.1 / EI.1 rim: II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root) servd: ./Value
period	Σ	0..1	Period	There are no (further) constraints on this element Element id Encounter.participant.individual.identifier.period Short description Time period when id is/was valid for use Definition Time period during which identifier is/was valid for use. Data type Period Mappings v2: CX.7 + CX.8 rim: Role.effectiveTime or implied by context servd: ./StartDate and ./EndDate
assigner	Σ	0..1	Reference(Organization)	There are no (further) constraints on this element Element id Encounter.participant.individual.identifier.assigner Short description Organization that issued id (may be just text) Definition Organization that issued/manages the identifier. 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. Data type Reference(Organization) Mappings v2: CX.4 / (CX.4,CX.9,CX.10) rim: II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper servd: ./IdentifierIssuingAuthority
display	S Σ	0..1	string	Element id Encounter.participant.individual.display Short description Tha name of the individual Definition Tha name of the individual Plain text narrative that identifies the resource in addition to the resource reference. Comments This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. Data type string Mappings rim: N/A
appointment	Σ	0..1	Reference(Appointment)	There are no (further) constraints on this element Element id Encounter.appointment Short description The appointment that scheduled this encounter Definition The appointment that scheduled this encounter. Data type Reference(Appointment) Mappings v2: SCH-1 / SCH-2 rim: .outboundRelationship[typeCode=FLFS].target[classCode=ENC, moodCode=APT]
period	S	1..1	Period	Element id Encounter.period Short description The start and end time of the digital encounter Definition Time period for the digital encounter, the system should provide both start and end times. If the start-time is not known a single end time can be provided as a timestamp for the Encounter. Example code: `"period":{ "start":"2018-06-25T09:56:23.945+02:00", "end":"2018-06-25T10:01:03.936+02:00" }` Comments If not (yet) known, the end of the Period may be omitted. Data type Period Mappings v2: PV1-44, PV1-45 rim: .effectiveTime (low & high) w5: when.done
id		0..1	string	There are no (further) constraints on this element Element id Encounter.period.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.period.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
start	S Σ I	0..1	dateTime	There are no (further) constraints on this element Element id Encounter.period.start Short description Starting time with inclusive boundary Definition The start of the period. The boundary is inclusive. Comments If the low element is missing, the meaning is that the low boundary is not known. Data type dateTime Mappings v2: DR.1 rim: ./low
end	S Σ I	0..1	dateTime	There are no (further) constraints on this element Element id Encounter.period.end Short description 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. 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 Data type dateTime Mappings v2: DR.2 rim: ./high
length		0..1	Duration	There are no (further) constraints on this element Element id Encounter.length Short description Quantity of time the encounter lasted (less time absent) Definition Quantity of time the encounter lasted. This excludes the time during leaves of absence. Comments May differ from the time the Encounter.period lasted because of leave of absence. Data type Duration Mappings v2: (PV1-45 less PV1-44) iff ( (PV1-44 not empty) and (PV1-45 not empty) ); units in minutes rim: .lengthOfStayQuantity
reason	S Σ	0..1	CodeableConceptBinding	Element id Encounter.reason Short description Reason the encounter takes place (code) Alternate names Indication, Admission diagnosis Definition Reason the encounter takes place, coded according to http://ehelse.no/fhir/ValueSet/vkp-encounter-reason-v05 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). Data type CodeableConcept Binding vkp-encounter-reason-v05 vkp-encounter-reason-v05.valueset (required) Mappings v2: EVN-4 / PV2-3 (note: PV2-3 is nominally constrained to inpatient admissions; HL7 v2 makes no vocabulary suggestions for PV2-3; would not expect PV2 segment or PV2-3 to be in use in all implementations ) rim: .reasonCode w5: why
diagnosis	Σ	0..*	BackboneElement	There are no (further) constraints on this element Element id Encounter.diagnosis Short description The list of diagnosis relevant to this encounter Definition The list of diagnosis relevant to this encounter. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: .outboundRelationship[typeCode=RSON]
id		0..1	string	There are no (further) constraints on this element Element id Encounter.diagnosis.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.diagnosis.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Mappings rim: n/a
modifierExtension	Σ ?!	0..*	Extension	There are no (further) constraints on this element Element id Encounter.diagnosis.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content, modifiers 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. 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. Data type Extension Mappings rim: N/A
condition		1..1	Reference(Condition \| Procedure)	There are no (further) constraints on this element Element id Encounter.diagnosis.condition Short description Reason the encounter takes place (resource) Alternate names Admission diagnosis, discharge diagnosis, indication 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. 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). Data type Reference(Condition \| Procedure) Mappings v2: Resources that would commonly referenced at Encounter.indication would be Condition and/or Procedure. These most closely align with DG1/PRB and PR1 respectively. rim: .outboundRelationship[typeCode=RSON].target w5: why
role		0..1	CodeableConceptBinding	There are no (further) constraints on this element Element id Encounter.diagnosis.role Short description 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 …). Data type CodeableConcept Binding The type of diagnosis this condition represents DiagnosisRole (preferred) Mappings rim: n/a
rank		0..1	positiveInt	There are no (further) constraints on this element Element id Encounter.diagnosis.rank Short description Ranking of the diagnosis (for each role type) Definition Ranking of the diagnosis (for each role type). Data type positiveInt Mappings rim: .outboundRelationship[typeCode=RSON].priority
account		0..*	Reference(Account)	There are no (further) constraints on this element Element id Encounter.account Short description 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. Comments The billing system may choose to allocate billable items associated with the Encounter to different referenced Accounts based on internal business rules. Data type Reference(Account) Mappings rim: .pertains.A_Account
hospitalization		0..1	BackboneElement	There are no (further) constraints on this element Element id Encounter.hospitalization Short description Details about the admission to a healthcare service Definition Details about the admission to a healthcare service. 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. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: .outboundRelationship[typeCode=COMP].target[classCode=ENC, moodCode=EVN]
id		0..1	string	There are no (further) constraints on this element Element id Encounter.hospitalization.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.hospitalization.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Mappings rim: n/a
modifierExtension	Σ ?!	0..*	Extension	There are no (further) constraints on this element Element id Encounter.hospitalization.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content, modifiers 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. 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. Data type Extension Mappings rim: N/A
preAdmissionIdentifier		0..1	Identifier	There are no (further) constraints on this element Element id Encounter.hospitalization.preAdmissionIdentifier Short description Pre-admission identifier Definition Pre-admission identifier. Data type Identifier Mappings v2: PV1-5 rim: .id
origin		0..1	Reference(Location)	There are no (further) constraints on this element Element id Encounter.hospitalization.origin Short description The location from which the patient came before admission Definition The location from which the patient came before admission. Data type Reference(Location) Mappings rim: .participation[typeCode=ORG].role
admitSource		0..1	CodeableConceptBinding	There are no (further) constraints on this element Element id Encounter.hospitalization.admitSource Short description From where patient was admitted (physician referral, transfer) Definition From where patient was admitted (physician referral, transfer). Data type CodeableConcept Binding From where the patient was admitted. AdmitSource (preferred) Mappings v2: PV1-14 rim: .admissionReferralSourceCode
reAdmission		0..1	CodeableConcept	There are no (further) constraints on this element Element id Encounter.hospitalization.reAdmission Short description 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. Data type CodeableConcept Binding The reason for re-admission of this hospitalization encounter. v2 Re-Admission Indicator (example) Mappings v2: PV1-13 rim: n/a
dietPreference		0..*	CodeableConcept	There are no (further) constraints on this element Element id Encounter.hospitalization.dietPreference Short description Diet preferences reported by the patient Definition Diet preferences reported by the patient. 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). Data type CodeableConcept Binding Medical, cultural or ethical food preferences to help with catering requirements. Diet (example) Mappings v2: PV1-38 rim: .outboundRelationship[typeCode=COMP].target[classCode=SBADM, moodCode=EVN, code="diet"]
specialCourtesy		0..*	CodeableConceptBinding	There are no (further) constraints on this element Element id Encounter.hospitalization.specialCourtesy Short description Special courtesies (VIP, board member) Definition Special courtesies (VIP, board member). Data type CodeableConcept Binding Special courtesies SpecialCourtesy (preferred) Mappings v2: PV1-16 rim: .specialCourtesiesCode
specialArrangement		0..*	CodeableConceptBinding	There are no (further) constraints on this element Element id Encounter.hospitalization.specialArrangement Short description 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. Data type CodeableConcept Binding Special arrangements SpecialArrangements (preferred) Mappings v2: PV1-15 / OBR-30 / OBR-43 rim: .specialArrangementCode
destination		0..1	Reference(Location)	There are no (further) constraints on this element Element id Encounter.hospitalization.destination Short description Location to which the patient is discharged Definition Location to which the patient is discharged. Data type Reference(Location) Mappings v2: PV1-37 rim: .participation[typeCode=DST]
dischargeDisposition		0..1	CodeableConcept	There are no (further) constraints on this element Element id Encounter.hospitalization.dischargeDisposition Short description Category or kind of location after discharge Definition Category or kind of location after discharge. Data type CodeableConcept Binding Discharge Disposition DischargeDisposition (example) Mappings v2: PV1-36 rim: .dischargeDispositionCode
location	S	0..*	BackboneElement	Element id Encounter.location Short description List of locations where the patient has been Definition VKP uses this refererence to name location where the digital-Encounter takes place. Typically includes only location.location.display element with a textual description of the location. List of locations where the patient has been during this encounter. 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". VKP Example: `"location": [ { "location":{ "display":"rom24 @ sykehjem" } } ]` Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: .participation[typeCode=LOC]
id		0..1	string	There are no (further) constraints on this element Element id Encounter.location.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.location.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Mappings rim: n/a
modifierExtension	Σ ?!	0..*	Extension	There are no (further) constraints on this element Element id Encounter.location.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content, modifiers 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. 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. Data type Extension Mappings rim: N/A
location	S	1..1	Reference(Location)	Element id Encounter.location.location Short description Location the encounter takes place Definition A location reference. Only display value is supported by the VKP. The location where the encounter takes place. Data type Reference(Location) Mappings v2: PV1-3 / PV1-6 / PV1-11 / PV1-42 / PV1-43 rim: .role w5: where
id		0..1	string	There are no (further) constraints on this element Element id Encounter.location.location.id Short description 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. Data type string Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Encounter.location.location.extension Short description Additional Content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
reference	Σ I	0..1	string	There are no (further) constraints on this element Element id Encounter.location.location.reference Short description Literal reference, Relative, internal or absolute URL Definition A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Comments Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. Data type string Mappings rim: N/A
identifier	Σ	0..1	Identifier	There are no (further) constraints on this element Element id Encounter.location.location.identifier Short description Logical reference, when literal reference is not known Definition An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. Comments When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Data type Identifier Mappings rim: .identifier
display	S Σ	0..1	string	Element id Encounter.location.location.display Short description Text alternative for the resource Definition The Display value for the location. In vkp the format is usually "[room or room-number] @ [location name]". Plain text narrative that identifies the resource in addition to the resource reference. Comments This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. Data type string Examples display "rom24 @ sykehjem" Mappings rim: N/A
status		0..1	codeBinding	There are no (further) constraints on this element Element id Encounter.location.status Short description 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. 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. Data type code Binding The status of the location. EncounterLocationStatus (required) Mappings rim: .role.statusCode
period		0..1	Period	There are no (further) constraints on this element Element id Encounter.location.period Short description Time period during which the patient was present at the location Definition Time period during which the patient was present at the location. Data type Period Mappings rim: .time
serviceProvider		0..1	Reference(Organization)	There are no (further) constraints on this element Element id Encounter.serviceProvider Short description 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. Data type Reference(Organization) Mappings v2: PV1-10 / PL.6 & PL.1 (note: HL7 v2 definition is "the treatment or type of surgery that the patient is scheduled to receive"; seems slightly out of alignment with the concept name 'hospital service'. Would not trust that implementations apply this semantic by default) rim: .particiaption[typeCode=PFM].role
partOf		0..1	Reference(Encounter)	There are no (further) constraints on this element Element id Encounter.partOf Short description Another Encounter this encounter is part of Definition Another Encounter of which this encounter is a part of (administratively or in time). 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. Data type Reference(Encounter) Mappings rim: .inboundRelationship[typeCode=COMP].source[classCode=COMP, moodCode=EVN]