ePflegebericht

Hilfsmittel

Vorhandene Hilfsmittel

Vorhandene Hilfsmittel werden als Device modelliert. Die Nutzung im Kontext einer bestimmten Condition kann über ein DeviceUseStatement erfolgen.

Zukünftige Hilfsmittel

Für geplante oder beantragte Hilfsmittel gibt es zwei Alternativen:

Sie werden ebenfalls als Device modelliert werden. Das Device wird dann aus einem DeviceRequest heraus über codeReference referenziert.
Sie werden als codeCodeableConcept in DeviceRequest angegeben. In diesem Fall wird über den Code angegeben, was für ein Hilfsmittel es sein soll, genauere Angaben zum Hersteller etc. entfallen.

Der DeviceRequest kann über reasonReference auf eine Condition, z.B. ein Pflegeproblem, oder auf eine Observation, z.B. ein pflegerisches Assessment, verweisen.

Device

Das Device selbst wird hier nicht profiliert.

DeviceRequest

GeNSDeviceRequest

DeviceRequest	I		DeviceRequest	There are no (further) constraints on this element Element id DeviceRequest Short description Medical device request Definition Represents a request for a patient to employ a medical device. The device may be an implantable device, or an external assistive device, such as a walker. Data type DeviceRequest Constraints dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources `contained.contained.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 or SHALL refer to the containing resource `contained.where((('#'+id in (%resource.descendants().reference \| %resource.descendants().as(canonical) \| %resource.descendants().as(uri) \| %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()` dom-6: A resource should have narrative for robust management text.`div`.exists() dom-5: If a resource is contained in another resource, it SHALL NOT have a security label `contained.meta.security.empty()` Mappings rim: Entity. Role, or Act workflow: Request v2: ORC rim: Act[moodCode<=INT]
id	Σ	0..1	string	There are no (further) constraints on this element Element id DeviceRequest.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 string
meta	Σ	0..1	Meta	There are no (further) constraints on this element Element id DeviceRequest.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 might not always be associated with version changes to the resource. Data type Meta Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
implicitRules	Σ ?!	0..1	uri	There are no (further) constraints on this element Element id DeviceRequest.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. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
language		0..1	codeBinding	There are no (further) constraints on this element Element id DeviceRequest.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. CommonLanguages (preferred) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
text		0..1	Narrative	There are no (further) constraints on this element Element id DeviceRequest.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 can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. 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 information is added later. Data type Narrative Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A rim: Act.text?
contained		0..*	Resource	There are no (further) constraints on this element Element id DeviceRequest.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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels. Data type Resource Mappings rim: Entity. Role, or Act rim: N/A
extension	I	0..*	Extension	There are no (further) constraints on this element Element id DeviceRequest.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. 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 can 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 Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (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
modifierExtension	?! I	0..*	Extension	There are no (further) constraints on this element Element id DeviceRequest.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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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 Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (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
identifier	Σ	0..*	Identifier	There are no (further) constraints on this element Element id DeviceRequest.identifier Short description External Request identifier Definition Identifiers assigned to this order by the orderer or by the receiver. Data type Identifier Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CX / EI (occasionally, more often EI maps to a resource id or a URL) rim: II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT] servd: Identifier workflow: Request.identifier w5: FiveWs.identifier v2: ORC.2, ORC.3 rim: .identifier quick: ClinicalStatement.identifier
instantiatesCanonical	Σ	0..*	canonical(ActivityDefinition \| PlanDefinition)	There are no (further) constraints on this element Element id DeviceRequest.instantiatesCanonical Short description Instantiates FHIR protocol or definition Definition The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this DeviceRequest. Comments Note: This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number. Data type canonical(ActivityDefinition \| PlanDefinition) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Request.instantiatesCanonical v2: Varies by domain rim: .outboundRelationship[typeCode=DEFN].target
instantiatesUri	Σ	0..*	uri	There are no (further) constraints on this element Element id DeviceRequest.instantiatesUri Short description Instantiates external protocol or definition Definition The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this DeviceRequest. Comments This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Request.instantiatesUri v2: Varies by domain rim: .outboundRelationship[typeCode=DEFN].target
basedOn	Σ I	0..*	Reference(Resource)	There are no (further) constraints on this element Element id DeviceRequest.basedOn Short description What request fulfills Definition Plan/proposal/order fulfilled by this request. Comments References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Data type Reference(Resource) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Request.basedOn v2: ORC.8 (plus others) rim: .outboundRelationship[typeCode=FLFS].target quick: Proposal.prnReason.reason
priorRequest	Σ I	0..*	Reference(Resource)	There are no (further) constraints on this element Element id DeviceRequest.priorRequest Short description What request replaces Definition The request takes the place of the referenced completed or terminated request(s). Comments References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Data type Reference(Resource) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Request.replaces v2: Handled by message location of ORC (ORC.1=RO or RU) rim: .outboundRelationship[typeCode=RPLC].target
groupIdentifier	Σ	0..1	Identifier	There are no (further) constraints on this element Element id DeviceRequest.groupIdentifier Short description Identifier of composite request Definition Composite request this is part of. Data type Identifier Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CX / EI (occasionally, more often EI maps to a resource id or a URL) rim: II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT] servd: Identifier workflow: Request.groupIdentifier v2: ORC.4 rim: .inboundRelationship(typeCode=COMP].source[moodCode=INT].identifier
status	Σ ?!	0..1	codeBinding	There are no (further) constraints on this element Element id DeviceRequest.status Short description draft \| active \| on-hold \| revoked \| completed \| entered-in-error \| unknown Definition The status of the request. Comments This element is labeled as a modifier because the status contains the codes cancelled and entered-in-error that mark the request as not currently valid. Data type code Binding Codes representing the status of the request. RequestStatus (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Request.status w5: FiveWs.status v2: ORC.5 rim: .status quick: Action.currentStatus
intent	Σ ?!	1..1	codeBinding	There are no (further) constraints on this element Element id DeviceRequest.intent Short description proposal \| plan \| directive \| order \| original-order \| reflex-order \| filler-order \| instance-order \| option Definition Whether the request is a proposal, plan, an original order or a reflex order. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data type code Binding The kind of diagnostic request. RequestIntent (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Request.intent w5: FiveWs.class v2: N/A rim: .moodCode (nuances beyond PRP/PLAN/RQO would need to be elsewhere)
priority	Σ	0..1	codeBinding	There are no (further) constraints on this element Element id DeviceRequest.priority Short description routine \| urgent \| asap \| stat Definition Indicates how quickly the {{title}} should be addressed with respect to other requests. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Meaning when missing If missing, normal priority Data type code Binding Identifies the level of importance to be assigned to actioning the request. RequestPriority (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Request.priority w5: FiveWs.grade v2: TQ1.9 rim: .priorityCode
code[x]	S Σ	1..1		There are no (further) constraints on this element Element id DeviceRequest.code[x] Short description Device requested Definition The details of the device to be used. Binding Codes for devices that can be requested. FHIRDeviceTypes (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Request.code w5: FiveWs.what[x] v2: Varies by domain rim: .code quick: DeviceUse.device
codeCodeableConcept			CodeableConcept	There are no (further) constraints on this element Data type CodeableConcept
codeReference			Reference(Device)	There are no (further) constraints on this element Data type Reference(Device)
parameter		0..*	BackboneElement	There are no (further) constraints on this element Element id DeviceRequest.parameter Short description Device details Definition Specific parameters for the ordered item. For example, the prism value for lenses. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a w5: FiveWs.what[x] v2: Varies by domain rim: .code quick: DeviceUse.device
id		0..1	string	There are no (further) constraints on this element Element id DeviceRequest.parameter.id Short description Unique id for inter-element referencing 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	I	0..*	Extension	There are no (further) constraints on this element Element id DeviceRequest.parameter.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. 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 can 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 Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (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
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id DeviceRequest.parameter.modifierExtension Short description Extensions that cannot be ignored even if unrecognized 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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 Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (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
code		0..1	CodeableConcept	There are no (further) constraints on this element Element id DeviceRequest.parameter.code Short description Device detail Definition A code or string that identifies the device detail being asserted. Comments Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Data type CodeableConcept Binding A code that identifies the device detail. (unbound) (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD w5: FiveWs.what[x] v2: Varies by domain rim: .code quick: DeviceUse.device
value[x]		0..1		There are no (further) constraints on this element Element id DeviceRequest.parameter.value[x] Short description Value of detail Definition The value of the device detail. Comments Range means device should have a value that falls somewhere within the specified range. Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a w5: FiveWs.what[x] v2: Varies by domain rim: .code quick: DeviceUse.device
valueCodeableConcept			CodeableConcept	There are no (further) constraints on this element Data type CodeableConcept
valueQuantity			Quantity	There are no (further) constraints on this element Data type Quantity
valueRange			Range	There are no (further) constraints on this element Data type Range
valueBoolean			boolean	There are no (further) constraints on this element Data type boolean
subject	Σ I	1..1	Reference(Patient \| Group \| Location \| Device)	There are no (further) constraints on this element Element id DeviceRequest.subject Short description Focus of request Definition The patient who will use the device. Comments References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Data type Reference(Patient \| Group \| Location \| Device) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Request.subject w5: FiveWs.subject[x] v2: Accompanying PID segment rim: .participation[typeCode=SBJ].role quick: ClinicalStatement.subject w5: FiveWs.subject
encounter	Σ I	0..1	Reference(Encounter)	There are no (further) constraints on this element Element id DeviceRequest.encounter Short description Encounter motivating request Definition An encounter that provides additional context in which this request is made. Comments References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Data type Reference(Encounter) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Request.encounter w5: FiveWs.context v2: Accompanying PV1 rim: .inboundRelationship(typeCode=COMP].source[classCode<=PCPR, moodCode=EVN] quick: ClinicalStatement.encounter
occurrence[x]	Σ	0..1		There are no (further) constraints on this element Element id DeviceRequest.occurrence[x] Short description Desired time or schedule for use Definition The timing schedule for the use of the device. The Schedule data type allows many different expressions, for example. "Every 8 hours"; "Three times a day"; "1/2 an hour before breakfast for 10 days from 23-Dec 2011:"; "15 Oct 2013, 17 Oct 2013 and 1 Nov 2013". Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Request.occurrence[x] w5: FiveWs.planned v2: Accompanying TQ1/TQ2 segments rim: .effectiveTime quick: DeviceUse.applicationSchedule
occurrenceDateTime			dateTime	There are no (further) constraints on this element Data type dateTime
occurrencePeriod			Period	There are no (further) constraints on this element Data type Period
occurrenceTiming			Timing	There are no (further) constraints on this element Data type Timing
authoredOn	Σ	0..1	dateTime	There are no (further) constraints on this element Element id DeviceRequest.authoredOn Short description When recorded Definition When the request transitioned to being actionable. Data type dateTime Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Request.authoredOn w5: FiveWs.recorded v2: ORC.9 rim: .participation[typeCode=AUT].time quick: ClinicalStatement.statementDateTime
requester	Σ I	0..1	Reference(Device \| Practitioner \| PractitionerRole \| Organization)	There are no (further) constraints on this element Element id DeviceRequest.requester Short description Who/what is requesting diagnostics Definition The individual who initiated the request and has responsibility for its activation. Comments References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Data type Reference(Device \| Practitioner \| PractitionerRole \| Organization) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Request.requester w5: FiveWs.author v2: ORC.12 rim: .participation[typeCode=AUT].role
performerType	Σ	0..1	CodeableConcept	There are no (further) constraints on this element Element id DeviceRequest.performerType Short description Filler role Definition Desired type of performer for doing the diagnostic testing. Comments Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Data type CodeableConcept Binding Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc. ParticipantRoles (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD workflow: Request.performerType w5: FiveWs.actor v2: PRT rim: .participation[typeCode=PRF].role[scoper.determinerCode=KIND].code
performer	Σ I	0..1	Reference(Practitioner \| PractitionerRole \| Organization \| CareTeam \| HealthcareService \| Patient \| Device \| RelatedPerson)	There are no (further) constraints on this element Element id DeviceRequest.performer Short description Requested Filler Definition The desired performer for doing the diagnostic testing. Comments References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Data type Reference(Practitioner \| PractitionerRole \| Organization \| CareTeam \| HealthcareService \| Patient \| Device \| RelatedPerson) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Request.performer w5: FiveWs.actor v2: PRT rim: .participation[typeCode=PRF].role[scoper.determinerCode=INSTANCE]
reasonCode	Σ	0..*	CodeableConcept	There are no (further) constraints on this element Element id DeviceRequest.reasonCode Short description Coded Reason for request Definition Reason or justification for the use of this device. Comments Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Data type CodeableConcept Binding Diagnosis or problem codes justifying the reason for requesting the device. Condition/Problem/DiagnosisCodes (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD workflow: Request.reasonCode w5: FiveWs.why[x] v2: ORC.16 rim: .reasonCode quick: Action.indication.reason
reasonReference	S Σ I	0..*	Reference(Condition \| Observation \| GeNSNursingProblem \| GeNSNursingGoal)	Element id DeviceRequest.reasonReference Short description Linked Reason for request Definition Reason or justification for the use of this device. Comments References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Data type Reference(Condition \| Observation \| GeNSNursingProblem \| GeNSNursingGoal) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Request.reasonReference w5: FiveWs.why[x] v2: ORC.16 rim: .outboundRelationship[typeCode=RSON].target
insurance	I	0..*	Reference(Coverage \| ClaimResponse)	There are no (further) constraints on this element Element id DeviceRequest.insurance Short description Associated insurance coverage Definition Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be required for delivering the requested service. Comments References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Data type Reference(Coverage \| ClaimResponse) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Request.insurance v2: IN1/IN2 rim: .outboundRelationship[typeCode=COVBY].target
supportingInfo	I	0..*	Reference(Resource)	There are no (further) constraints on this element Element id DeviceRequest.supportingInfo Short description Additional clinical information Definition Additional clinical information about the patient that may influence the request fulfilment. For example, this may include where on the subject's body the device will be used (i.e. the target site). Requirements Knowing where the device is targeted is important for tracking if multiple sites are possible. Comments References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Data type Reference(Resource) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Request.supportingInfo v2: Accompanying segments rim: .outboundRelationship[typeCode=PERT].target
note		0..*	Annotation	There are no (further) constraints on this element Element id DeviceRequest.note Short description Notes or comments Definition Details about this request that were not represented at all or sufficiently in one of the attributes provided in a class. These may include for example a comment, an instruction, or a note associated with the statement. Comments For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible). Data type Annotation Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: N/A rim: Act workflow: Request.note v2: NTE rim: .inboundRelationship(typeCode=SUBJ].source[classCode=ANNGEN, moodCode=EVN].value[xsi:type=ST] quick: ClinicalStatement.additionalText
relevantHistory	I	0..*	Reference(Provenance)	There are no (further) constraints on this element Element id DeviceRequest.relevantHistory Short description Request provenance Definition Key events in the history of the request. Comments This might not include provenances for all versions of the request - only those deemed "relevant" or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a "relevant" change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject. Data type Reference(Provenance) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Request.relevantHistory v2: N/A rim: .inboundRelationship(typeCode=SUBJ].source[classCode=CACT, moodCode=EVN]

Beispiel: vorhandenes Hilfsmittel

<Device xmlns="http://hl7.org/fhir">
    <id value="Toilettensitz" />
    <status value="active" />
    <type>
        <coding>
            <system value="http://snomed.info/sct" />
            <code value="705593007" />
            <display value="erh&#246;hter Toilettensitz" />
        </coding>
    </type>
    <patient>
        <reference value="Patient/example" />
    </patient>
</Device>

Beispiel: geplantes Hilfsmittel - Variante (a): Rollator

<Device xmlns="http://hl7.org/fhir">
    <id value="Rollator" />
    <status value="active" />
    <manufacturer value="Becker HomeCare" />
    <type>
        <coding>
            <system value="http://snomed.info/sct" />
            <code value="705406009" />
            <display value="Rollator" />
        </coding>
    </type>
    <patient>
        <reference value="Patient/example" />
    </patient>
</Device>

<DeviceRequest xmlns="http://hl7.org/fhir">
    <id value="GeNS_EX_RollatorRequest" />
    <meta>
        <profile value="http://hs-osnabrueck.de/fhir/ePflegebericht/StructureDefinition/DeviceRequest" />
    </meta>
    <status value="active" />
    <intent value="order" />
    <codeReference>
        <reference value="Device/Rollator" />
    </codeReference>
    <subject>
        <reference value="Patient/example" />
    </subject>
    <authoredOn value="2019-11-05" />
</DeviceRequest>

Beispiel: geplantes Hilfsmittel - Variante (b): Rollstuhl

<DeviceRequest xmlns="http://hl7.org/fhir">
    <id value="GeNS_EX_Rollstuhl" />
    <meta>
        <profile value="http://hs-osnabrueck.de/fhir/ePflegebericht/StructureDefinition/DeviceRequest" />
    </meta>
    <status value="active" />
    <intent value="plan" />
    <codeCodeableConcept>
        <coding>
            <system value="http://snomed.info/sct" />
            <code value="58938008" />
            <display value="Rollstuhl" />
        </coding>
    </codeCodeableConcept>
    <subject>
        <reference value="Patient/example" />
    </subject>
</DeviceRequest>