Current Build

Переводит команда Health Samurai . Приглашаем поучаствовать в русификации стандарта FHIR: GitHub , Email.

12.20 Ресурс DeviceUseStatement - Назначение

Orders and Observations Work GroupMaturity Level: 0 Trial UseSecurity Category: Patient Compartments: Device, Patient

A record of a device being used by a patient where the record is the result of a report from the patient or another clinician.

Эти ресурсы еще не прошли надлежащую проверку PC, CQI, CDS и OO. На данный момент они считаются потенциальными черновыми предложениями ресурсов.

This resource is an event resource from a FHIR workflow perspective - see Workflow. It is the intent of the Orders and Observation Workgroup to align this resource with the workflow pattern for event resources.

В данный ресурс записывается использование пациентом медицинского изделия. Эта запись является результатом сообщения об использовании пациентом, другим поставщиком мед. услуг или родственником. Ресурс можно использовать для записи о применении вспомогательных изделий, например инвалидная коляска или слуховой аппарат, контрацептивов, например внутриматочная спираль, или других имплантированных изделий, например кардиостимулятор.

Данный ресурс отличается от DeviceRequest, который записывает запрос на использование изделия. Также он отличается от ресурса Procedure, который может описывать имплантацию или эксплантацию изделия.

Структура

ИмяФлагиКард.ТипОписание и ограниченияdoco
.. DeviceUseStatement TUDomainResourceRecord of use of a device
Элементы, определённые в прародителе: id, meta, implicitRules, language, text, contained, extension, modifierExtension
... identifier Σ0..*IdentifierExternal identifier for this record
... basedOn Σ0..*Reference(ServiceRequest)Fulfills plan, proposal or order
... status ?!Σ1..1codeactive | completed | entered-in-error +
DeviceUseStatementStatus (Required)
... subject Σ1..1Reference(Patient | Group)Patient using device
... derivedFrom Σ0..*Reference(ServiceRequest | Procedure | Claim | Observation | QuestionnaireResponse | DocumentReference)Supporting information
... timing[x] Σ0..1How often the device was used
.... timingTimingTiming
.... timingPeriodPeriod
.... timingDateTimedateTime
... recordedOn Σ0..1dateTimeWhen statement was recorded
... source Σ0..1Reference(Patient | Practitioner | RelatedPerson)Who made the statement
... device Σ1..1Reference(Device)Reference to device used
... reasonCode Σ0..*CodeableConceptWhy device was used
... reasonReference Σ0..*Reference(Condition | Observation | DiagnosticReport | DocumentReference | Media)Why was DeviceUseStatement performed?
... bodySite Σ0..1CodeableConceptTarget body site
SNOMED CT Body Structures (Example)
... note 0..*AnnotationAddition details (comments, instructions)

doco Документация по этому формату

UML-диаграмма (Legend)

DeviceUseStatement (DomainResource)An external identifier for this statement such as an IRIidentifier : Identifier [0..*]A plan, proposal or order that is fulfilled in whole or in part by this DeviceUseStatementbasedOn : Reference [0..*] « ServiceRequest »A code representing the patient or other source's judgment about the state of the device used that this statement is about. Generally this will be active or completed (this element modifies the meaning of other elements)status : code [1..1] « A coded concept indicating the current status of the Device Usage. (Strength=Required)DeviceUseStatementStatus! »The patient who used the devicesubject : Reference [1..1] « Patient|Group »Allows linking the DeviceUseStatement to the underlying Request, or to other information that supports or is used to derive the DeviceUseStatementderivedFrom : Reference [0..*] « ServiceRequest|Procedure|Claim| Observation|QuestionnaireResponse|DocumentReference »How often the device was usedtiming[x] : Type [0..1] « Timing|Period|dateTime »The time at which the statement was made/recordedrecordedOn : dateTime [0..1]Who reported the device was being used by the patientsource : Reference [0..1] « Patient|Practitioner|RelatedPerson »The details of the device useddevice : Reference [1..1] « Device »Reason or justification for the use of the devicereasonCode : CodeableConcept [0..*]Indicates another resource whose existence justifies this DeviceUseStatementreasonReference : Reference [0..*] « Condition|Observation| DiagnosticReport|DocumentReference|Media »Indicates the anotomic location on the subject's body where the device was used ( i.e. the target)bodySite : CodeableConcept [0..1] « Codes describing anatomical locations. May include laterality. (Strength=Example)SNOMEDCTBodyStructures?? »Details about the device statement 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 statementnote : Annotation [0..*]

