Fix type on Bundle FHIR object in hook documentation (cds-hooks#190)

Also, fix small typo referencing an RFC link
lmckenzi · Mar 30, 2018 · d4d9cd5 · d4d9cd5
1 parent 873eafe
commit d4d9cd5
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 5 deletions.
diff --git a/docs/hooks/medication-prescribe.md b/docs/hooks/medication-prescribe.md
@@ -17,7 +17,7 @@ Field | Optionality | Prefetch Token | Type | Description
 ----- | -------- | ---- | ---- | ----
 `patientId` | REQUIRED | Yes | *string* |  The FHIR `Patient.id` of the current patient in context
 `encounterId` | OPTIONAL | Yes | *string* |  The FHIR `Encounter.id` of the current encounter in context
-`medications` | REQUIRED | No | *array* | DSTU2 - An array of MedicationOrder resources <br/> STU3 - An array of MedicationRequest resources
+`medications` | REQUIRED | No | *object* | DSTU2 - FHIR Bundle of MedicationOrder resources <br/> STU3 - FHIR Bundle of MedicationOrder
 
 ### Example (DSTU2)
 

diff --git a/docs/hooks/order-review.md b/docs/hooks/order-review.md
@@ -17,7 +17,7 @@ Field | Optionality | Prefetch Token | Type | Description
 ----- | -------- | ---- | ---- | ----
 `patientId` | REQUIRED | Yes | *string* | The FHIR `Patient.id` of the current patient in context
 `encounterId` | OPTIONAL | Yes | *string* | The FHIR `Encounter.id` of the current encounter in context
-`orders` | REQUIRED | No | *array* | DSTU2 - Array of MedicationOrder, DiagnosticOrder, DeviceUseRequest, ReferralRequest, ProcedureRequest, NutritionOrder, VisionPrescription <br/> STU3 - Array of MedicationRequest, ReferralRequest, ProcedureRequest, NutritionOrder, VisionPrescription
+`orders` | REQUIRED | No | *object* | DSTU2 - FHIR Bundle of MedicationOrder, DiagnosticOrder, DeviceUseRequest, ReferralRequest, ProcedureRequest, NutritionOrder, VisionPrescription <br/> STU3 - FHIR Bundle of MedicationRequest, ReferralRequest, ProcedureRequest, NutritionOrder, VisionPrescription
 
 ### Example (DSTU2)
 
@@ -171,4 +171,3 @@ Field | Optionality | Prefetch Token | Type | Description
 Version | Description
 ---- | ----
 1.0 | Initial Release
-
diff --git a/docs/specification/1.0.md b/docs/specification/1.0.md
@@ -518,7 +518,7 @@ Per [rfc7519](https://tools.ietf.org/html/rfc7519#section-4.1.3), the `aud` valu
 
 The EHR MUST make its public key, expressed as a JSON Web Key (JWK) in a JWK Set, as defined by [rfc7517](https://tools.ietf.org/html/rfc7517). The `kid` value from the JWT header allows a CDS Service to identify the correct JWK in the JWK Set that can be used to verify the signature.
 
-The EHR MAY make its JWK Set available via a URL identified by the `jku` header field, as defined by [rfc7517 4.1.2](https://tools.ietf.org/html/rfc7515#section-4.1.2). If the `jku` header field is ommitted, the EHR and CDS Service SHALL communicate the JWK Set out-of-band.
+The EHR MAY make its JWK Set available via a URL identified by the `jku` header field, as defined by [rfc7515 4.1.2](https://tools.ietf.org/html/rfc7515#section-4.1.2). If the `jku` header field is ommitted, the EHR and CDS Service SHALL communicate the JWK Set out-of-band.
 
 An example JSON web token header and payload:
 
@@ -591,4 +591,3 @@ As another example, an extension defined on the discovery response could look li
   ]
 }
 ```
-