[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-573404-105":53,"doc-detail-573404-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","cds-service-discovery-get-request-and-response-cheat-sheet","CDS Service Discovery - GET - Request and Response Cheat Sheet","","CDS Service Discovery documentation cheat sheet describing how to call CDS Hooks endpoints for retrieving and invoking CDS services. It specifies the GET /cds-services response structure, including required fields like hook, title, description, id, and optional prefetch FHIR query parameters. It also details the POST /cds-services/{id} request body requirements such as hook, hookInstance, fhirServer, fhirAuthorization, context, and prefetch, plus the response format using cards, sources, suggestions, actions, and links.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/cds-service-discovery-get-request-and-response-cheat-sheet/573404/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/cds-service-discovery-get-request-and-response-cheat-sheet/573404.png","ImageObject",442,249,{"name":88,"@type":89},"Rizky","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-17","2026-10-14",true,{"@type":98,"interactionType":99,"userInteractionCount":76},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What does CDS Service Discovery GET /cds-services return?","Question",{"text":108,"@type":109},"It returns a services array where each CDS Service includes required hook, title, description, and id fields, and may include optional prefetch parameters for FHIR queries.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"What fields are required in a CDS Service Request POST /cds-services/{id}?",{"text":113,"@type":109},"The request requires hook and hookInstance, and it requires fhirAuthorization context data plus any hook-specific contextual data and optional prefetch values.",{"name":115,"@type":106,"acceptedAnswer":116},"How is a CDS Service Response structured?",{"text":117,"@type":109},"The response contains cards, and each card includes a required summary, a required indicator, a required source, and optional details, suggestions, and links. Suggestions can include actions such as create/update/delete with resource or id details.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},573404,1792242384,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":76,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":9,"language":135,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":136,"faqs":137,"seo_title":138,"seo_description":61,"update_tm":139,"read_time":4},962085564807,"https://ap-avatar.wpscdn.com/davatar_6f874abed73319feea01a86fa6f0fab8","CDS Service Discovery-GET {baseUrl}/cds-services  \nResponse Body  \nservices -An array of CDS Services  \nCDS Service:  \nhook-REQUIRED-hook this service should be invoked on title-RECOMMENDED-human-friendly name of this service description-REQUIRED-description of this service  \nid-REQUIRED- {id} portion of service URL:{baseUrl}/cds-services/{id}  \nprefetch-OPTIONAL-Object containing key/value pairs of FHIR queries that this service is requesting the CDS Client to include on service calls  \n{  \n\"services\": [  \n{  \n\"hook\": \"hook-noun-verb\",  \n\"title\": \"CDS Service Example\",  \n\"description\": \"An example of a CDS Service that returns a card\",  \n\"id\": \"patient-greeter\",  \n\"prefetch\": {  \n\"patientToGreet\": \"Patient/{{context.patientId}}\"  \n}  \n}  \n]  \n}  \nCDS Service Request-POST {baseUrl}/cds-services/{id}  \nRequest Body  \nhook - REQUIRED - hook that triggered this CDS Service call hookInstance - REQUIRED - UUID for this hook call  \nfhirServer -OPTIONAL-base URL for CDS Client’s FHIR server  \nfhirAuthorization -OPTIONAL-structure with FHIR Authorization information for the above url context - REQUIRED - hook-specific contextual data  \nprefetch -OPTIONAL-FHIR data prefetched by the CDS Client  \nFHIR Authorization  \naccess_token - REQUIRED -OAuth 2.0 access token token_type - REQUIRED -fixed value: Bearer  \nexpires_in - REQUIRED - lifetime in seconds of the access token  \nscope - REQUIRED -scopes the access token grants to the CDS Service  \nsubject - REQUIRED -OAuth 2.0 client id of the CDS Service’s auth server registration {  \n\"hook\": \"hook-noun-verb\",  \n\"hookInstance\": \"d1577c69-dfbe-44ad-ba6d-3e05e953b2ea\",  \n\"fhirServer\": \"[https://fhir.client.com/version](https://fhir.client.com/version)\",  \n\"fhirAuthorization\": {  \n\"access_token\": \"opaque-token\",  \n\" . . . \": \"\u003Csnipped for brevity>\"  \n},  \n\"context\": {  \n\"userId\": \"Practitioner/example\",  \n\" . . . \": \"\u003Csnipped for brevity>\"  \n},  \n\"prefetch\": {  \n\"patientToGreet\":{  \n\"resourceType\": \"Patient\",  \n\" . . . \": \"\u003Csnipped for brevity>\"  \n}  \n}  \n}  \nCDS Service Response Body  \ncards - REQUIRED - an array of Cards with a combination of information, suggested actions, and links  \nCard:  \nsummary - REQUIRED - \u003C140-character summary sentence for display to the user inside of this card detail -OPTIONAL-optional detailed information to display (GitHub Flavored Markdown)  \nindicator - REQUIRED - urgency/importance of what this card conveys (info/warning/critical) source - REQUIRED -grouping structure for the Source of information displayed on this card suggestions -OPTIONAL- array of Suggestions for changes in the context of the current activity  \nselectionBehavior -OPTIONAL-intended behavior of the suggestions. If suggestions present, value must be at-most-one links -OPTIONAL-array of Links to suggest an app or other additional information  \nSource:  \nlabel - REQUIRED -short, human-readable label to display source of the card’s information  \nurl -OPTIONAL-optional absolute URL to load to learn more about the organization or data set  \nicon -OPTIONAL-absolute url for an icon for the source of this card (100x100 pixel PNG without any transparent regions)  \nSuggestion  \nlabel - REQUIRED - human-readable label to display for this suggestion uuid -OPTIONAL-unique identifier for auditing and logging suggestions actions -OPTIONAL-array of suggested Actions (logically AND’d together)  \nAction:  \ntype - REQUIRED -type of action being performed (create/update/delete) description - REQUIRED - human-readable description of the suggested action resource -OPTIONAL-FHIR resource to create/update or id of resource to delete  \nLink:  \nlabel - REQUIRED - human-readable label to display url - REQUIRED - URL to GET when link is clicked  \ntype - REQUIRED -type of the given URL (absolute/smart)  \nappContext -OPTIONAL-additional context to share with a linked SMART app  \n{  \n\"cards\": [  \n{  \n\"summary\": \"\u003C140 char Summary Message\",  \n\"detail\": \"optional GitHub Markdown details\",  \n\"indicator\": \"info\",  \n\"source\": ","cbCaihL8SYp3ehuo","https://ap.wps.com/l/cbCaihL8SYp3ehuo","pdf",163918,"English","# CDS Service Discovery\n## GET /cds-services\n## POST /cds-services/{id}\n## Response format: cards, suggestions, actions, links","[{\"question\":\"What does CDS Service Discovery GET /cds-services return?\",\"answer\":\"It returns a services array where each CDS Service includes required hook, title, description, and id fields, and may include optional prefetch parameters for FHIR queries.\"},{\"question\":\"What fields are required in a CDS Service Request POST /cds-services/{id}?\",\"answer\":\"The request requires hook and hookInstance, and it requires fhirAuthorization context data plus any hook-specific contextual data and optional prefetch values.\"},{\"question\":\"How is a CDS Service Response structured?\",\"answer\":\"The response contains cards, and each card includes a required summary, a required indicator, a required source, and optional details, suggestions, and links. Suggestions can include actions such as create/update/delete with resource or id details.\"}]","CDS Service Discovery - GET - Request and Response Cheat Sheet | PDF",1791939189]