Merge pull request #449 from cds-hooks/issue/202-add-hook-context-naming-recommendation

Recommend that hook authors name their context fields consistent with other hooks

Author: kpshek

docs/specification/1.0.md

@@ -830,7 +830,7 @@ Describe the set of contextual data used by this hook. Only data logically and n
 
 All fields defined by the hook's context MUST be defined in a table where each field is described by the following attributes:
 
-- Field: The name of the field in the context JSON object.
+- Field: The name of the field in the context JSON object. Hook authors SHOULD name their context fields to be consistent with other existing hooks when referring to the same context field.
 - Optionality: A string value of either `REQUIRED` or `OPTIONAL`
 - Prefetch Token: A string value of either `Yes` or `No`, indicating whether this field can be tokenized in a prefetch template.
 - Type: The type of the field in the context JSON object, expressed as the JSON type, or the name of a FHIR Resource type. Valid types are *boolean*, *string*, *number*, *object*, *array*, or the name of a FHIR resource type. When a field can be of multiple types, type names MUST be separated by a *pipe* (`|`)