Skip to content

Commit 964b65a

Browse files
committed
move normative text outside of example section
Fixes FHIR-28671
1 parent a92d6de commit 964b65a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/specification/current.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -230,7 +230,7 @@ A prefetch token is a placeholder in a prefetch template that is replaced by a v
230230

231231
Prefetch tokens MUST be delimited by `{{` and `}}`, and MUST contain only the qualified path to a hook context field.
232232

233-
Individual hooks specify which of their `context` fields can be used as prefetch tokens. Only root-level fields with a primitive value within the `context` object are eligible to be used as prefetch tokens. For example, `{{context.medication.id}}` is not a valid prefetch token because it attempts to access the `id` field of the `medication` field.
233+
Individual hooks specify which of their `context` fields can be used as prefetch tokens. Only root-level fields with a primitive value within the `context` object are eligible to be used as prefetch tokens. For example, `{{context.medication.id}}` is not a valid prefetch token because it attempts to access the `id` field of the `medication` field. Hook creators MUST document which fields in the context are supported as tokens. If a context field can be tokenized, the value of the context field MUST be a JSON primitive data type that can placed into a FHIR query (i.e. a string, a number, or a boolean).
234234

235235
#### Prefetch query restrictions
236236

@@ -256,7 +256,7 @@ Often a prefetch template builds on the contextual data associated with the hook
256256

257257
The token name would be `{{context.patientId}}`. Again using our above conditions example, the complete prefetch template would be `Condition?patient={{context.patientId}}`.
258258

259-
Only the first level fields in context may be considered for tokens. Hook creators MUST document which fields in the context are supported as tokens. If a context field can be tokenized, the value of the context field MUST be a JSON primitive data type that can placed into a FHIR query (i.e. a string, a number, or a boolean).
259+
Only the first level fields in context may be considered for tokens.
260260

261261
For example, given the following context that contains amongst other things, a Patient FHIR resource:
262262

0 commit comments

Comments
 (0)