Stream: implementers
Topic: US Core Search Parameter
Chetana Nayyar (Aug 20 2021 at 07:52):
For CMS compliance what is the requirement for search paramaters; is it required to support mandatory and optional search parameters?
http://hl7.org/fhir/us/core/StructureDefinition-us-core-allergyintolerance.html
Mandatory Search Parameters:
The following search parameters and search parameter combinations SHALL be supported:
SHALL support searching for all allergies for a patient using the patient search parameter:
GET [base]/AllergyIntolerance?patient={Type/}[id]
Optional Search Parameters:
The following search parameter combinations SHOULD be supported:
SHOULD support searching using the combination of the patient and clinical-status search parameters:
GET [base]/AllergyIntolerance?patient={Type/}[id]&clinical-status={system|}[code]
@Lloyd McKenzie @Grahame Grieve Kindly help pointing to the concerned teammember
Lloyd McKenzie (Aug 20 2021 at 13:14):
Does CMS mandate conformance to the US-Core implementation guide? If so, as a server, the answer would be 'yes'.
Daniel Venton (Aug 20 2021 at 13:41):
My understanding is that if you comply with USCore then you comply with CMS but CMS doesn't require the use of USCore. CMS doesn't dictate how it is to be done, just that it shall be done and it shall be documented so people can use it. For USCDI, Patient Access API is a different thing and it does require FHIR, CARIN, UsCore, pdex formulary. https://www.cms.gov/Regulations-and-Guidance/Guidance/Interoperability/index
(Although I kinda know FHIR, I am not a lawyer)
Last updated: Apr 12 2022 at 19:14 UTC