Turtle-шаблон

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:DeviceUseStatement;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:DeviceUseStatement.identifier [ Identifier ], ... ; # 0..* External identifier for this record
  fhir:DeviceUseStatement.basedOn [ Reference(ServiceRequest) ], ... ; # 0..* Fulfills plan, proposal or order
  fhir:DeviceUseStatement.status [ code ]; # 1..1 active | completed | entered-in-error +
  fhir:DeviceUseStatement.subject [ Reference(Patient|Group) ]; # 1..1 Patient using device
  fhir:DeviceUseStatement.derivedFrom [ Reference(ServiceRequest|Procedure|Claim|Observation|QuestionnaireResponse|
  DocumentReference) ], ... ; # 0..* Supporting information
  # DeviceUseStatement.timing[x] : 0..1 How often  the device was used. One of these 3
    fhir:DeviceUseStatement.timingTiming [ Timing ]
    fhir:DeviceUseStatement.timingPeriod [ Period ]
    fhir:DeviceUseStatement.timingDateTime [ dateTime ]
  fhir:DeviceUseStatement.recordedOn [ dateTime ]; # 0..1 When statement was recorded
  fhir:DeviceUseStatement.source [ Reference(Patient|Practitioner|RelatedPerson) ]; # 0..1 Who made the statement
  fhir:DeviceUseStatement.device [ Reference(Device) ]; # 1..1 Reference to device used
  fhir:DeviceUseStatement.reasonCode [ CodeableConcept ], ... ; # 0..* Why device was used
  fhir:DeviceUseStatement.reasonReference [ Reference(Condition|Observation|DiagnosticReport|DocumentReference|Media) ], ... ; # 0..* Why was DeviceUseStatement performed?
  fhir:DeviceUseStatement.bodySite [ CodeableConcept ]; # 0..1 Target body site
  fhir:DeviceUseStatement.note [ Annotation ], ... ; # 0..* Addition details (comments, instructions)
]

Changes since R3

DeviceUseStatement
DeviceUseStatement.basedOn
  • Added Element
DeviceUseStatement.derivedFrom
  • Added Element
DeviceUseStatement.reasonCode
  • Added Element
DeviceUseStatement.reasonReference
  • Added Element
DeviceUseStatement.whenUsed
  • deleted
DeviceUseStatement.indication
  • deleted

See the Full Difference for further information

This analysis is available as XML or JSON.

See R3 <--> R4 Conversion Maps (status = 1 test that all execute ok. All tests pass round-trip testing and all r3 resources are valid.)

Структура

ИмяФлагиКард.ТипОписание и ограниченияdoco
.. DeviceUseStatement TUDomainResourceRecord of use of a device
Элементы, определённые в прародителе: id, meta, implicitRules, language, text, contained, extension, modifierExtension
... identifier Σ0..*IdentifierExternal identifier for this record
... basedOn Σ0..*Reference(ServiceRequest)Fulfills plan, proposal or order
... status ?!Σ1..1codeactive | completed | entered-in-error +
DeviceUseStatementStatus (Required)
... subject Σ1..1Reference(Patient | Group)Patient using device
... derivedFrom Σ0..*Reference(ServiceRequest | Procedure | Claim | Observation | QuestionnaireResponse | DocumentReference)Supporting information
... timing[x] Σ0..1How often the device was used
.... timingTimingTiming
.... timingPeriodPeriod
.... timingDateTimedateTime
... recordedOn Σ0..1dateTimeWhen statement was recorded
... source Σ0..1Reference(Patient | Practitioner | RelatedPerson)Who made the statement
... device Σ1..1Reference(Device)Reference to device used
... reasonCode Σ0..*CodeableConceptWhy device was used
... reasonReference Σ0..*Reference(Condition | Observation | DiagnosticReport | DocumentReference | Media)Why was DeviceUseStatement performed?
... bodySite Σ0..1CodeableConceptTarget body site
SNOMED CT Body Structures (Example)
... note 0..*AnnotationAddition details (comments, instructions)

doco Документация по этому формату

UML-диаграмма (Legend)

