Skip to content

Commit f176698

Browse files
authored
Small fixes
1 parent 0786bdd commit f176698

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
@@ -44,7 +44,7 @@ A _CDS Client_ is an Electronic Health Record (EHR), or other clinical informati
4444
Decision support is then returned to the CDS Client in the form of [_cards_](#cds-service-response), which the CDS Client MAY display to the end-user as part of their workflow. Cards may be informational, or they may provide suggestions that the user may accept or reject they may provide a [link](#link) to additional information or even launch a SMART app when additional user interaction is required.
4545

4646
## Discovery
47-
A CDS Service is discoverable via a stable endpoint by CDS Clients. The discovery endpoint includes information such as a description of the CDS Service, when it should be invoked, and any data that is requested to be prefetched.
47+
A CDS Service is discoverable via a stable endpoint by CDS Clients. The Discovery endpoint includes information such as a description of the CDS Service, when it should be invoked, and any data that is requested to be prefetched.
4848

4949
A CDS Service provider exposes its discovery endpoint at:
5050

@@ -1093,7 +1093,7 @@ For example, consider a simple `patient-view` hook that is invoked whenever the
10931093
```
10941094

10951095
Prefetch data, on the other hand, is defined by CDS Services as a way to allow the CDS Client to provide the data that a CDS Service needs as part of the initial request to the service. When the context data relates to a FHIR resource, it is important not to conflate context and prefetch. For instance, in the hook described above for opening a patient's chart, the hook context includes the id of the patient whose chart is being opened, not the full patient FHIR resource. In this case, the FHIR id of the patient is appropriate as the CDS Services may not be interested in details from the patient resource but instead other in data related to this patient.
1096-
Alternatively, a CDS Service may need the full patient resource in certain scenarios, in which case they can request it to be prefetched or fetch it as needed from the FHIR server using a prefetch template in their discovery response, such as:
1096+
Alternatively, a CDS Service may need the full patient resource in certain scenarios, in which case they can request it to be prefetched or fetch it as needed from the FHIR server using a prefetch template in their discovery response, such as:
10971097

10981098
```json
10991099
"prefetch": {

0 commit comments

Comments
 (0)