FHIR:Vissue-MM-2759 Search result examples - Bewerkingsoverzicht

Pieter Edelman: /* Server doesn't support read operations */

2022-06-24T08:54:36Z

Server doesn't support read operations

← Oudere versie		Versie van 24 jun 2022 08:54
Regel 232:		Regel 232:
	"resource": {		"resource": {
	"resourceType": "Patient",		"resourceType": "Patient",
	// When returning a resource, Resource.id SHOULD be populated. When no stable .id is available, the temporary UUID, without the urn:uuid part, MAY be used instead.		// When returning a resource, Resource.id SHOULD be populated. When no stable .id is available,
			// the temporary UUID, without the urn:uuid part, MAY be used instead.
	// However, it is recommended in this case to simply leave out the Resource.id		// However, it is recommended in this case to simply leave out the Resource.id
	// "id": "69aefd96-b37d-4323-866b-762536c03375",		// "id": "69aefd96-b37d-4323-866b-762536c03375",

Pieter Edelman: /* Server supports the read operation for all resources */

2022-06-24T08:53:48Z

Server supports the read operation for all resources

← Oudere versie		Versie van 24 jun 2022 08:53
Regel 106:		Regel 106:
	},		},
	"search": {		"search": {
	// Resources that match the search request have mode set to 'match'		// Resources that match the search request have mode set to 'match'
	"mode": "match"		"mode": "match"
	}		}

Eduard de Rijcke: MM-2759 Small JSON corrections at the second example

2022-06-24T08:21:28Z

MM-2759 Small JSON corrections at the second example

← Oudere versie		Versie van 24 jun 2022 08:21
Regel 217:		Regel 217:

	// The "self link" reflects the search as it was understood by the server		// The "self link" reflects the search as it was understood by the server
	"link": {		"link": [
			{
	"relation": "self",		"relation": "self",
	"url": "https://example-server.nl/fhir/Observation?code=http://loinc.org\|85354-9"		"url": "https://example-server.nl/fhir/Observation?code=http://loinc.org\|85354-9"
	}		}
			],
	// The server is unable to offer a stable RESTful URL to the Patient resource, but it needs to satisfy the requirement		// The server is unable to offer a stable RESTful URL to the Patient resource, but it needs to satisfy the requirement
	// that all resources are resolvable. Therefore, it includes the referenced Patient resource in the searchset Bundle.		// that all resources are resolvable. Therefore, it includes the referenced Patient resource in the searchset Bundle.
Regel 255:		Regel 256:
	...		...
	}		}
	},		}
	"search": {		],
			"search": {
	// Resources that match the search request have mode set to 'match'		// Resources that match the search request have mode set to 'match'
	"mode": "match"		"mode": "match"

Eduard de Rijcke: MM-2759 Small JSON corrections at the first example

2022-06-24T08:10:44Z

MM-2759 Small JSON corrections at the first example

← Oudere versie		Versie van 24 jun 2022 08:10
Regel 71:		Regel 71:
	<syntaxhighlight lang="json" highlight="">		<syntaxhighlight lang="json" highlight="">
	{		{
	"resourceType": "Bundle",		"resourceType": "Bundle",
	...		...

	// Bundle.type should be set to 'searchset'		//Bundle.type should be set to 'searchset'
	"type": "searchset",		"type": "searchset",

	// Bundle.total is set to the number of matches for the request		// Bundle.total is set to the number of matches for the request
	"total": "1",		"total": 1,

	// The 'self link' shows the search request as how it was understood by the server		// The 'self link' shows the search request as how it was understood by the server
	"link": [		"link": [
	"relation": "self",		{
	"url": "https://example-server.nl/fhir/Observation?code=http://loinc.org\|85354-9"		"relation": "self",
	],		"url": "https://example-server.nl/fhir/Observation?code=http://loinc.org\|85354-9"
			}
	"entry": [		],
	// The Observation resource is accessible through a RESTful URL, which is used for the fullUrl
	"fullUrl": "https://example-server.nl/fhir/Observation/observation-123",		"entry": [
			{
	"resource": {		// The Observation resource is accessible through a RESTful URL, which is used for the fullUrl
	"resourceType": "Observation",		"fullUrl": "https://example-server.nl/fhir/Observation/observation-123",

	// The Resource.id MUST be populated when it is accessible using a RESTful URL.		"resource": {
	"id": "observation-123",		"resourceType": "Observation",
	...
	~~"subject": {~~		// The Resource.id MUST be populated when it is accessible using a RESTful URL.
	// The Patient resource resides on the same server and can be referenced using a relative URL.		"id": "observation-123",
	// An absolute URL could be used in this case as well.		...
	"reference": "Patient/patient-123"		// The Patient resource resides on the same server and can be referenced using a relative URL.
	}		// An absolute URL could be used in this case as well.
	~~...~~		"subject": {
	},		"reference": "Patient/patient-123"
	~~"search": {~~
	~~// Resources that match the search request have mode set to 'match'~~
	~~"mode": "match~~"
	}		}
	]		},
			"search": {
			// Resources that match the search request have mode set to 'match'
			"mode": "match"
			}
			}
			]
	}		}
	</syntaxhighlight>		</syntaxhighlight>

Pieter Edelman: /* Invalid: server doesn't support read operations and uses contained resources instead */

2022-06-23T12:16:25Z

