{
"description": "When the Registry periodic submission upload would exceed timeout limits or \\nis requested as an [NDJSON](https://www.hl7.org/fhir/nd-json.html) file, use of this Upload operation is suggested.\\n See the FHIR [Asynchronous API](https://www.hl7.org/fhir/async.html) for more details on asynchronous FHIR exchange.",
"_filename": "OperationDefinition-RegistryUpload.json",
"package_name": "hl7.fhir.us.registry",
"date": "2023-11-14T18:51:51+00:00",
"system": true,
"publisher": "HL7 International / 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": "The Registry Upload of NDJSON data",
"package_version": "protocols-1.0.0",
"extension": [ {
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode": "cic"
} ],
"status": "active",
"id": "b7aca964-e688-4355-9482-947d8f5e3695",
"resource": [ "Binary" ],
"kind": "operation",
"url": "http://hl7.org/fhir/us/registry-protocols/OperationDefinition/RegistryUpload",
"code": "registryUpload",
"version": "1.0.0",
"contact": [ {
"telecom": [ {
"value": "http://www.hl7.org/Special/committees/cic",
"system": "url"
} ]
}, {
"telecom": [ {
"value": "cic@lists.hl7.org",
"system": "email"
} ]
}, {
"name": "Clinical Interoperability Council",
"telecom": [ {
"value": "http://www.hl7.org/Special/committees/cic",
"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."
} ]
}