MedMij:Vprepub-2020.01/FHIR PDFA - Bewerkingsoverzicht

Luud Slagter: MM-3500: Added known issue w.r.t. unused profiles

2022-09-20T08:34:31Z

MM-3500: Added known issue w.r.t. unused profiles

← Oudere versie		Versie van 20 sep 2022 08:34
Regel 260:		Regel 260:
	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 267:		Regel 267:
	* 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.
Regel 355:		Regel 355:
	==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}}
Regel 404:		Regel 404:
	\| 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]].

Vincent Goris: MM-1960, Support for the Find DocumentManifest transaction is made optional instead of mandatory for servers.

2021-04-26T08:25:22Z

MM-1960, Support for the Find DocumentManifest transaction is made optional instead of mandatory for servers.

← Oudere versie		Versie van 26 apr 2021 08:25
Regel 151:		Regel 151:
	! style="font-weight: bold; text-align:left;" \| MHD Actors		! 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;" \| MHD Transactions
			! style="font-weight: bold; text-align:left;" \| Optionallity
	\|-		\|-
	\| rowspan="5" \| Patient		\| rowspan="5" \| Patient
Regel 158:		Regel 159:
	\| rowspan="3" \| Document Consumer		\| rowspan="3" \| Document Consumer
	\| Find Document Manifest		\| Find Document Manifest
			\| Optional
	\|-		\|-
	\| Find Document Reference		\| Find Document Reference
			\| Required
	\|-		\|-
	\| Retrieve Document		\| Retrieve Document
			\| Required
	\|-		\|-
	\| rowspan="5" \| Healthcare provider		\| rowspan="5" \| Healthcare provider
Regel 169:		Regel 173:
	\| rowspan="3" \| Document Responder		\| rowspan="3" \| Document Responder
	\| Find Document Manifest		\| Find Document Manifest
			\| Optional
	\|-		\|-
	\| Find Document Reference		\| Find Document Reference
			\| Required
	\|-		\|-
	\| Retrieve Document		\| Retrieve Document
			\| Required
	\|}		\|}
	<font size = "1">'''Table 2. MHD actors and transactions in perspective of systems in a MedMij context'''</font>		<font size = "1">'''Table 2. MHD actors and transactions in perspective of systems in a MedMij context''' </font>

	~~===Transactions in scope===~~		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 Document Manifests – This transaction is used to issue parameterized queries that result in a list of ~~Document Manifest resources.~~
	* Find ~~Document References – This transaction is used to issue parameterized queries that produce a list of~~ Document Reference ~~resources.~~
	* Retrieve Document – This transaction is used to get documents.

	~~Document Consumer shall implement 'Find Document References~~' and 'Retrieve Document'~~, implementing~~ 'Find Document Manifest' is optional for Document Consumer. Document Responder ~~shall implement all transactions.~~

	~~===Transactions out of scope===~~
	The MHD profile specifies how to send documents from a Document Source to a Document Receiver using the Provide Document Bundle transaction. However, sending PDF/A documents is currently out of scope for the MedMij context. The 'Afsprakenstelsel' first focuses on pulling data from a XIS to a PHR before considering push transactions. In the future, specifications of sending PDF/A documents from a PHR will be added.

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

Niek van Galen: MM-1899: updated notebox to be ready for a minimum and maximum package version

2021-03-22T09:21:06Z

MM-1899: updated notebox to be ready for a minimum and maximum package version

