STU 3 Candidate
This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions 
USLabOrder Receiver
{
"resourceType": "Conformance",
"id": "conformance-uslaborder-receiver",
"text": {
"status": "generated",
"div": "<div>\n\t\t\t\n <h2>USLabOrder Receiver</h2>\n\t\t\t\n <p>(Requirements Definition)</p>\n\t\t\t\n <p>Published: 2014-12-02 (draft)</p>\n\t\t\t\n <p>Published by: \n <b>\n\t\t\t\t\t\n <a href=\"http://www.hl7.org/\">HL7 Orders and Observation Workgroup</a>\n\t\t\t\t\n </b> Primary Author: Eric Haas Health eData Inc\n\t\t\t\t\n </p>\n\t\t\t\n <p>This profile defines the expected capabilities of the USLabOrder Receiver actor when conforming to the \n <a href=\"uslaborder.html\">The US Receiver Order Implementation (USLabOrder)</a>. This actor is the recipient/filler of a laboratory test order request 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.\n </p>\n\t\t\t\n <h2>General</h2>\n\t\t\t\n <table>\n\t\t\t\t\n <tbody>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>FHIR Version:</th>\n\t\t\t\t\t\t\n <td>0.8</td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>Supported formats:</th>\n\t\t\t\t\t\t\n <td>xml, json</td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\n </tbody>\n\t\t\t\n </table>\n\t\t\t\n <h2>REST behavior</h2>\n\t\t\t\n <p>\n\t\t\t\t\n <b>Mode:</b> Server\n\t\t\t\n </p>\n\t\t\t\n <p>This conformance resource assumes the USLabOrder Receiver is the server, in other words, operating in 'Pull' or 'Push/Pull' RESTful interface. The USLabOrder Receiver MUST support querying one or more resources outlined by the \n <a href=\"uslaborder-guide.html\">USLabOrder Guide</a>. The USLabOrder Receiver MUST use all the vocabularies and value set constraints defined by the individual resource profiles used by USLabOrder. The USLabOrder Receiver MUST implement REST behavior according to the \n <a href=\"../http.html\">FHIR specification</a> and MUST be able to handle errors gracefully from Query Responders who may not support the submitted query.\n </p>\n\t\t\t\n <p>\n\t\t\t\t\n <b>Security:</b>\n\t\t\t\n </p>\n\t\t\t\n <p>Implementations must meet the security requirements documented in the \n <a href=\"uslaborder-guide.html#assumptions\">USLabOrder Guide assumptions</a>.\n </p>\n\t\t\t\n <h3>Summary</h3>\n\t\t\t\n <table class=\"grid\">\n\t\t\t\t\n <thead>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>Resource</th>\n\t\t\t\t\t\t\n <th>Search</th>\n\t\t\t\t\t\t\n <th>Read</th>\n\t\t\t\t\t\t\n <th>Read Version</th>\n\t\t\t\t\t\t\n <th>Instance History</th>\n\t\t\t\t\t\t\n <th>Resource History</th>\n\t\t\t\t\t\t\n <th>Validate</th>\n\t\t\t\t\t\t\n <th>Create</th>\n\t\t\t\t\t\t\n <th>Update</th>\n\t\t\t\t\t\t\n <th>Delete</th>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\n </thead>\n\t\t\t\t\n <tbody>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>DiagnosticOrder</th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows a user to search for existing DiagnosticOrder\" href=\"#DiagnosticOrder-search-type\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows retrieval of a specific known DiagnosticOrder\" href=\"#DiagnosticOrder-read\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows retrieval of a specific version of a DiagnosticOrder\" href=\"#DiagnosticOrder-vread\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows review of changes to a DiagnosticOrder over time\" href=\"#DiagnosticOrder-history-instance\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td/>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows a client to verify whether a particular new DiagnosticOrder or revision of an existing DiagnosticOrder would be accepted based on validation and other business rules. Useful for some workflows\" href=\"#DiagnosticOrder-validate\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows defining a new DiagnosticOrder\" href=\"#DiagnosticOrder-create\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows editing of an existing DiagnosticOrder. Servers may choose to prohibit certain types of edits, instead requiring the creation of a new DiagnosticOrder (and potentially the retiring of the existing DiagnosticOrder). Servers may also limit who can change particular DiagnosticOrder.\" href=\"#DiagnosticOrder-update\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td/>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\n </tbody>\n\t\t\t\n </table>\n\t\t\t\n <br/>\n\t\t\t\n <br/>\n\t\t\t\n <h3>\n\t\t\t\t\n <a href=\"../diagnosticorder.html\">DiagnosticOrder</a>\n\t\t\t\n </h3>\n\t\t\t\n <h4>Interactions</h4>\n\t\t\t\n <table class=\"list\">\n\t\t\t\t\n <thead>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>Name</th>\n\t\t\t\t\t\t\n <th>Description</th>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\n </thead>\n\t\t\t\t\n <tbody>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticOrder-search-type\"> </a>\n\t\t\t\t\t\t\t\n <span>search-type</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows a user to search for existing DiagnosticOrder</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticOrder-read\"> </a>\n\t\t\t\t\t\t\t\n <span>read</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows retrieval of a specific known DiagnosticOrder</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticOrder-vread\"> </a>\n\t\t\t\t\t\t\t\n <span>vread</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows retrieval of a specific version of a DiagnosticOrder</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticOrder-history-instance\"> </a>\n\t\t\t\t\t\t\t\n <span>history-instance</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows review of changes to a DiagnosticOrder over time</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticOrder-create\"> </a>\n\t\t\t\t\t\t\t\n <span>create</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows defining a new DiagnosticOrder</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticOrder-update\"> </a>\n\t\t\t\t\t\t\t\n <span>update</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows editing of an existing DiagnosticOrder. Servers may choose to prohibit certain types of edits, instead requiring the creation of a new DiagnosticOrder (and potentially the retiring of the existing DiagnosticOrder). Servers may also limit who can change particular DiagnosticOrder.</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticOrder-validate\"> </a>\n\t\t\t\t\t\t\t\n <span>validate</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows a client to verify whether a particular new DiagnosticOrder or revision of an existing DiagnosticOrder would be accepted based on validation and other business rules. Useful for some workflows</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\n </tbody>\n\t\t\t\n </table>\n\t\t\t\n <h4>Search</h4>\n\t\t\t\n <p>Supported Includes: DiagnosticOrder.subject, DiagnosticOrder.orderer, DiagnosticOrder.supportingInformation, DiagnosticOrder.specimen, DiagnosticOrder.uslabcc</p>\n\t\t\t\n <h2>REST behavior</h2>\n\t\t\t\n <p>\n\t\t\t\t\n <b>Mode:</b> Client\n\t\t\t\n </p>\n\t\t\t\n <p>The following conformance rules assumes the USLabOrder Receiver is the client, in other words, operating in 'Push' RESTful interface. The USLabOrder Receiver MUST support querying one or more resources outlined by the \n <a href=\"uslaborder.html\">USLabOrder Guide</a>. The USLabOrder Receiver MUST use all the vocabularies and value set constraints defined by the individual resource profiles used by USLabOrder. The USLabOrder Receiver MUST implement REST behavior according to the \n <a href=\"../http.html\">FHIR specification</a> and MUST be able to handle errors gracefully from Query Responders who may not support the submitted query.\n </p>\n\t\t\t\n <p>\n\t\t\t\t\n <b>Security:</b>\n\t\t\t\n </p>\n\t\t\t\n <p>Implementations must meet the security requirements documented in the \n <a href=\"uslaborder.html\">USLabOrder Guide assumptions</a>.\n </p>\n\t\t\t\n <h3>Summary</h3>\n\t\t\t\n <table class=\"grid\">\n\t\t\t\t\n <thead>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>Resource</th>\n\t\t\t\t\t\t\n <th>Search</th>\n\t\t\t\t\t\t\n <th>Read</th>\n\t\t\t\t\t\t\n <th>Read Version</th>\n\t\t\t\t\t\t\n <th>Instance History</th>\n\t\t\t\t\t\t\n <th>Resource History</th>\n\t\t\t\t\t\t\n <th>Validate</th>\n\t\t\t\t\t\t\n <th>Create</th>\n\t\t\t\t\t\t\n <th>Update</th>\n\t\t\t\t\t\t\n <th>Delete</th>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\n </thead>\n\t\t\t\t\n <tbody>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>DiagnosticOrder</th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows a user to search for existing DiagnosticOrder\" href=\"#DiagnosticOrder-search-type\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows retrieval of a specific known DiagnosticOrder\" href=\"#DiagnosticOrder-read\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows retrieval of a specific version of a DiagnosticOrder\" href=\"#DiagnosticOrder-vread\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows review of changes to a DiagnosticOrder over time\" href=\"#DiagnosticOrder-history-instance\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td/>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows a client to verify whether a particular new DiagnosticOrder or revision of an existing DiagnosticOrder would be accepted based on validation and other business rules. Useful for some workflows\" href=\"#DiagnosticOrder-validate\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows defining a new DiagnosticOrder\" href=\"#DiagnosticOrder-create\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <a title=\"Allows editing of an existing DiagnosticOrder. Servers may choose to prohibit certain types of edits, instead requiring the creation of a new DiagnosticOrder (and potentially the retiring of the existing DiagnosticOrder). Servers may also limit who can change particular DiagnosticOrder.\" href=\"#DiagnosticOrder-update\">Yes</a>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\t\n <td/>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\n </tbody>\n\t\t\t\n </table>\n\t\t\t\n <br/>\n\t\t\t\n <br/>\n\t\t\t\n <h3>\n\t\t\t\t\n <a href=\"../diagnosticorder.html\">DiagnosticOrder</a>\n\t\t\t\n </h3>\n\t\t\t\n <h4>Interactions</h4>\n\t\t\t\n <table class=\"list\">\n\t\t\t\t\n <thead>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>Name</th>\n\t\t\t\t\t\t\n <th>Description</th>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\n </thead>\n\t\t\t\t\n <tbody>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticOrder-search-type\"> </a>\n\t\t\t\t\t\t\t\n <span>search-type</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows a user to search for existing DiagnosticOrder</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticOrder-read\"> </a>\n\t\t\t\t\t\t\t\n <span>read</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows retrieval of a specific known DiagnosticOrder</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticOrder-vread\"> </a>\n\t\t\t\t\t\t\t\n <span>vread</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows retrieval of a specific version of a DiagnosticOrder</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticOrder-history-instance\"> </a>\n\t\t\t\t\t\t\t\n <span>history-instance</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows review of changes to a DiagnosticOrder over time</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticOrder-create\"> </a>\n\t\t\t\t\t\t\t\n <span>create</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows defining a new DiagnosticOrder</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticOrder-update\"> </a>\n\t\t\t\t\t\t\t\n <span>update</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows editing of an existing DiagnosticOrder. Servers may choose to prohibit certain types of edits, instead requiring the creation of a new DiagnosticOrder (and potentially the retiring of the existing DiagnosticOrder). Servers may also limit who can change particular DiagnosticOrder.</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\t\n <tr>\n\t\t\t\t\t\t\n <th>\n\t\t\t\t\t\t\t\n <a name=\"DiagnosticOrder-validate\"> </a>\n\t\t\t\t\t\t\t\n <span>validate</span>\n\t\t\t\t\t\t\n </th>\n\t\t\t\t\t\t\n <td>\n\t\t\t\t\t\t\t\n <p>Allows a client to verify whether a particular new DiagnosticOrder or revision of an existing DiagnosticOrder would be accepted based on validation and other business rules. Useful for some workflows</p>\n\t\t\t\t\t\t\n </td>\n\t\t\t\t\t\n </tr>\n\t\t\t\t\n </tbody>\n\t\t\t\n </table>\n\t\t\t\n <h4>Search</h4>\n\t\t\t\n <p>Supported Includes: DiagnosticOrder.subject, DiagnosticOrder.orderer, DiagnosticOrder.supportingInformation, DiagnosticOrder.specimen, DiagnosticOrder.uslabcc</p>\n\t\t\n </div>"
},
"name": "USLabOrder Receiver",
"_name": {
"fhir_comments": [
" EH: this is the SDC template for conformance examples which I will run to generate the text "
]
},
"status": "draft",
"date": "2014-12-02",
"publisher": "Published by: HL7 Orders and Observation Workgroup. Primary Author: Eric Haas Health eData Inc",
"contact": [
{
"telecom": [
{
"system": "other",
"value": "http://www.hl7.org/"
}
]
}
],
"description": "This profile defines the expected capabilities of the USLabOrder Receiver actor when conforming to the [[uslaborder.html|The US Receiver Order Implementation (USLabOrder)]]. This actor is the recipient/filler of a laboratory test order request 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.",
"kind": "requirements",
"fhirVersion": "1.0.0",
"acceptUnknown": "extensions",
"format": [
"xml",
"json"
],
"rest": [
{
"fhir_comments": [
" EH: need to distinguish when laboratory in server mode = Pull: The source is a server, and the destination is a client. When the client wants to use the data, it uses a combination of search and read so the users can find the data they need\nPush/Pull: The source is a server, and the destination is a client. On a regular basis, the destination queries the server for its history, and replicates the changes in its own copy of the database\n...\nor when laboratory in client mode =Push: The source is a client, and when new data is available, it uses create, update, and transaction to push data to the destination, which is a server "
],
"mode": "server",
"documentation": "This conformance resource assumes the USLabOrder Receiver is the server, in other words, operating in 'Pull' or 'Push/Pull' RESTful interface. The USLabOrder Receiver MUST support querying one or more resources outlined by the [[uslaborder|USLabOrder Guide]]. The USLabOrder Receiver MUST use all the vocabularies and value set constraints defined by the individual resource profiles used by USLabOrder. The USLabOrder Receiver MUST implement REST behavior according to the [[http|FHIR specification]] and MUST be able to handle errors gracefully from Query Responders who may not support the submitted query.",
"security": {
"description": "Implementations must meet the security requirements documented in the [[uslaborder|USLabOrder Guide assumptions]]."
},
"resource": [
{
"type": "DiagnosticOrder",
"profile": {
"reference": "StructureDefinition/do-uslab"
},
"interaction": [
{
"code": "search-type",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows a user to search for existing DiagnosticOrder"
},
{
"code": "read",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows retrieval of a specific known DiagnosticOrder"
},
{
"code": "vread",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows retrieval of a specific version of a DiagnosticOrder"
},
{
"code": "history-instance",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows review of changes to a DiagnosticOrder over time"
},
{
"code": "create",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows defining a new DiagnosticOrder"
},
{
"code": "update",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows editing of an existing DiagnosticOrder. Servers may choose to prohibit certain types of edits, instead requiring the creation of a new DiagnosticOrder (and potentially the retiring of the existing DiagnosticOrder). Servers may also limit who can change particular DiagnosticOrder."
}
],
"searchInclude": [
"DiagnosticOrder.subject, DiagnosticOrder.orderer, DiagnosticOrder.supportingInformation, DiagnosticOrder.specimen, DiagnosticOrder.uslabcc"
],
"_searchInclude": [
{
"fhir_comments": [
" interaction>\n EH: comment out for now since deleting is probably not allowed <extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"MAY\"/>\n </extension>\n <code value=\"delete\"/>\n <documentation value=\"Allows removal of an existing DiagnosticOrder. Servers may choose to not support deletions or may limit deletions to DiagnosticOrder meeting certain requirements. E.g. only elements with a status of draft or only elements that have been retired for at least two years, etc.\"/>\n </interaction ",
" EH flags for support for versioning, read history, update create\n\t\t<versioning value=\"versioned|no-version\" "
]
}
]
}
]
},
{
"fhir_comments": [
" EH: comment out for now\n\t\t<searchParam ",
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension ",
" name value=\"category\"/>\n <definition value=\"http://hl7.org/fhir/StructureDefinition/dataelement#category\"/>\n <type value=\"token\"/>\n </searchParam>\n <searchParam ",
" interaction. operation "
],
"mode": "client",
"documentation": "The following conformance rules assumes the USLabOrder Receiver is the client, in other words, operating in 'Push' RESTful interface. The USLabOrder Receiver MUST support querying one or more resources outlined by the [[uslaborder|USLabOrder Guide]]. The USLabOrder Receiver MUST use all the vocabularies and value set constraints defined by the individual resource profiles used by USLabOrder. The USLabOrder Receiver MUST implement REST behavior according to the [[http|FHIR specification]] and MUST be able to handle errors gracefully from Query Responders who may not support the submitted query.",
"security": {
"description": "Implementations must meet the security requirements documented in the [[uslaborder|USLabOrder Guide assumptions]]."
},
"resource": [
{
"type": "DiagnosticOrder",
"profile": {
"reference": "StructureDefinition/do-uslab"
},
"interaction": [
{
"code": "search-type",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows a user to search for existing DiagnosticOrder"
},
{
"code": "read",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows retrieval of a specific known DiagnosticOrder"
},
{
"code": "vread",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows retrieval of a specific version of a DiagnosticOrder"
},
{
"code": "history-instance",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows review of changes to a DiagnosticOrder over time"
},
{
"code": "create",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows defining a new DiagnosticOrder"
},
{
"code": "update",
"_code": {
"fhir_comments": [
" EH: comment out for now extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"SHALL\"/>\n </extension "
]
},
"documentation": "Allows editing of an existing DiagnosticOrder. Servers may choose to prohibit certain types of edits, instead requiring the creation of a new DiagnosticOrder (and potentially the retiring of the existing DiagnosticOrder). Servers may also limit who can change particular DiagnosticOrder."
}
],
"searchInclude": [
"DiagnosticOrder.subject, DiagnosticOrder.orderer, DiagnosticOrder.supportingInformation, DiagnosticOrder.specimen, DiagnosticOrder.uslabcc"
],
"_searchInclude": [
{
"fhir_comments": [
" interaction>\n EH: comment out for now since deleting is probably not allowed <extension url=\"http://hl7.org/fhir/StructureDefinition/conformance-expectation\">\n <valueCode value=\"MAY\"/>\n </extension>\n <code value=\"delete\"/>\n <documentation value=\"Allows removal of an existing DiagnosticOrder. Servers may choose to not support deletions or may limit deletions to DiagnosticOrder meeting certain requirements. E.g. only elements with a status of draft or only elements that have been retired for at least two years, etc.\"/>\n </interaction ",
" EH flags for support for versioning, read history, update create\n\t\t<versioning value=\"versioned|no-version\" "
]
}
]
}
]
}
]
}
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.
© HL7.org 2011+. FHIR STU3 Candidate (v1.4.0-8139) generated on Thu, Mar 31, 2016 08:08+1100. QA Page
Links: Search |
Version History |
Table of Contents |
Compare to DSTU2 |
|
Propose a change