DeviceUseStatement (DomainResource)An external identifier for this statement such as an IRIidentifier : Identifier [0..*]A plan, proposal or order that is fulfilled in whole or in part by this DeviceUseStatementbasedOn : Reference [0..*] « ServiceRequest »A code representing the patient or other source's judgment about the state of the device used that this statement is about. Generally this will be active or completed (this element modifies the meaning of other elements)status : code [1..1] « A coded concept indicating the current status of the Device Usage. (Strength=Required)DeviceUseStatementStatus! »The patient who used the devicesubject : Reference [1..1] « Patient|Group »Allows linking the DeviceUseStatement to the underlying Request, or to other information that supports or is used to derive the DeviceUseStatementderivedFrom : Reference [0..*] « ServiceRequest|Procedure|Claim| Observation|QuestionnaireResponse|DocumentReference »How often the device was usedtiming[x] : Type [0..1] « Timing|Period|dateTime »The time at which the statement was made/recordedrecordedOn : dateTime [0..1]Who reported the device was being used by the patientsource : Reference [0..1] « Patient|Practitioner|RelatedPerson »The details of the device useddevice : Reference [1..1] « Device »Reason or justification for the use of the devicereasonCode : CodeableConcept [0..*]Indicates another resource whose existence justifies this DeviceUseStatementreasonReference : Reference [0..*] « Condition|Observation| DiagnosticReport|DocumentReference|Media »Indicates the anotomic location on the subject's body where the device was used ( i.e. the target)bodySite : CodeableConcept [0..1] « Codes describing anatomical locations. May include laterality. (Strength=Example)SNOMEDCTBodyStructures?? »Details about the device statement 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 statementnote : Annotation [0..*]

Turtle-шаблон

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:DeviceUseStatement;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:DeviceUseStatement.identifier [ Identifier ], ... ; # 0..* External identifier for this record
  fhir:DeviceUseStatement.basedOn [ Reference(ServiceRequest) ], ... ; # 0..* Fulfills plan, proposal or order
  fhir:DeviceUseStatement.status [ code ]; # 1..1 active | completed | entered-in-error +
  fhir:DeviceUseStatement.subject [ Reference(Patient|Group) ]; # 1..1 Patient using device
  fhir:DeviceUseStatement.derivedFrom [ Reference(ServiceRequest|Procedure|Claim|Observation|QuestionnaireResponse|
  DocumentReference) ], ... ; # 0..* Supporting information
  # DeviceUseStatement.timing[x] : 0..1 How often  the device was used. One of these 3
    fhir:DeviceUseStatement.timingTiming [ Timing ]
    fhir:DeviceUseStatement.timingPeriod [ Period ]
    fhir:DeviceUseStatement.timingDateTime [ dateTime ]
  fhir:DeviceUseStatement.recordedOn [ dateTime ]; # 0..1 When statement was recorded
  fhir:DeviceUseStatement.source [ Reference(Patient|Practitioner|RelatedPerson) ]; # 0..1 Who made the statement
  fhir:DeviceUseStatement.device [ Reference(Device) ]; # 1..1 Reference to device used
  fhir:DeviceUseStatement.reasonCode [ CodeableConcept ], ... ; # 0..* Why device was used
  fhir:DeviceUseStatement.reasonReference [ Reference(Condition|Observation|DiagnosticReport|DocumentReference|Media) ], ... ; # 0..* Why was DeviceUseStatement performed?
  fhir:DeviceUseStatement.bodySite [ CodeableConcept ]; # 0..1 Target body site
  fhir:DeviceUseStatement.note [ Annotation ], ... ; # 0..* Addition details (comments, instructions)
]

Changes since Release 3

DeviceUseStatement
DeviceUseStatement.basedOn
  • Added Element
DeviceUseStatement.derivedFrom
  • Added Element
DeviceUseStatement.reasonCode
  • Added Element
DeviceUseStatement.reasonReference
  • Added Element
DeviceUseStatement.whenUsed
  • deleted
DeviceUseStatement.indication
  • deleted

See the Full Difference for further information

This analysis is available as XML or JSON.

See R3 <--> R4 Conversion Maps (status = 1 test that all execute ok. All tests pass round-trip testing and all r3 resources are valid.)

 

See the Profiles & Extensions and the Альтернативные определения: Основное определение XML + JSON, XML Schema/Schematron + JSON Schema, ShEx (for Turtle) + see the extensions & the Анализ зависимостей

PathОписаниеТипСсылка
DeviceUseStatement.status A coded concept indicating the current status of the Device Usage.RequiredDeviceUseStatementStatus
DeviceUseStatement.bodySite Codes describing anatomical locations. May include laterality.ExampleSNOMEDCTBodyStructures

Примечание для рецензентов:

На данный момент кодовые привязки оставлены пустыми и будут конкретизированы позже, после проверки сообществом.

Параметры поиска для этого ресурса. Также к нему применяются общие параметры. Более подробную информацию о поиске в REST, обмене сообщениями и сервисах см. в разделе Поиск.

ИмяТипОпределениеВыражениеIn Common
devicereferenceSearch by deviceDeviceUseStatement.device
(Device)
identifiertokenSearch by identifierDeviceUseStatement.identifier
patientreferenceSearch by subject - a patientDeviceUseStatement.subject
(Group, Patient)
29 Resources
subjectreferenceSearch by subjectDeviceUseStatement.subject
(Group, Patient)