Stream: implementers
Topic: US Core Server CapabilityStatement V/s US Core Client Capabi
Vish (Apr 09 2021 at 10:54):
US Core Server CapabilityStatement V/S US Core Client CapabilityStatement,
1.What is difference
- While implementing Search Parameters, should we include shall and should from client as well? because Should implement search criteria for client capability statement is reflected as May in server capability statement
e.g. Should V/s May
As per US Core Server CapabilityStatement
For CarePlan Resource i
Search Parameter Summary:
Conformance Parameter Type Example
MAY category token GET [base]/CarePlan?category=[system]|[code]
MAY date date GET [base]/CarePlan?date=[date]
MAY patient reference GET [base]/CarePlan?patient=[patient]
MAY status token GET [base]/CarePlan?status=[status]
where as as per US Core Client CapabilityStatement
For CarePlan Resource
Search Parameter Summary:
Conformance Parameter Type Example
SHOULD category token GET [base]/CarePlan?category=[system]|[code]
SHOULD date date GET [base]/CarePlan?date=[date]
SHOULD patient reference GET [base]/CarePlan?patient=[patient]
SHOULD status token GET [base]/CarePlan?status=[status]
- For population search methods per Argonaut project what queries FHIR should support, do we have link of those methods or queries?
Lloyd McKenzie (Apr 09 2021 at 16:27):
- Clients are systems that are querying for data or initiating creation or update of data. Servers are systems that 'own' data and respond to search, create and update requests.
- It's possible for a system to act as both client and server - i.e. you access data from other systems (as a client) and provide data to other systems (as a server). You would be expected to comply with the expectations for the role you're acting in at the time.
Last updated: Apr 12 2022 at 19:14 UTC
