MedMij:Vissue-MM-3500/FHIR PDFA - Bewerkingsoverzicht

Luud Slagter: /* List of profiles */

2022-09-09T08:07:26Z

List of profiles

← Oudere versie		Versie van 9 sep 2022 08:07
Regel 406:		Regel 406:
	\| style="background-color: white;"\| {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/IHE.MHD.List\|nictiz.fhir.nl.stu3.zib2017}}		\| style="background-color: white;"\| {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/IHE.MHD.List\|nictiz.fhir.nl.stu3.zib2017}}
	\|}		\|}

			{{IssueBox\|Even though the table above contains all profiles based on IHE MHD applicable to this use case, both the Bundle and List profiles aren't explicitly used within the PDF/A information standard, and are merely listed for completeness purposes.}}

	=Release notes=		=Release notes=
	Release notes can be found on the [[MedMij:Vprepub-2020.01/OntwerpPDFA#Release_notes\| functional design page]].		Release notes can be found on the [[MedMij:Vprepub-2020.01/OntwerpPDFA#Release_notes\| functional design page]].

Luud Slagter: /* List of profiles */

2022-09-09T07:41:43Z

List of profiles

← Oudere versie		Versie van 9 sep 2022 07:41
Regel 262:		Regel 262:
	IHE has defined profiles and other conformance resources applicable to this use case. The FHIR Implementation Guide on the '''[http://wiki.ihe.net/index.php/Mobile_access_to_Health_Documents_(MHD)#FHIR_Implementation_Guide IHE MHD wiki]''' lists these conformance resources.		IHE has defined profiles and other conformance resources applicable to this use case. The FHIR Implementation Guide on the '''[http://wiki.ihe.net/index.php/Mobile_access_to_Health_Documents_(MHD)#FHIR_Implementation_Guide IHE MHD wiki]''' lists these conformance resources.

	Due to errors encountered when creating the send use case, that IHE did not intend to fix in STU3, Nictiz has fixed the errors and re-published the IHE.MHD profiles in the Nictiz namespace. Note that IHE originally created two profiles, one for Query DocumentReference and one for Provide DocumentReference which are identical to ~~eachother~~. For usability purposes, these two profiles have been merged.		Due to errors encountered when creating the send use case, that IHE did not intend to fix in STU3, Nictiz has fixed the errors and re-published the IHE.MHD profiles in the Nictiz namespace. Note that IHE originally created two profiles, one for Query DocumentReference and one for Provide DocumentReference which are identical to each other. For usability purposes, these two profiles have been merged.

	Find and retrieve existing PDF/A document transaction uses the following profiles:		Find and retrieve existing PDF/A document transaction uses the following profiles:
Regel 269:		Regel 269:
	* DocumentManifest (canonical URL {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/IHE.MHD.DocumentManifest\|nictiz.fhir.nl.stu3.zib2017}})		* DocumentManifest (canonical URL {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/IHE.MHD.DocumentManifest\|nictiz.fhir.nl.stu3.zib2017}})

	{{IssueBox\|The IHE profiles restrict the use of the .created element. This is a known issue and will be addressed in the R4 release of the profiles. This issue (CP-ITI-1100) can be found on the [http://wiki.ihe.net/index.php/Mobile_access_to_Health_Documents_(MHD)#FHIR_Implementation_Guide IHE MHD wiki]. Therefore the indexed element is used to capture creation time.}}		{{IssueBox\|The IHE profiles restrict the use of the .created element. This is a known issue and will be addressed in the R4 release of the profiles. This issue (CP-ITI-1100) can be found on the [http://wiki.ihe.net/index.php/Mobile_access_to_Health_Documents_(MHD)#FHIR_Implementation_Guide IHE MHD wiki]. Therefore the .indexed element is used to capture creation time.}}

	The complete set of used profiles for the response message is listed in the table below.		The complete set of used profiles for the response message is listed in the table below.

Luud Slagter: /* List of profiles */

2022-09-09T07:32:34Z

List of profiles

← Oudere versie		Versie van 9 sep 2022 07:32
Regel 357:		Regel 357:
	==List of profiles==		==List of profiles==

	IHE has defined profiles applicable to this use case. Although the IHE MHD Profile text (the published PDF) is Normative these conformance resources are labelled as Informative. Not all IHE MHD profiles are implementable as-is for the send use case because of errors that IHE does not intend to resolve in FHIR STU3, but instead, require updating to FHIR R4. MedMij is not ready upgrading to FHIR R4 for just this use case and has implemented the necessary fixes in the IHE FHIR STU3 profiles to support this use case. The IHE MHD profiles 'IHE.MHD.DocumentManifest' and 'IHE.MHD.ProvideDocumentBundle~~.Minimal~~' are therefore copied, adjusted for the known issues and released in the Nictiz namespace. The table below shows the IHE MHD profiles used for the Providing Document Bundle transaction and the relevant HCIM profiles. Note that IHE originally created two profiles on DocumentReference, one for Query DocumentReference and one for Provide DocumentReference which are identical to ~~eachother~~. For usability purposes, these two profiles have been merged.		IHE has defined profiles applicable to this use case. Although the IHE MHD Profile text (the published PDF) is Normative these conformance resources are labelled as Informative. Not all IHE MHD profiles are implementable as-is for the send use case because of errors that IHE does not intend to resolve in FHIR STU3, but instead, require updating to FHIR R4. MedMij is not ready upgrading to FHIR R4 for just this use case and has implemented the necessary fixes in the IHE FHIR STU3 profiles to support this use case. The IHE MHD profiles 'IHE.MHD.DocumentManifest' and 'IHE.MHD.Minimal.ProvideDocumentBundle' are therefore copied, adjusted for the known issues and released in the Nictiz namespace. The table below shows the IHE MHD profiles used for the Providing Document Bundle transaction and the relevant HCIM profiles. Note that IHE originally created two profiles on DocumentReference, one for Query DocumentReference and one for Provide DocumentReference which are identical to each other. For usability purposes, these two profiles have been merged.

	{{MedMij:Vprepub-2020.01/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}		{{MedMij:Vprepub-2020.01/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}

Luud Slagter: Clone of V2020.01 production page for issue MM-3500

2022-09-09T07:10:47Z

Clone of V2020.01 production page for issue MM-3500

Nieuwe pagina

{{IssuePaginaWaarschuwing|MM-3500|MedMij:V2020.01/FHIR_PDFA}}
__NOINDEX__
__NUMBEREDHEADINGS__
{{DISPLAYTITLE:MedMij FHIR Implementation Guide: PDF/A {{VersieInfo|PDFA}}}}
{{MedMij:Vprepub-2020.01/Issuebox_FHIR_IG}}

[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]
[[Bestand:PDF-A_icoon.png|link=|87px |links||PDF/A]]
<imagemap>Bestand:Leeswijzer-technisch-banner 03 white.png|center|400px|alt=Afspraken-Functioneel-Technisch
circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
circle 1013 224 212 [[MedMij:Vprepub-2020.01/OntwerpPDFA|Functioneel]]
circle 1787 230 212 [[MedMij:Vprepub-2020.01/FHIR_IG|Technisch]]
desc none
</imagemap>

__TOC__

=Introduction=
[[Bestand:Functioneel-02.png|link=MedMij:Vprepub-2020.01/Ontwerpen |100px|rechts|Functional design|Go to functional design]]
MedMij specifies the format [http://www.pdfa.org/publication/pdfa-in-a-nutshell-2-0/ PDF/A] for exchanging unstructured documents containing health information. Forum Standaardisatie is a Dutch governmental organization that aims to stimulate the use of open standards. PDF/A is one of the standards that is recommended by Forum Standaardisatie. More information regarding PDF/A can be found here: https://www.forumstandaardisatie.nl/standaard/pdf-nen-iso.

To achieve exchange of PDF/A files, MedMij adopts as much as possible from the Mobile access to Health Documents (MHD) profile from Integrating the Healthcare Enterprise (IHE) that defines a RESTful/HTTP interface to an [http://wiki.ihe.net/index.php/Cross-Enterprise_Document_Sharing XDS] environment using HL7 FHIR STU3 resources. The MHD profile is written to be content agnostic and as such is suitable for much more than PDF/A. For this use case, we have limited the scope to PDF/A. The next section summarizes MHD and contains references to IHE MHD specification. The following sections provides an adaptation of the MHD profile to specify exchange of PDF/A documents in a MedMij context.

When implementing PDF/A, a minimum compliance must be assumed. That is, PDF/A-1 and PDF/A-b is also permitted within this. For more information, see the wiki page on this: https://en.wikipedia.org/wiki/PDF/A#Conformance_levels_and_versions

'''Note''': This implementation guide builds on the general guidelines described in the [[MedMij:Vprepub-2020.01/FHIR_IG#Use case overarching principles|use case overarching principles]].

===IHE MHD specification===
Mobile access to Health Documents (MHD) profile defines a simple HTTP RESTful interface to an XDS like environment, based on HL7 FHIR. It describes four transactions:
# submit submission sets, folders, new documents, and document metadata from the mobile device to a document receiver (Provide Document Bundle),
# find submission sets matching query parameters (Find Document Manifest),
# find document entries containing metadata based on query parameters (Find Document Reference),
# retrieve a copy of a specific document (Retrieve Document).
These transactions leverage the document content and format agnostic metadata concepts from XDS but simplify them for access by constrained environments such as mobile devices, or other resource-constrained systems. The MHD profile does not replace XDS. It can be used to allow mobile devices, or other resource-constrained systems, access to an XDS health information exchange.[http://wiki.ihe.net/index.php/Mobile_access_to_Health_Documents_(MHD)]

'''Wiki:'''
[http://wiki.ihe.net/index.php/Mobile_access_to_Health_Documents_(MHD) Mobile acces to Health Document (MHD)]

'''Document:'''
[https://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_MHD_Rev.2.4_TI_2018-07-24.pdf MHD Supplement] (Rev 2.4 July 24, 2018)

'''Additional Supplement:'''
[https://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_Appx-Z_Rev1.2_TI_2017-07_21.pdf Appendix Z on HL7 FHIR] (Rev 1.2 July 21, 2017)

=Actors and transactions involved=
Table 1 shows the relevant actors, systems and FHIR capability statements in a MedMij context. The capability statements demonstrate the minimum requirements to be conformant to the full MHD specifications.
{| class="wikitable"
! colspan="2" style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;" | Persons
! colspan="2" style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;" | Systems
! colspan="2" style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;" | FHIR Capability Statements
|-
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;" |Name
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;" |Description
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;" |Name
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;" |Description
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;" |Name
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;" |Description
|-
| Patient
| The user of a personal healthcare environment.
| PHR
| Personal health record
|[[Bestand: Verwijzing.png| 20px]] {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/pdfa-clientcapabilities|nictiz.fhir.nl.stu3.zib2017|title=CapabilityStatement: Client}}
| PDFA FHIR Client requirements
|-
| Healthcare Provider
| The user of a XIS
| XIS
| Healthcare information system
|[[Bestand: Verwijzing.png| 20px]] {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/pdfa-servercapabilities|nictiz.fhir.nl.stu3.zib2017|title=CapabilityStatement: Server}}
| PDFA FHIR Server requirements
|}
'''Table 1. Actors, systems and FHIR capability statements'''

Table 2 shows the MHD actors and transactions in perspective of the systems used in a MedMij context.

{| class="wikitable"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;" | Person
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;" | System
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;" | MHD Actors
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;" | MHD Transactions
|-
| rowspan="6" | Patient
|-
| rowspan="5" | PHR
|-
| rowspan="3" | Document Consumer
| Find Document Manifests [ITI-66]
|-
| Find Document References [ITI-67]
|-
| Retrieve Document [ITI-68]
|-
| Document Source
| Provide Document Bundle [ITI-65]
|-
| rowspan="6" | Healthcare provider
|-
| rowspan="5" | XIS
|-
| rowspan="3" | Document Responder
| Find Document Manifests [ITI-66]
|-
| Find Document References [ITI-67]
|-
| Retrieve Document [ITI-68]
|-
| Document Recipient
| Provide Document Bundle [ITI-65]
|}

=Use case: Find and retrieve existing PDF/A document(s)=
[[Bestand:Afsprakenstelsel-01.png|link=https://www.medmij.nl/afsprakenstelsel/|rechts |100px|Go to Afsprakenstelsel]]
{{FHIR-IG-Afsprakenstelsel-Note}}

==Introduction==
This section summarizes the IHE MHD profile to find and retrieve PDF/A documents in a MedMij context.

==Actors and transactions involved==
Table 1 shows the relevant actors, systems and FHIR capability statements in a MedMij context. The capability statements demonstrate the minimum requirements to be conformant to the full MHD specifications.
{| class="wikitable"
! colspan="2" style="text-align:left;" | Persons
! colspan="2" style="text-align:left;" | Systems
! colspan="2" style="text-align:left;" | FHIR Capability Statements
|-
! style="text-align:left;" |Name
! style="text-align:left;" |Description
! style="text-align:left;" |Name
! style="text-align:left;" |Description
! style="text-align:left;" |Name
! style="text-align:left;" |Description
|-
| Patient
| The user of a personal healthcare environment.
| PHR
| Personal health record
|[[Bestand: Verwijzing.png| 20px]] {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/pdfa-clientcapabilities|nictiz.fhir.nl.stu3.zib2017|title=CapabilityStatement: Client}}
| PDFA FHIR Client requirements
|-
| Healthcare Provider
| The user of a XIS
| XIS
| Healthcare information system
|[[Bestand: Verwijzing.png| 20px]] {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/pdfa-servercapabilities|nictiz.fhir.nl.stu3.zib2017|title=CapabilityStatement: Server}}
| PDFA FHIR Server requirements
|}
'''Table 1. Actors, systems and FHIR capability statements'''

Table 2 shows the MHD actors and transactions in perspective of the systems used in a MedMij context.
{| class="wikitable"
! style="font-weight: bold; text-align:left;" | Person
! style="font-weight: bold; text-align:left;" | System
! style="font-weight: bold; text-align:left;" | MHD Actors
! style="font-weight: bold; text-align:left;" | MHD Transactions
! style="font-weight: bold; text-align:left;" | Optionallity
|-
| rowspan="5" | Patient
|-
| rowspan="4" | PHR
|-
| rowspan="3" | Document Consumer
| Find Document Manifest
| Optional
|-
| Find Document Reference
| Required
|-
| Retrieve Document
| Required
|-
| rowspan="5" | Healthcare provider
|-
| rowspan="4" | XIS
|-
| rowspan="3" | Document Responder
| Find Document Manifest
| Optional
|-
| Find Document Reference
| Required
|-
| Retrieve Document
| Required
|}
'''Table 2. MHD actors and transactions in perspective of systems in a MedMij context''' 

Implementation of the 'Find Document Reference' and 'Retrieve Document' transactions are required. The 'Find Document Manifest' transaction is optional for both the Document Consumer and Document Responder.

==Find and retrieve existing PDF/A document(s)==

===Find PDF/A or PDF/A collection===
Discovery of PDF/A documents is done with the MHD defined transaction 'Find Document Reference' or 'Find Document Manifest.' The Find Document Reference retrieves FHIR DocumentReference Resources that represents a single reference to document per resource, for example, one PDF/A file. The Find Document Manifest retrieves FHIR DocumentManifest Resources. A DocumentManifest Resource gathers a set of DocumentReference Resources into a single package together with metadata that applies to the collection.

The Document Consumer requests DocumentReference or DocumentManifest Resources, matching a set of criteria, from the Document Responder. The Document Responder returns DocumentReference or DocumentManifest Resources that match the search criteria provided by the Document Consumer.

====Request message====
'''Search'''

The Document Consumer executes an HTTP GET conform to the FHIR [http://hl7.org/fhir/http.html RESTful] and [http://hl7.org/fhir/search.html search] specification. A search query would have the following format.

<pre>
GET [base]/DocumentReference?status=[status]{&[parameters]}
GET [base]/DocumentManifest?status=[status]{&[parameters]}
</pre>

An example query to search for DocumentReferences which have status "''current''" and which are indexed/created after 01-01-2010:
<pre>GET [base]/DocumentReference?status=current&indexed=ge2010-01-01</pre>

'''Search Parameters'''
The Document Consumer shall include search parameter status. The Document Consumer may supply, and the Document Responder shall be capable of processing, all search parameters listed below. These search parameters are a selection of the defined search parameters by the IHE MHD profile. The IHE MHD profile contains more search parameters that were deemed to pose a disproportionate implemenation burden for Document Responders. The following subselection still allow Document Consumers with server-side filter capabilities while making this use case more implementable for Document Responders.

{| class="wikitable"
! colspan="3" style="font-weight: bold; text-align:left;" | DocumentReference
! colspan="3" style="font-weight: bold; text-align:left;" | DocumentManifest
|-
| style="font-weight: bold;" | Name
| style="font-weight: bold;" | Type
| style="font-weight: bold;" | Description
| style="font-weight: bold;" | Name
| style="font-weight: bold;" | Type
| style="font-weight: bold;" | Description
|-
| <code>indexed</code>
| date
| When this document reference was created
| <code>created</code>
| date
| When this document manifest created
|-
| <code>status</code>
| token
| current / superseded
| <code>status</code>
| token
| current / superseded
|}

====Response message====
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'.

===Retrieve PDF/A document===
After obtaining the location of the PDF/A document in the DocumentReference.content.attachment.url, the Document Consumer requests the document from the Document Responder. The Document Responder sequentially serves the PDF/A document to the Document Consumer. The context that was established in the initial request shall also apply when retrieving/serving the document contents.

====Request Message====
This message is an HTTP GET request to retrieve the document. See an example below.

<pre>GET http://example:9556/svc/fhir/Binary/1e404af3-077f-4bee-b7a6-a9be97e1ce32</pre>

The Document Consumer may provide an HTTP Accept header, according to the semantics of the HTTP protocols (see RFC2616, Section 14.1). The only MIME type assured to be returned is the
MIME type indicated in the 'DocumentReference.content.attachment.contentType'. Within MedMij this is set to 'application/pdf'. The HTTP If-Unmodified-Since header shall not be included in the GET request

====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 [http://hl7.org/fhir/STU3/binary.html 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.[http://hl7.org/fhir/STU3/binary.html#rest]

==List of profiles==
IHE has defined profiles and other conformance resources applicable to this use case. The FHIR Implementation Guide on the '''[http://wiki.ihe.net/index.php/Mobile_access_to_Health_Documents_(MHD)#FHIR_Implementation_Guide IHE MHD wiki]''' lists these conformance resources.

Due to errors encountered when creating the send use case, that IHE did not intend to fix in STU3, Nictiz has fixed the errors and re-published the IHE.MHD profiles in the Nictiz namespace. Note that IHE originally created two profiles, one for Query DocumentReference and one for Provide DocumentReference which are identical to eachother. For usability purposes, these two profiles have been merged.

Find and retrieve existing PDF/A document transaction uses the following profiles:

* DocumentReference from Query with Minimal Metadata (canonical URL {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/IHE.MHD.Minimal.DocumentReference|nictiz.fhir.nl.stu3.zib2017}})
* DocumentManifest (canonical URL {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/IHE.MHD.DocumentManifest|nictiz.fhir.nl.stu3.zib2017}})

{{IssueBox|The IHE profiles restrict the use of the .created element. This is a known issue and will be addressed in the R4 release of the profiles. This issue (CP-ITI-1100) can be found on the [http://wiki.ihe.net/index.php/Mobile_access_to_Health_Documents_(MHD)#FHIR_Implementation_Guide IHE MHD wiki]. Therefore the indexed element is used to capture creation time.}}

The complete set of used profiles for the response message is listed in the table below.

{{MedMij:Vprepub-2020.01/NoteBoxPackage|p1=nictiz.fhir.nl.stu3.zib2017|v1Min=2.0.0}}

{| class="wikitable" width="1400px"
|-style="background-color: #1F497D; color: white; font-weight: bold; "
|Zib name NL||Zib name EN||FHIR Resource||URL profile|
|-style="vertical-align:top; background-color: #E3E3E3;
|-
| Patient
| #Zib Patient|Patient
| Patient
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nictiz.fhir.nl.stu3.zib2017}}
|-
| Zorgverlener
| HealthProfessional
| Practitioner
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017}}
|-
| Zorgaanbieder
| HealthcareProvider
| Organization
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017}}
|-
| -
| -
| DocumentManifest
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/IHE.MHD.DocumentManifest|nictiz.fhir.nl.stu3.zib2017}}
|-
| -
| -
| DocumentReference
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/IHE.MHD.Minimal.DocumentReference|nictiz.fhir.nl.stu3.zib2017}}
|}

=Use case: Send PDF/A document(s)=

==Introduction==
[[Bestand:Afsprakenstelsel-01.png|link=https://www.medmij.nl/afsprakenstelsel/|rechts |100px|Go to Afsprakenstelsel]]
This section summarizes the IHE MHD profile to Send PDF/A document(s) in a MedMij context.

{{FHIR-IG-Afsprakenstelsel-Note}}

==Actors==
{| class="wikitable"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;" | Person
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;" | System
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;" | MHD Actors
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;" | MHD Transactions
|-
| Patient
| PHR
| Document Source
| Provide Document Bundle [ITI-65]
|-
| Healthcare provider
| XIS
| Document Recipient
| Provide Document Bundle [ITI-65]
|}

==Send PDFA==
===PHR: Request message===
When the patient (PHR) wants to send one or more PDF/A documents, it issues a send PDFA request message.

The PHR initiates a FHIR transaction using a create action by sending an HTTP POST request, composed of a FHIR Bundle resource containing one DocumentManifest resource, one or more DocumentReference resources, one or more Binary resources, one Patient resource, and zero or more Practitioner resources to the XIS recipient. References to the FHIR specification for the required transaction and POST requests are given in the [[#Interactions.2C_operations.2C_search_parameters|interactions, operations and search parameters]] section below.

The PHR executes an HTTP POST against the XIS's base endpoint as shown below.

<pre>
POST [base]
</pre>

'''Read more:'''
* [http://hl7.org/fhir/STU3/http.html#transaction transaction]
* [http://hl7.org/fhir/STU3/http.html#create create]

===XIS: Response message===
The target XIS returns an HTTP Status code appropriate to the processing outcome and returns a Bundle, of type transaction-response, that contains one entry for each entry in the request, in the same order, with the outcome of processing the entry.

The target XIS SHALL return a Bundle with type set to transaction-response that contains one entry for each entry in the request, in the same order, with the outcome of processing the entry.

A client may use the returned Bundle to track the outcomes of processing the entry, and the identities assigned to the resources by the server. Each entry element SHALL contain a response element which details the outcome of processing the entry - the HTTP status code, and the location and ETag header values, which are used for identifying and versioning the resources. In addition, a resource may be included in the entry, as specified by the Prefer header.

==List of profiles==

IHE has defined profiles applicable to this use case. Although the IHE MHD Profile text (the published PDF) is Normative these conformance resources are labelled as Informative. Not all IHE MHD profiles are implementable as-is for the send use case because of errors that IHE does not intend to resolve in FHIR STU3, but instead, require updating to FHIR R4. MedMij is not ready upgrading to FHIR R4 for just this use case and has implemented the necessary fixes in the IHE FHIR STU3 profiles to support this use case. The IHE MHD profiles 'IHE.MHD.DocumentManifest' and 'IHE.MHD.ProvideDocumentBundle.Minimal' are therefore copied, adjusted for the known issues and released in the Nictiz namespace. The table below shows the IHE MHD profiles used for the Providing Document Bundle transaction and the relevant HCIM profiles. Note that IHE originally created two profiles on DocumentReference, one for Query DocumentReference and one for Provide DocumentReference which are identical to eachother. For usability purposes, these two profiles have been merged.

{{MedMij:Vprepub-2020.01/NoteBoxPackage|p1=nictiz.fhir.nl.stu3.zib2017}}
{| class="wikitable" width="1400px"
|-style="background-color: #1F497D; color: white; font-weight: bold; "
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Zib name NL
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Zib name EN
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|FHIR Resource
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|URL profile
|-style="vertical-align:top; background-color: #E3E3E3;
|-
| style="background-color: white;"| Patient
| #Zib Patient|Patient
| style="background-color: white;"| Patient
| style="background-color: white;"| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nictiz.fhir.nl.stu3.zib2017}}
|-
| rowspan="2" style="background-color: white;" | [https://zibs.nl/wiki/Zorgverlener-v3.2(2017NL) Zorgverlener]
| rowspan="2" style="background-color: white;" | [https://zibs.nl/wiki/HealthProfessional-v3.2(2017EN) HealthProfessional]
| style="background-color: white;"| Practitioner
| style="background-color: white;"| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017}}
|-
| style="background-color: white;"| PractitionerRole
| style="background-color: white;"| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nictiz.fhir.nl.stu3.zib2017}}
|-
| style="background-color: white;"| Zorgaanbieder
| style="background-color: white;"| HealthcareProvider
| style="background-color: white;"| Organization
| style="background-color: white;"| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017}}
|-
| style="background-color: white;"| -
| style="background-color: white;"| -
| style="background-color: white;"| Bundle
| style="background-color: white;"| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/IHE.MHD.Minimal.ProvideDocumentBundle|nictiz.fhir.nl.stu3.zib2017}}
|-
| style="background-color: white;"| -
| style="background-color: white;"| -
| style="background-color: white;"| DocumentManifest
| style="background-color: white;"| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/IHE.MHD.DocumentManifest|nictiz.fhir.nl.stu3.zib2017}}
|-
| style="background-color: white;"| -
| style="background-color: white;"| -
| style="background-color: white;"| DocumentReference
| style="background-color: white;"| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/IHE.MHD.Minimal.DocumentReference|nictiz.fhir.nl.stu3.zib2017}}
|-
| style="background-color: white;"| -
| style="background-color: white;"| -
| style="background-color: white;"| List
| style="background-color: white;"| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/IHE.MHD.List|nictiz.fhir.nl.stu3.zib2017}}
|}

=Release notes=
Release notes can be found on the [[MedMij:Vprepub-2020.01/OntwerpPDFA#Release_notes| functional design page]].