Invalid: server doesn't support read operations and uses contained resources instead

← Oudere versie		Versie van 23 jun 2022 12:16
Regel 435:		Regel 435:
	"fullUrl": "urn:uuid:2290607c-79e8-47ed-a23e-b8c3d5f224b2",		"fullUrl": "urn:uuid:2290607c-79e8-47ed-a23e-b8c3d5f224b2",
	"resource": {		"resource": {
	"resourceType": "Observation"		"resourceType": "Observation",
	...		...
	"contained": [		"contained": [

Pieter Edelman: /* Server supports the read operation for all resources */

2022-06-23T12:15:47Z

Server supports the read operation for all resources

← Oudere versie		Versie van 23 jun 2022 12:15
Regel 87:		Regel 87:

	"entry": [		"entry": [
	~~<!--~~ The Observation resource is accessible through a RESTful URL, which is used for the fullUrl ~~-->~~		// The Observation resource is accessible through a RESTful URL, which is used for the fullUrl
	"fullUrl": "https://example-server.nl/fhir/Observation/observation-123",		"fullUrl": "https://example-server.nl/fhir/Observation/observation-123",

Pieter Edelman op 23 jun 2022 om 07:56

2022-06-23T07:56:32Z

← Oudere versie		Versie van 23 jun 2022 07:56
Regel 193:		Regel 193:
	</resource>		</resource>
	<search>		<search>
	~~<mode value="match"/>~~ <!-- Resources that match the search request have mode set to 'match' -->		<!-- Resources that match the search request have mode set to 'match' -->
			<mode value="match"/>
	</search>		</search>
	</entry>		</entry>

Pieter Edelman: Remove question mark

2022-06-23T07:55:00Z

Remove question mark

← Oudere versie		Versie van 23 jun 2022 07:55
Regel 177:		Regel 177:
	<entry>		<entry>
	<!--		<!--
	Note that the fullUrl MUST be populated, even if this resource is not referred by any other resource within the Bundle. ~~(?)~~		Note that the fullUrl MUST be populated, even if this resource is not referred by any other resource within the Bundle.
	Since the server is unable to produce a RESTful URL for reading the Observation resource, it creates an ephemeral fullUrl		Since the server is unable to produce a RESTful URL for reading the Observation resource, it creates an ephemeral fullUrl
	for this resource as well.		for this resource as well.
Regel 238:		Regel 238:
	},		},
	{		{
	// Note that the fullUrl MUST be populated, even if this resource is not referred by any other resource within the Bundle. ~~(?)~~		// Note that the fullUrl MUST be populated, even if this resource is not referred by any other resource within the Bundle.
	// Since the server is unable to produce a RESTful URL for reading the Observation resource, it creates an ephemeral fullUrl		// Since the server is unable to produce a RESTful URL for reading the Observation resource, it creates an ephemeral fullUrl
	// for this resource as well.		// for this resource as well.
Regel 302:		Regel 302:
	Since the server is unable to produce a RESTful URL for reading the Observation resource, it creates an ephemeral fullUrl		Since the server is unable to produce a RESTful URL for reading the Observation resource, it creates an ephemeral fullUrl
	for this resource.		for this resource.
	Note that the fullUrl MUST be populated, even if this resource is not referred by any other resource within the Bundle. ~~(?)~~		Note that the fullUrl MUST be populated, even if this resource is not referred by any other resource within the Bundle.
	-->		-->
	<fullUrl value="urn:uuid:e07ffa10-c043-4dd6-aa52-6ac273c82da9"/>		<fullUrl value="urn:uuid:e07ffa10-c043-4dd6-aa52-6ac273c82da9"/>
Regel 347:		Regel 347:
	// Since the server is unable to produce a RESTful URL for reading the Observation resource, it creates an ephemeral fullUrl		// Since the server is unable to produce a RESTful URL for reading the Observation resource, it creates an ephemeral fullUrl
	// for this resource.		// for this resource.
	// Note that the fullUrl MUST be populated, even if this resource is not referred by any other resource within the Bundle. ~~(?)~~		// Note that the fullUrl MUST be populated, even if this resource is not referred by any other resource within the Bundle.
	"fullUrl": "urn:uuid:e07ffa10-c043-4dd6-aa52-6ac273c82da9",		"fullUrl": "urn:uuid:e07ffa10-c043-4dd6-aa52-6ac273c82da9",
	"resource": {		"resource": {

Pieter Edelman: Add LOINC code in request

2022-06-23T07:52:13Z

Add LOINC code in request

← Oudere versie		Versie van 23 jun 2022 07:52
Regel 377:		Regel 377:
	\|-		\|-
	\| '''Request'''		\| '''Request'''
	\| <pre> GET [base]/Observation</pre>		\| <pre> GET [base]/Observation?code=http://loinc.org\|85354-9</pre>
	\|-		\|-
	\| '''Response'''		\| '''Response'''

Pieter Edelman: Add LOINC code in request

2022-06-23T07:51:54Z

Add LOINC code in request

← Oudere versie		Versie van 23 jun 2022 07:51
Regel 269:		Regel 269:
	\|-		\|-
	\| '''Request'''		\| '''Request'''
	\| <pre> GET [base]/Observation</pre>		\| <pre> GET [base]/Observation?code=http://loinc.org\|85354-9</pre>
	\|-		\|-
	\| '''Response'''		\| '''Response'''