{
  "description": null,
  "_filename": "OperationDefinition-RegistryUpload.json",
  "package_name": "hl7.fhir.us.registry-protocols",
  "date": "2023-03-29T01:19:33+00:00",
  "system": true,
  "publisher": "Clinical Interoperability Council",
  "instance": false,
  "jurisdiction": [ {
    "coding": [ {
      "code": "US",
      "system": "urn:iso:std:iso:3166",
      "display": "United States of America"
    } ]
  } ],
  "name": "RegistryUpload",
  "type": "false",
  "experimental": null,
  "resourceType": "OperationDefinition",
  "title": null,
  "package_version": "1.0.0-ballot",
  "status": "active",
  "id": "18efa0ab-6049-4035-91ae-fbc83afaac6d",
  "resource": [ "Binary" ],
  "kind": "operation",
  "url": "http://hl7.org/fhir/us/registry-protocols/OperationDefinition/RegistryUpload",
  "code": "registryUpload",
  "version": "1.0.0-ballot",
  "contact": [ {
    "telecom": [ {
      "value": "http://hl7.org/Special/committees/cic",
      "system": "url"
    } ]
  }, {
    "telecom": [ {
      "value": "cic@lists.hl7.org",
      "system": "email"
    } ]
  }, {
    "name": "Clinical Interoperability Council",
    "telecom": [ {
      "value": "http://hl7.org/Special/committees/cic/index.cfm",
      "system": "url"
    } ]
  }, {
    "name": "David Pyke",
    "telecom": [ {
      "value": "mailto:David.Pyke@pointclickcare.com",
      "system": "email"
    } ]
  } ],
  "parameter": [ {
    "max": "1",
    "min": 1,
    "use": "in",
    "name": "input",
    "type": "Binary",
    "documentation": "The POST will be Binary resource consisting of the contentType element listing the mime type of\n  application/fhir+ndjson and the data element consisting of a NDJSON file. Each line of the NDJSON file will comprising a \n  single patient Submission Bundle.\n  The http POST will have: \n  1. the Prefer header set to respond-async and \n  2. the Accept header set to the application/fhir+ndjson format"
  }, {
    "max": "1",
    "min": 1,
    "use": "out",
    "name": "output",
    "type": "OperationOutcome",
    "documentation": "The optionally attached OperationOutcome will solely be the result of the validation that the submission file is a valid NDJSON file\n  and will not have information regarding the content sumbitted.\n  The result of a successful submission will be a 202 Accepted with the Content-Location pointing to a polling \n  location of the NDJSON file of OperationOutcomes. \n  Each OperationOutcome in the fetched NDJSON file will give the results of a validation exercise \n  for the individual lines within the submission file."
  } ]
}