Verduidelijken functionele kwalificatiescripts PDFA m.b.t. Binary endpoint
Description
Verduidelijking van Impact
Proposed solution (NL)
In PDF/A kwalificatiescript beschikbaarstellen onderaan sectie 1.2 toevoegen van extra notitie dat 1.4 en 2.4 of 2.5 gedaan moet worden.
Dit kan buiten de september release om aangepast worden in het script voor kwalificatie.
Proposed solution (EN)
Release notes (NL)
Release notes (EN)
is related to
Activity
Vincent Goris October 13, 2020 at 12:36 PM
Notitie toegevoegd en gepubliceerd, dit ticket kan worden gesloten.
Vincent Goris September 2, 2020 at 12:50 PM
Voorstel:
The Document Responder shall process the query to discover the DocumentReference or DocumentManifest entries that match the search parameters given. The Document Responder returns an HTTP Status code appropriate to the processing as well as a Bundle including the matching DocumentReference or DocumentManifest Resources.
The Document Responder shall place into the 'DocumentReference.content.attachment.url' element a full URL that can be used by the Document Consumer to retrieve the document using Retrieve Document transaction.
The Document Responder shall only include references which are resolved through the Document Responder to maintain control over the authentication and authorization. The Document Responder shall only serve DocumentReference or DocumentManifest resources that contain a reference which the Document Consumer may resolve.
The Document Responder shall return only PDF/A documents and shall place into the 'DocumentReference.content.attachment.contentType' element the value 'application/pdf'.
The 'DocumentReference.content.attachment.url' can reference to either a Binary resource or another location that is not a Binary endpoint.
--> laatste bullet point toegevoegd
3.3.2.2 Response Message
The Document Responder shall process the request message. The Document Responder returns an HTTP Status code appropriate to the processing as well as the content of the requested PDF/A document in the HTTP message-body.
The document may be placed inside a FHIR Binary resource if it is useful to handle pure binary content using the same framework as other resources. Binary resources behave slightly differently from all other resources on the RESTful API. Specifically, when a read request is made for the binary resource that doesn't explicitly specify the FHIR content types "application/fhir+xml" or "application/fhir+json", then the content should be returned using the content type stated in the resource. e.g. if the content type in the resource is "application/pdf", then the content should be returned as a PDF directly.[[2]|http://hl7.org/fhir/STU3/binary.html#rest]
The Document Responder is not required to place the document in a Binary resource. For qualification in MedMij, a Document Responder (XIS) is required to qualify through either supplying a PDF/A document through a Binary endpoint or through a non Binary endpoint (both is allowed as well). The qualification materials provide further information on which scenarios are required for either method of supplying a PDF/A document.
--> laatste alinea toegevoegd
Ardon Toonstra July 31, 2020 at 8:59 AM
Dit issue werd duidelijk na overleg met en .
Vanuit de functionele kwalificatiescripts wordt het niet duidelijk dat er door de server gekozen mag worden om de PDFA documenten beschikbaar te stellen van een Binary of een non-binanry endpoint.
Relevant stuk spec: https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2019.01_FHIR_PDFA#Retrieve_PDF.2FA_document
Betreft scenario's 1.4 of 2.5 .