Da Vinci - Coverage Requirements Discovery
2.1.0 - STU 2.1 United States of America flag

Da Vinci - Coverage Requirements Discovery, published by HL7 International / Financial Management. This guide is not an authorized publication; it is the continuous build for version 2.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/davinci-crd/ and changes regularly. See the Directory of published versions

Resource Profile: CRDDeviceRequest - Detailed Descriptions

Page standards status: Trial-use Maturity Level: 3

Definitions for the profile-devicerequest resource profile.

Guidance on how to interpret the contents of this table can be found here

0. DeviceRequest
2. DeviceRequest.extension
SlicingThis element introduces a set of slices on DeviceRequest.extension. The slices areUnordered and Open, and can be differentiated using the following discriminators:
  • value @ url
  • 4. DeviceRequest.extension:Coverage-Information
    Slice NameCoverage-Information
    Control0..*
    TypeExtension(Coverage Information) (Complex Extension)
    Must Supporttrue
    6. DeviceRequest.identifier
    NoteThis is a business identifier, not a resource identifier (see discussion)
    Must Supporttrue
    8. DeviceRequest.basedOn
    Must Supporttrue
    10. DeviceRequest.status
    Comments

    This will be 'draft' when using order-select or an initial order-sign, but may be 'active' or other values for order-sign representing edits to the order or for order-dispatch.

    Control1..?
    Must Supporttrue
    Example<br/><b>General</b>:draft
    12. DeviceRequest.code[x]
    BindingUnless not suitable, these codes SHALL be taken from CRD Device Request Codes Value Set
    (extensible to http://hl7.org/fhir/us/davinci-crd/ValueSet/deviceRequest)
    TypeChoice of: Reference(CRD Device), CodeableConcept
    [x] NoteSeeChoice of Data Typesfor further information about how to use [x]
    Must Supporttrue
    Must Support TypesNo must-support rules about the choice of types/profiles
    14. DeviceRequest.parameter
    Must Supporttrue
    16. DeviceRequest.subject
    TypeReference(CRD Patient)
    Must Supporttrue
    18. DeviceRequest.encounter
    Comments

    potentially relevant for CRD in some situations.

    TypeReference(CRD Encounter)
    20. DeviceRequest.occurrence[x]
    [x] NoteSeeChoice of Data Typesfor further information about how to use [x]
    Must Supporttrue
    22. DeviceRequest.authoredOn
    Control1..?
    Must Supporttrue
    24. DeviceRequest.requester
    Control1..?
    TypeReference(US Core Practitioner Profile, HRex PractitionerRole Profile)
    Must Supporttrue
    Must Support TypesReference(US Core Practitioner Profile, HRex PractitionerRole Profile)
    26. DeviceRequest.performer
    TypeReference(US Core Practitioner Profile, HRex PractitionerRole Profile)
    Must Supporttrue
    Must Support TypesReference(US Core Practitioner Profile, HRex PractitionerRole Profile)
    28. DeviceRequest.reasonCode
    Must Supporttrue
    30. DeviceRequest.reasonReference
    Comments

    potentially relevant for CRD in some situations.

    Must Supporttrue