← Oudere versie		Versie van 22 mrt 2021 09:21
Regel 273:		Regel 273:
	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.

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

	{\| class="wikitable" width="1400px"		{\| class="wikitable" width="1400px"

Pieter Edelman: Tekst vervangen - "MedMij:Vprepub" door "MedMij:Vprepub-2020.01"

2020-12-01T12:53:16Z

Tekst vervangen - "MedMij:Vprepub" door "MedMij:Vprepub-2020.01"

← Oudere versie		Versie van 1 dec 2020 12:53
Regel 1:		Regel 1:
	__NUMBEREDHEADINGS__		__NUMBEREDHEADINGS__
	{{DISPLAYTITLE:MedMij FHIR Implementation Guide: PDF/A {{VersieInfo\|PDFA}}}}		{{DISPLAYTITLE:MedMij FHIR Implementation Guide: PDF/A {{VersieInfo\|PDFA}}}}
	{{MedMij:Vprepub/Issuebox_FHIR_IG}}		{{MedMij:Vprepub-2020.01/Issuebox_FHIR_IG}}

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

	=Introduction=		=Introduction=
	[[Bestand:Functioneel-02.png\|link=MedMij:Vprepub/Ontwerpen \|100px\|rechts\|Functional design\|Go to functional design]]		[[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.		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.

Regel 22:		Regel 22:
	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		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/FHIR_IG#Use case overarching principles\|use case overarching principles]].		'''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===		===IHE MHD specification===
Regel 273:		Regel 273:
	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.

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

	{\| class="wikitable" width="1400px"		{\| class="wikitable" width="1400px"
Regel 359:		Regel 359:
	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.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/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}		{{MedMij:Vprepub-2020.01/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}
	{\| class="wikitable" width="1400px"		{\| class="wikitable" width="1400px"
	\|-style="background-color: #1F497D; color: white; font-weight: bold; "		\|-style="background-color: #1F497D; color: white; font-weight: bold; "
Regel 408:		Regel 408:

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

Pieter Edelman: Pieter Edelman heeft de pagina MedMij:Vprepub/FHIR PDFA hernoemd naar MedMij:Vprepub-2020.01/FHIR PDFA zonder een doorverwijzing achter te laten: Generaliseren van prepub-mechanisme

2020-12-01T12:49:26Z

Pieter Edelman heeft de pagina MedMij:Vprepub/FHIR PDFA hernoemd naar MedMij:Vprepub-2020.01/FHIR PDFA zonder een doorverwijzing achter te laten: Generaliseren van prepub-mechanisme

← Oudere versie	Versie van 1 dec 2020 12:49
(geen verschil)

Pieter Edelman: Tekst vervangen - "MedMij:Vissue-MM-1522/NoteBoxPackage" door "MedMij:Vprepub/NoteBoxPackage"

2020-11-20T13:14:57Z

Tekst vervangen - "MedMij:Vissue-MM-1522/NoteBoxPackage" door "MedMij:Vprepub/NoteBoxPackage"

← Oudere versie		Versie van 20 nov 2020 13:14
Regel 273:		Regel 273:
	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.

	{{MedMij:~~Vissue-MM-1522~~/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}		{{MedMij:Vprepub/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}

	{\| class="wikitable" width="1400px"		{\| class="wikitable" width="1400px"
Regel 359:		Regel 359:
	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.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:~~Vissue-MM-1522~~/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}		{{MedMij:Vprepub/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}
	{\| class="wikitable" width="1400px"		{\| class="wikitable" width="1400px"
	\|-style="background-color: #1F497D; color: white; font-weight: bold; "		\|-style="background-color: #1F497D; color: white; font-weight: bold; "

Jorn Duwel: MM-1522: Removing 'Terminology...' section, removing references to Sjabloon:Voorbeelden, updating NoteBoxPackage to 2020.01 version

2020-11-13T15:38:09Z

MM-1522: Removing 'Terminology...' section, removing references to Sjabloon:Voorbeelden, updating NoteBoxPackage to 2020.01 version

← Oudere versie		Versie van 13 nov 2020 15:38
Regel 242:		Regel 242:
	** 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 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 Document Responder shall return only PDF/A documents and shall place into the ''''DocumentReference.content.attachment.contentType'''' element the value 'application/pdf'.

	~~{{Sjabloon:Voorbeelden}}~~

	===Retrieve PDF/A document===		===Retrieve PDF/A document===
Regel 260:		Regel 258:

	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]		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]

	~~{{Sjabloon:Voorbeelden}}~~

	==List of profiles==		==List of profiles==
Regel 277:		Regel 273:
	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.

	{{MedMij:NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}		{{MedMij:Vissue-MM-1522/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}

	{\| class="wikitable" width="1400px"		{\| class="wikitable" width="1400px"
Regel 309:		Regel 305:
	\| {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/IHE.MHD.Minimal.DocumentReference\|nictiz.fhir.nl.stu3.zib2017}}		\| {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/IHE.MHD.Minimal.DocumentReference\|nictiz.fhir.nl.stu3.zib2017}}
	\|}		\|}
	~~{{Sjabloon:Voorbeelden}}~~

	=Use case: Send PDF/A document(s)=		=Use case: Send PDF/A document(s)=
Regel 352:		Regel 347:
	* [http://hl7.org/fhir/STU3/http.html#transaction transaction]		* [http://hl7.org/fhir/STU3/http.html#transaction transaction]
	* [http://hl7.org/fhir/STU3/http.html#create create]		* [http://hl7.org/fhir/STU3/http.html#create create]

	~~{{Sjabloon:Voorbeelden}}~~

	===XIS: Response message===		===XIS: Response message===
Regel 366:		Regel 359:
	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.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:NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}		{{MedMij:Vissue-MM-1522/NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}
	{\| class="wikitable" width="1400px"		{\| class="wikitable" width="1400px"
	\|-style="background-color: #1F497D; color: white; font-weight: bold; "		\|-style="background-color: #1F497D; color: white; font-weight: bold; "
Regel 413:		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}}
	\|}		\|}

	~~{{Sjabloon:Voorbeelden}}~~

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

Vincent Goris: MM-1228: Removed inline examples in TO of PDF/A and replaced them with links to simplifier examples.

2020-09-25T12:43:36Z

MM-1228: Removed inline examples in TO of PDF/A and replaced them with links to simplifier examples.

Wijzigingen bekijken

Vincent Goris: MM-1328: Changed specifications of which transactions are needed to be supported by DVP

2020-09-25T12:41:37Z

MM-1328: Changed specifications of which transactions are needed to be supported by DVP

← Oudere versie		Versie van 25 sep 2020 12:41
Regel 182:		Regel 182:
	* Retrieve Document – This transaction is used to get documents.		* Retrieve Document – This transaction is used to get documents.

	Document Consumer shall implement ~~at least one transaction:~~ Find Document ~~Manifests~~, Find Document ~~References, or Retrieve~~ Document. Document Responder shall implement all transactions.		Document Consumer shall implement 'Find Document References' and 'Retrieve Document', implementing 'Find Document Manifest' is optional for Document Consumer. Document Responder shall implement all transactions.

	===Transactions out of scope===		===Transactions out of scope===

Pieter Edelman: MM-1011: Replace the generic term "StructureDefinitions" with the more specfic term "profiles"

2020-09-21T08:08:52Z

MM-1011: Replace the generic term "StructureDefinitions" with the more specfic term "profiles"

← Oudere versie		Versie van 21 sep 2020 08:08
Regel 363:		Regel 363:
	</Binary></pre>		</Binary></pre>

	==List of ~~StructureDefinitions~~==		==List of profiles==
	IHE has defined ~~StructureDefinitions~~ 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 ~~StructureDefinitions~~.		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 eachother. For usability purposes, these two profiles have been merged.

	Find and retrieve existing PDF/A document transaction uses the following ~~StructureDefinitions~~:		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}})		* 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}})		* DocumentManifest (canonical URL {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/IHE.MHD.DocumentManifest\|nictiz.fhir.nl.stu3.zib2017}})

	{{IssueBox\|The IHE ~~StructureDefinitions~~ 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 ~~StructureDefinitions~~ 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.

	{{MedMij:NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}		{{MedMij:NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}
Regel 517:		Regel 517:
	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.		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 ~~StructureDefinitions~~==		==List of profiles==

	IHE has defined ~~StructureDefinitions~~ 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.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:NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}		{{MedMij:NoteBoxPackage\|p1=nictiz.fhir.nl.stu3.zib2017}}