Skip to content

FHIR-43352: Relax requirement for extensions #514

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

FHIR-43352: Relax requirement for extensions #514

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
dbc6c62
FHIR-43352: Relax requirement for extensions
canon-cmi-paulius-galinauskas Dec 7, 2023
28128e0
set implementer expectations for pre-coordination of extensions/2-8-E…
isaacvetter Dec 27, 2023
f4549b5
Merge branch 'master' into FHIR-43352
bvdh Jul 3, 2024
a066262
Change MUST to SHALL
bvdh Jul 3, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 20 additions & 20 deletions input/pagecontent/2-8-Extensions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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"
}
}
]
}
```