Sjabloon:FHIR-IG-Afsprakenstelsel-Note - Bewerkingsoverzicht

Ardon Toonstra op 15 okt 2018 om 15:44

2018-10-15T15:44:55Z

← Oudere versie		Versie van 15 okt 2018 15:44
Regel 1:		Regel 1:
	This FHIR implementation guide assumes that the ~~PHE~~ system is able to make a connection to the right XIS that contains the patient's information. It does not provide information on finding the right XIS nor does it provide information about security. Moreover, each transaction is performed in the context of a specific authenticated patient, for whose context (token) has been established using the authentication mechanisms described in the [https://www.medmij.nl/afsprakenstelsel/ 'Afsprakenstelsel']. <!--This token must be passed in each call in the HTTP header named “Authorization”.--> Each XIS Gateway is required to perform filtering based on the patient associated with the context for the request, so only the records associated with the authenticated patient are returned. For this reason, search parameters should not be included for patient identification.		This FHIR implementation guide assumes that the PHR system is able to make a connection to the right XIS that contains the patient's information. It does not provide information on finding the right XIS nor does it provide information about security. Moreover, each transaction is performed in the context of a specific authenticated patient, for whose context (token) has been established using the authentication mechanisms described in the [https://www.medmij.nl/afsprakenstelsel/ 'Afsprakenstelsel']. <!--This token must be passed in each call in the HTTP header named “Authorization”.--> Each XIS Gateway is required to perform filtering based on the patient associated with the context for the request, so only the records associated with the authenticated patient are returned. For this reason, search parameters should not be included for patient identification.

Ardon Toonstra op 11 sep 2018 om 11:19

2018-09-11T11:19:12Z

← Oudere versie		Versie van 11 sep 2018 11:19
Regel 1:		Regel 1:
	This FHIR implementation guide assumes that the PHE system is able to make a connection to the right XIS that contains the patient's information. It does not provide information on finding the right XIS nor does it provide information about security. Moreover, each transaction is performed in the context of a specific authenticated patient, for whose context (token) has been established using the authentication mechanisms described in the [https://www.medmij.nl/afsprakenstelsel/ 'Afsprakenstelsel']. <!--This token must be passed in each call in the HTTP header named “Authorization”.--> Each XIS Gateway is required to perform filtering based on the patient associated with the context for the request, so only the records associated with the authenticated patient are returned. For this reason search parameters should be ~~passed~~ for patient identification.		This FHIR implementation guide assumes that the PHE system is able to make a connection to the right XIS that contains the patient's information. It does not provide information on finding the right XIS nor does it provide information about security. Moreover, each transaction is performed in the context of a specific authenticated patient, for whose context (token) has been established using the authentication mechanisms described in the [https://www.medmij.nl/afsprakenstelsel/ 'Afsprakenstelsel']. <!--This token must be passed in each call in the HTTP header named “Authorization”.--> Each XIS Gateway is required to perform filtering based on the patient associated with the context for the request, so only the records associated with the authenticated patient are returned. For this reason, search parameters should not be included for patient identification.

Ardon Toonstra op 14 mrt 2018 om 11:52

2018-03-14T11:52:59Z

← Oudere versie		Versie van 14 mrt 2018 11:52
Regel 1:		Regel 1:
	This FHIR implementation guide assumes that the ~~PHR~~ system is able to make a connection to the right XIS that contains the patient's information. It does not provide information on finding the right XIS nor does it provide information about security. Moreover, each transaction is performed in the context of a specific authenticated patient, for whose context (token) has been established using the authentication mechanisms described in the [https://www.medmij.nl/afsprakenstelsel/ 'Afsprakenstelsel']. <!--This token must be passed in each call in the HTTP header named “Authorization”.--> Each XIS Gateway is required to perform filtering based on the patient associated with the context for the request, so only the records associated with the authenticated patient are returned. For this reason search parameters should be passed for patient identification.		This FHIR implementation guide assumes that the PHE system is able to make a connection to the right XIS that contains the patient's information. It does not provide information on finding the right XIS nor does it provide information about security. Moreover, each transaction is performed in the context of a specific authenticated patient, for whose context (token) has been established using the authentication mechanisms described in the [https://www.medmij.nl/afsprakenstelsel/ 'Afsprakenstelsel']. <!--This token must be passed in each call in the HTTP header named “Authorization”.--> Each XIS Gateway is required to perform filtering based on the patient associated with the context for the request, so only the records associated with the authenticated patient are returned. For this reason search parameters should be passed for patient identification.

Ardon Toonstra: Nieuwe pagina aangemaakt met 'This FHIR implementation guide assumes that the PHR system is able to make a connection to the right XIS that contains the patient's information. It does not provid...'

2018-01-02T11:45:18Z

Nieuwe pagina aangemaakt met 'This FHIR implementation guide assumes that the PHR system is able to make a connection to the right XIS that contains the patient's information. It does not provid...'

Nieuwe pagina

This FHIR implementation guide assumes that the PHR system is able to make a connection to the right XIS that contains the patient's information. It does not provide information on finding the right XIS nor does it provide information about security. Moreover, each transaction is performed in the context of a specific authenticated patient, for whose context (token) has been established using the authentication mechanisms described in the [https://www.medmij.nl/afsprakenstelsel/ 'Afsprakenstelsel'].  Each XIS Gateway is required to perform filtering based on the patient associated with the context for the request, so only the records associated with the authenticated patient are returned. For this reason search parameters should be passed for patient identification.