MedMij:V2017.04 FHIR PDFA - Bewerkingsoverzicht

Pieter Edelman: Tekst vervangen - "{{Simplifier\|([^\|]+)(\|[^}]+)?\|scope=([^\|}@]+)@([^\|}]+)}}" door "{{Simplifier|$1|$3|pkgVersion=$4$2}}"

2020-07-30T12:50:21Z

Tekst vervangen - "{{Simplifier\|([^\|]+)(\|[^}]+)?\|scope=([^\|}@]+)@([^\|}]+)}}" door "{{Simplifier|$1|$3|pkgVersion=$4$2}}"

← Oudere versie		Versie van 30 jul 2020 12:50
Regel 76:		Regel 76:
	\| PHR		\| PHR
	\| Personal health record		\| Personal health record
	\|[[Bestand: Verwijzing.png\| 20px]] {{Simplifier\|http://nictiz.nl/fhir/CapabilityStatement/pdfa-clientcapabilities\|~~title=CapabilityStatement: Client\|scope=~~nictiz.fhir.nl.stu3.zib2015@1.0.0}}		\|[[Bestand: Verwijzing.png\| 20px]] {{Simplifier\|http://nictiz.nl/fhir/CapabilityStatement/pdfa-clientcapabilities\|nictiz.fhir.nl.stu3.zib2015\|pkgVersion=1.0.0\|title=CapabilityStatement: Client}}
	\| PDFA FHIR Client requirements		\| PDFA FHIR Client requirements
	\|-		\|-
Regel 83:		Regel 83:
	\| XIS		\| XIS
	\| Healthcare information system		\| Healthcare information system
	\|[[Bestand: Verwijzing.png\| 20px]] {{Simplifier\|http://nictiz.nl/fhir/CapabilityStatement/pdfa-servercapabilities\|~~title=CapabilityStatement: Server\|scope=~~nictiz.fhir.nl.stu3.zib2015@1.0.0}}		\|[[Bestand: Verwijzing.png\| 20px]] {{Simplifier\|http://nictiz.nl/fhir/CapabilityStatement/pdfa-servercapabilities\|nictiz.fhir.nl.stu3.zib2015\|pkgVersion=1.0.0\|title=CapabilityStatement: Server}}
	\| PDFA FHIR Server requirements		\| PDFA FHIR Server requirements
	\|}		\|}

Pieter Edelman: Tekst vervangen - "{{Simplifier\|([^\|}]+)\|([^(scope=)][^\|}]+)" door "{{Simplifier|$1|title=$2"

2020-07-29T19:39:43Z

Tekst vervangen - "{{Simplifier\|([^\|}]+)\|([^(scope=)][^\|}]+)" door "{{Simplifier|$1|title=$2"

← Oudere versie		Versie van 29 jul 2020 19:39
Regel 76:		Regel 76:
	\| PHR		\| PHR
	\| Personal health record		\| Personal health record
	\|[[Bestand: Verwijzing.png\| 20px]] {{Simplifier\|http://nictiz.nl/fhir/CapabilityStatement/pdfa-clientcapabilities\|CapabilityStatement: Client\|scope=nictiz.fhir.nl.stu3.zib2015@1.0.0}}		\|[[Bestand: Verwijzing.png\| 20px]] {{Simplifier\|http://nictiz.nl/fhir/CapabilityStatement/pdfa-clientcapabilities\|title=CapabilityStatement: Client\|scope=nictiz.fhir.nl.stu3.zib2015@1.0.0}}
	\| PDFA FHIR Client requirements		\| PDFA FHIR Client requirements
	\|-		\|-
Regel 83:		Regel 83:
	\| XIS		\| XIS
	\| Healthcare information system		\| Healthcare information system
	\|[[Bestand: Verwijzing.png\| 20px]] {{Simplifier\|http://nictiz.nl/fhir/CapabilityStatement/pdfa-servercapabilities\|CapabilityStatement: Server\|scope=nictiz.fhir.nl.stu3.zib2015@1.0.0}}		\|[[Bestand: Verwijzing.png\| 20px]] {{Simplifier\|http://nictiz.nl/fhir/CapabilityStatement/pdfa-servercapabilities\|title=CapabilityStatement: Server\|scope=nictiz.fhir.nl.stu3.zib2015@1.0.0}}
	\| PDFA FHIR Server requirements		\| PDFA FHIR Server requirements
	\|}		\|}

Maarten Ligtvoet: Tekst vervangen - "{{#customtitle:" door "{{DISPLAYTITLE:"

2020-07-20T01:12:16Z

Tekst vervangen - "{{#customtitle:" door "{{DISPLAYTITLE:"

← Oudere versie		Versie van 20 jul 2020 01:12
Regel 1:		Regel 1:
	{{~~#customtitle~~:MedMij FHIR use case PDF/A, publication 2017.04}}		{{DISPLAYTITLE:MedMij FHIR use case PDF/A, publication 2017.04}}
	[[Bestand:MedMij2.png \|link=https://www.medmij.nl/\|rechts\|Naar medmij.nl]]		[[Bestand:MedMij2.png \|link=https://www.medmij.nl/\|rechts\|Naar medmij.nl]]
	[[Bestand:PDF-A_icoon.png\|link=\|87px \|links\|\|Self-Measurements]]		[[Bestand:PDF-A_icoon.png\|link=\|87px \|links\|\|Self-Measurements]]

Pieter Edelman: /* Actors and transactions involved */ Redirect Simplifier-links to package

2020-06-03T18:53:32Z

Actors and transactions involved: Redirect Simplifier-links to package

← Oudere versie		Versie van 3 jun 2020 18:53
Regel 76:		Regel 76:
	\| PHR		\| PHR
	\| Personal health record		\| Personal health record
	\|[[Bestand: Verwijzing.png\| 20px]] ~~[https~~://~~simplifier~~.~~net~~/~~NictizSTU3~~/pdfa-clientcapabilities CapabilityStatement: Client]		\|[[Bestand: Verwijzing.png\| 20px]] {{Simplifier\|http://nictiz.nl/fhir/CapabilityStatement/pdfa-clientcapabilities\|CapabilityStatement: Client\|scope=nictiz.fhir.nl.stu3.zib2015@1.0.0}}
	\| PDFA FHIR Client requirements		\| PDFA FHIR Client requirements
	\|-		\|-
Regel 83:		Regel 83:
	\| XIS		\| XIS
	\| Healthcare information system		\| Healthcare information system
	\|[[Bestand: Verwijzing.png\| 20px]] ~~[https~~://~~simplifier~~.~~net~~/~~NictizSTU3~~/pdfa-servercapabilities CapabilityStatement: Server]		\|[[Bestand: Verwijzing.png\| 20px]] {{Simplifier\|http://nictiz.nl/fhir/CapabilityStatement/pdfa-servercapabilities\|CapabilityStatement: Server\|scope=nictiz.fhir.nl.stu3.zib2015@1.0.0}}
	\| PDFA FHIR Server requirements		\| PDFA FHIR Server requirements
	\|}		\|}

Marc: /* Transactions in scope */

2018-03-20T08:10:53Z

Transactions in scope

← Oudere versie		Versie van 20 mrt 2018 08:10
Regel 121:		Regel 121:
	===Transactions in scope===		===Transactions in scope===

	* Find Document Manifests – This transaction is used to issue parameterized queries that result in a list of Document Manifest resources.		* Find Document Manifests [ITI-66] – 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 result in a list of Document Reference resources.		* Find Document References [ITI-67] – This transaction is used to issue parameterized queries that result in a list of Document Reference resources.
	* Retrieve Document – This transaction is used to get documents.		* Retrieve Document [ITI-68] – This transaction is used to get documents.

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

Ardon Toonstra: /* Response Message */

2018-03-14T14:11:26Z

Response Message

← Oudere versie		Versie van 14 mrt 2018 14:11
Regel 349:		Regel 349:

	====Response Message====		====Response Message====
	The Document Responder shall process the request message. The Document Responder returns a HTTP Status code appropriate to the processing as well as the PDF/A in a FHIR [http://hl7.org/fhir/STU3/binary.html Binary] ~~Resource~~. Binary resources behave slightly differently to 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 Responder shall process the request message. The Document Responder returns a 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 to 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]

	When the Document Responder needs to report an error or warning, it shall use HTTP error response codes and should include a [http://hl7.org/fhir/STU3/operationoutcome.html OperationOutcome] with more details on the failure or warning. If the Retrieve Document message is processed successfully the HTTP status code shall be 200.		When the Document Responder needs to report an error or warning, it shall use HTTP error response codes and should include a [http://hl7.org/fhir/STU3/operationoutcome.html OperationOutcome] with more details on the failure or warning. If the Retrieve Document message is processed successfully the HTTP status code shall be 200.

Ardon Toonstra: /* List of StructureDefinitions */

2018-03-14T13:58:55Z

List of StructureDefinitions

← Oudere versie		Versie van 14 mrt 2018 13:58
Regel 386:		Regel 386:

	==List of StructureDefinitions==		==List of StructureDefinitions==
	~~The following HL7 FHIR STU3~~ StructureDefinitions are ~~defined for MHD:~~		IHE has defined StructureDefinitions and other Conformance resources applicable for this use case. They are listed under 'FHIR Implementation Guide' on the [http://wiki.ihe.net/index.php/Mobile_access_to_Health_Documents_(MHD)#FHIR_Implementation_Guide IHE MHD wiki].
	* [~~https~~://~~simplifier~~.~~net/IHEPatientDemographi/IHEMHDDocumentManifest http://~~ihe.net/~~fhir/StructureDefinition~~/~~IHE.~~MHD~~.DocumentManifest]~~
	* [https://simplifier.net/IHEPatientDemographi/IHEMHDDocumentReference http://ihe.net/fhir/StructureDefinition/IHE.MHD~~.DocumentReference~~]
	* [https://simplifier.~~net/IHEPatientDemographi/IHEMHDList http://ihe.net/fhir/StructureDefinition/IHE.MHD.List]~~

Ardon Toonstra: /* Response Message */

2018-03-14T08:23:12Z

Response Message

← Oudere versie		Versie van 14 mrt 2018 08:23
Regel 349:		Regel 349:

	====Response Message====		====Response Message====
	The Document Responder shall process the request message. The Document Responder returns a HTTP Status code appropriate to the processing as well as ~~a Bundle with~~ the PDF/A in a FHIR [http://hl7.org/fhir/STU3/binary.html Binary] Resource. Binary resources behave slightly differently to 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 Responder shall process the request message. The Document Responder returns a HTTP Status code appropriate to the processing as well as the PDF/A in a FHIR [http://hl7.org/fhir/STU3/binary.html Binary] Resource. Binary resources behave slightly differently to 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]

	When the Document Responder needs to report an error or warning, it shall use HTTP error response codes and should include a [http://hl7.org/fhir/STU3/operationoutcome.html OperationOutcome] with more details on the failure or warning. If the Retrieve Document message is processed successfully the HTTP status code shall be 200.		When the Document Responder needs to report an error or warning, it shall use HTTP error response codes and should include a [http://hl7.org/fhir/STU3/operationoutcome.html OperationOutcome] with more details on the failure or warning. If the Retrieve Document message is processed successfully the HTTP status code shall be 200.

	'''Example of a response message'''		'''Example of a response message'''
	<pre>		<pre><Binary>
	~~<Bundle xmlns="http://hl7.org/fhir">~~		<id value="1e404af3-077f-4bee-b7a6-a9be97e1ce32" />
	~~<id value="5905e2ee-8505-4f13-8701-63b33b531291" />~~		<meta>
	~~<meta>~~		<versionId value="948f3653-c9a3-4831-bae5-f629319c194f" />
	~~<versionId value="f80e4263-f7ef-4a6f-9996-95ee7607f553" />~~		<lastUpdated value="2017-09-20T17:55:14.098+00:00" />
	~~<lastUpdated value="2017-10-25T12:24:26.69+00:00" />~~		</meta>
	~~</meta>~~		<contentType value="application/pdf" />
	~~<type value="searchset" />~~		<content value="JVBERi0xLjUNJeLjz9MNCjU1I........"/>
	~~<total value="1" />~~		</Binary></pre>
	~~<link>~~
	~~<relation value="self" />~~
	<~~url value="http://example:9556/svc/fhir/~~Binary~~/1e404af3-077f-4bee-b7a6-a9be97e1ce32" /~~>
	~~</link>~~
	~~<entry>~~
	~~<fullUrl value="http://example:9556/svc/fhir/Binary/1e404af3-077f-4bee-b7a6-a9be97e1ce32" />~~
	~~<resource>~~
	~~<Binary>~~
	<id value="1e404af3-077f-4bee-b7a6-a9be97e1ce32" />
	<meta>
	<versionId value="948f3653-c9a3-4831-bae5-f629319c194f" />
	<lastUpdated value="2017-09-20T17:55:14.098+00:00" />
	</meta>
	<contentType value="application/pdf" />
	<content value="JVBERi0xLjUNJeLjz9MNCjU1I........"/>
	</Binary>
	~~</resource>~~
	~~</entry>~~
	~~<Bundle>~~
	</pre>

	==Interactions, operations, search parameters==		==Interactions, operations, search parameters==

Ahenket: /* Response Message */

2018-01-11T10:21:56Z

Response Message

← Oudere versie		Versie van 11 jan 2018 10:21
Regel 379:		Regel 379:
	<content value="JVBERi0xLjUNJeLjz9MNCjU1I........"/>		<content value="JVBERi0xLjUNJeLjz9MNCjU1I........"/>
	</Binary>		</Binary>
			</resource>
	</entry>		</entry>
	<Bundle>		<Bundle>

Ardon Toonstra op 18 dec 2017 om 12:15

2017-12-18T12:15:04Z

← Oudere versie		Versie van 18 dec 2017 12:15
Regel 4:		Regel 4:
	<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:V2017.~~04_draft_OntwerpPDFA~~\|Functioneel]]		circle 1013 224 212 [[MedMij:V2017.04_OntwerpPDFA\|Functioneel]]
	circle 1787 230 212 [[MedMij:V2017.04_FHIR_IG\|Technisch]]		circle 1787 230 212 [[MedMij:V2017.04_FHIR_IG\|Technisch]]
	desc none		desc none