Skip to content

Commit 9a61404

Browse files
authored
small language change
discovery endpoint shall include a description, not the purpose of the CDS service Fixes #303
1 parent cc25d3b commit 9a61404

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/specification/1.0.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ CDS Hooks implementers are not required to use the Open API Specification interf
2525

2626
## Discovery
2727

28-
Developers of CDS Services SHALL provide a stable endpoint for allowing EHRs to discover available CDS Services, including information such as the purpose of the CDS Service, when it should be invoked, and any data that is requested to be prefetched.
28+
Developers of CDS Services SHALL provide a stable endpoint for allowing EHRs to discover available CDS Services, including information such as a description of the CDS Service, when it should be invoked, and any data that is requested to be prefetched.
2929

3030
A CDS Service provider SHALL expose its Discovery endpoint at"
3131

@@ -589,4 +589,4 @@ As another example, an extension defined on the discovery response could look li
589589
]
590590
}
591591
```
592-
[OAuth 2.0]: https://oauth.net/2/
592+
[OAuth 2.0]: https://oauth.net/2/

0 commit comments

Comments
 (0)