This page is part of the FHIR Specification (v0.5.0: DSTU 2 Ballot 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
This is the narrative for the resource. See also the XML or JSON format.
(Requirements Definition)
Published: 2014-12-02 (draft)
Published by: HL7 Orders and Observation Workgroup Primary Author: Eric Haas Health eData Inc
This profile defines the expected capabilities of the USLabOrder Orderer actor when conforming to the The US Laboratory Order Implementation (USLabOrder). This actor is the originator of a laboratory test order request to the laboratory (order filler) and declares conformance to RESTful FHIR and FHIR profiles defined in this guide. The order reference one or more FHIR resources conforming to profiles outlined in the USLabOrder guide.
FHIR Version: | 0.8 |
---|---|
Supported formats: | xml, json |
Mode: Server
This conformance resource assumes the USLabOrder Orderer is the server, in other words, operating in 'Pull' or 'Push/Pull' RESTful interface. The USLabOrder Orderer MUST support querying one or more resources outlined by the USLabOrder Guide. The USLabOrder Orderer MUST use all the vocabularies and value set constraints defined by the individual resource profiles used by USLabOrder. The USLabOrder Orderer MUST implement REST behavior according to the FHIR specification and MUST be able to handle errors gracefully from Query Responders who may not support the submitted query.
Security:
Implementations must meet the security requirements documented in the USLabOrder Guide assumptions.
Resource | Search | Read | Read Version | Instance History | Resource History | Validate | Create | Update | Delete |
---|---|---|---|---|---|---|---|---|---|
DiagnosticOrder | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Supported Includes: DiagnosticOrder.subject, DiagnosticOrder.orderer, DiagnosticOrder.supportingInformation, DiagnosticOrder.specimen, DiagnosticOrder.uslabcc
Mode: Client
The following conformance rules assumes the USLabOrder Orderer is the client, in other words, operating in 'Push' RESTful interface. The USLabOrder Orderer MUST support querying one or more resources outlined by the USLabOrder Guide. The USLabOrder Orderer MUST use all the vocabularies and value set constraints defined by the individual resource profiles used by USLabOrder. The USLabOrder Orderer MUST implement REST behavior according to the FHIR specification and MUST be able to handle errors gracefully from Query Responders who may not support the submitted query.
Security:
Implementations must meet the security requirements documented in the USLabOrder Guide assumptions.
Resource | Search | Read | Read Version | Instance History | Resource History | Validate | Create | Update | Delete |
---|---|---|---|---|---|---|---|---|---|
DiagnosticOrder | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Supported Includes: DiagnosticOrder.subject, DiagnosticOrder.orderer, DiagnosticOrder.supportingInformation, DiagnosticOrder.specimen, DiagnosticOrder.uslabcc
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.