Conformance-uslabreport-sender.json

USLabReport Sender

{
  "resourceType": "Conformance",
  "id": "uslabreport-sender",
  "text": {
    "status": "generated",
    "div": "<div>!-- Snipped for Brevity --></div>"
  },
  "name": "USLabReport Sender",
  "publisher": "Published by: HL7 Orders and Observation Workgroup. Primary Author: Eric Haas  Health eData Inc",
  "contact": [
    {
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/"
        }
      ]
    }
  ],
  "description": "This profile defines the expected capabilities of the USLabReport Sender actor when conforming to the [[uslabreport.html|The US Sender Report Implementation (USLabReport)]].  This actor is the source of a laboratory test order report 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 USLabReport guide.",
  "status": "draft",
  "date": "2014-12-02",
  "fhirVersion": "0.8",
  "acceptUnknown": false,
  "format": [
    "xml",
    "json"
  ],
  "rest": [
    {
      "mode": "server",
      "documentation": "This conformance resource assumes the USLabReport Sender is the server, in other words, operating in 'Pull'  or 'Push/Pull' RESTful interface.  The USLabReport Sender MUST support querying one or more resources outlined by the [[uslabreport|USLabReport Guide]]. The USLabReport Sender MUST use all the vocabularies and value set constraints defined by the individual resource profiles used by USLabReport. The USLabReport Sender 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 [[uslabreport|USLabReport Guide assumptions]]."
      },
      "resource": [
        {
          "type": "DiagnosticReport",
          "profile": {
            "reference": "dr-uslab"
          },
          "interaction": [
            {
              "code": "search-type",
              "documentation": "Allows a user to search for existing DiagnosticReport"
            },
            {
              "code": "read",
              "documentation": "Allows retrieval of a specific known DiagnosticReport"
            },
            {
              "code": "vread",
              "documentation": "Allows retrieval of a specific version of a DiagnosticReport"
            },
            {
              "code": "history-instance",
              "documentation": "Allows review of changes to a DiagnosticReport over time"
            },
            {
              "code": "create",
              "documentation": "Allows defining a new DiagnosticReport"
            },
            {
              "code": "update",
              "documentation": "Allows editing of an existing DiagnosticReport.  Servers may choose to prohibit certain types of edits, instead requiring the creation of a new DiagnosticReport (and potentially the retiring of the existing DiagnosticReport).  Servers may also limit who can change particular DiagnosticReport."
            },
            {
              "code": "validate",
              "documentation": "Allows a client to verify whether a particular new DiagnosticReport or revision of an existing DiagnosticReport would be accepted based on validation and other business rules.  Useful for some workflows"
            }
          ],
          "searchInclude": [
            "DiagnosticReport.subject, DiagnosticReport.performer, DiagnosticReport.requestDetail, DiagnosticReport.specimen, DiagnosticReport.report"
          ]
        }
      ]
    },
    {
      "mode": "client",
      "documentation": "The following conformance rules assumes the USLabReport Sender is the client, in other words, operating in 'Push'  RESTful interface.  The USLabReport Sender MUST support querying one or more resources outlined by the [[uslabreport|USLabReport Guide]]. The USLabReport Sender MUST use all the vocabularies and value set constraints defined by the individual resource profiles used by USLabReport. The USLabReport Sender 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 [[uslabreport|USLabReport Guide assumptions]]."
      },
      "resource": [
        {
          "type": "DiagnosticReport",
          "profile": {
            "reference": "do-uslab"
          },
          "interaction": [
            {
              "code": "search-type",
              "documentation": "Allows a user to search for existing DiagnosticReport"
            },
            {
              "code": "read",
              "documentation": "Allows retrieval of a specific known DiagnosticReport"
            },
            {
              "code": "vread",
              "documentation": "Allows retrieval of a specific version of a DiagnosticReport"
            },
            {
              "code": "history-instance",
              "documentation": "Allows review of changes to a DiagnosticReport over time"
            },
            {
              "code": "create",
              "documentation": "Allows defining a new DiagnosticReport"
            },
            {
              "code": "update",
              "documentation": "Allows editing of an existing DiagnosticReport.  Servers may choose to prohibit certain types of edits, instead requiring the creation of a new DiagnosticReport (and potentially the retiring of the existing DiagnosticReport).  Servers may also limit who can change particular DiagnosticReport."
            },
            {
              "code": "validate",
              "documentation": "Allows a client to verify whether a particular new DiagnosticReport or revision of an existing DiagnosticReport would be accepted based on validation and other business rules.  Useful for some workflows"
            }
          ],
          "searchInclude": [
            "DiagnosticReport.subject, DiagnosticReport.performer, DiagnosticReport.requestDetail, DiagnosticReport.specimen, DiagnosticReport.report"
          ]
        }
      ]
    }
  ]
}