From dbc6c627edff490258e1446707fa019126d30343 Mon Sep 17 00:00:00 2001 From: Paulius Galinauskas Date: Thu, 7 Dec 2023 12:50:10 +0200 Subject: [PATCH 1/3] FHIR-43352: Relax requirement for extensions Currently in Extensions paragraph, the requirement for an Extension is to be "pre-coordinated". It is enough for an extension to be a valid JSON object. --- input/pagecontent/2-8-Extensions.md | 40 ++++++++++++++--------------- 1 file changed, 20 insertions(+), 20 deletions(-) diff --git a/input/pagecontent/2-8-Extensions.md b/input/pagecontent/2-8-Extensions.md index 6df37fc7..d4aed6df 100644 --- a/input/pagecontent/2-8-Extensions.md +++ b/input/pagecontent/2-8-Extensions.md @@ -1,20 +1,20 @@ -The specification is not prescriptive about support for extensions. However, to support extensions, the specification reserves the name `extension` and will never define an element with that name, allowing implementations to use it to provide custom behavior and information. The value of an extension element MUST be a pre-coordinated JSON object. For example, an extension on a notification could look like this: - -```json -{ - "context": [{ - "key": "patient", - "resource": { - "resourceType": "Patient", - "id": "ewUbXT9RWEbSj5wPEdgRaBw3" - } - }, - { - "key": "extension", - "data": { - "user-timezone": "+1:00" - } - } - ] -} -``` +The specification is not prescriptive about support for extensions. However, to support extensions, the specification reserves the name `extension` and will never define an element with that name, allowing implementations to use it to provide custom behavior and information. The value of an extension element MUST be a valid JSON object. For example, an extension on a notification could look like this: + +```json +{ + "context": [{ + "key": "patient", + "resource": { + "resourceType": "Patient", + "id": "ewUbXT9RWEbSj5wPEdgRaBw3" + } + }, + { + "key": "extension", + "data": { + "user-timezone": "+1:00" + } + } + ] +} +``` From 28128e0c853ce176db8783162dde74b410f1401b Mon Sep 17 00:00:00 2001 From: Isaac Vetter Date: Wed, 27 Dec 2023 08:09:09 -0600 Subject: [PATCH 2/3] set implementer expectations for pre-coordination of extensions/2-8-Extensions.md --- input/pagecontent/2-8-Extensions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/input/pagecontent/2-8-Extensions.md b/input/pagecontent/2-8-Extensions.md index d4aed6df..9b58fab4 100644 --- a/input/pagecontent/2-8-Extensions.md +++ b/input/pagecontent/2-8-Extensions.md @@ -1,4 +1,4 @@ -The specification is not prescriptive about support for extensions. However, to support extensions, the specification reserves the name `extension` and will never define an element with that name, allowing implementations to use it to provide custom behavior and information. The value of an extension element MUST be a valid JSON object. For example, an extension on a notification could look like this: +The specification is not prescriptive about support for extensions. However, to support extensions, the specification reserves the name `extension` and will never define an element with that name, allowing implementations to use it to provide custom behavior and information. The value of an extension element MUST be a valid JSON object and is typically pre-coordinated. For example, an extension on a notification could look like this: ```json { From a066262f0bcdd5817268f862570d824b51c22e44 Mon Sep 17 00:00:00 2001 From: Bas van den Heuvel Date: Wed, 3 Jul 2024 11:44:07 +0200 Subject: [PATCH 3/3] Change MUST to SHALL Co-authored-by: Isaac Vetter --- input/pagecontent/2-8-Extensions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/input/pagecontent/2-8-Extensions.md b/input/pagecontent/2-8-Extensions.md index 9b58fab4..2d74f8e2 100644 --- a/input/pagecontent/2-8-Extensions.md +++ b/input/pagecontent/2-8-Extensions.md @@ -1,4 +1,4 @@ -The specification is not prescriptive about support for extensions. However, to support extensions, the specification reserves the name `extension` and will never define an element with that name, allowing implementations to use it to provide custom behavior and information. The value of an extension element MUST be a valid JSON object and is typically pre-coordinated. For example, an extension on a notification could look like this: +The specification is not prescriptive about support for extensions. However, to support extensions, the specification reserves the name `extension` and will never define an element with that name, allowing implementations to use it to provide custom behavior and information. The value of an extension element SHALL be a valid JSON object and is typically pre-coordinated. For example, an extension on a notification could look like this: ```json {