Stream: united states
Topic: CMS Rules confusion
Shamil Nizamov (Aug 21 2021 at 18:07):
Is there anything in CMS-9115-F or similar (official) rule that specifically lists what APIs need to be implemented based on FHIR R4. I’ve seen that someone is truly confused, taking a sentence from the CMS-9115-F where it points to the base (technical) standard:
We proposed to adopt the technical standards as finalized by HHS in the ONC 21st Century Cures Act final rule (published elsewhere in this issue of the Federal Register) at 45 CFR 170.215. HHS is finalizing adoption of HL7 FHIR Release 4.0.1 as the foundational standard for APIs at 45 CFR 170.215(a)(1).
and based on that claims that, for example, the FHIR server/end-point that is built against US Core (the latest is 4.0.0 and therefore does not match FHIR 4.0.1 according to that person's view) shall support a ServiceRequest (which is the part of Prior Authorization Support) as well.
How to explain, quoting CMS rules, that FHIR 4.0.1 is just a technical standard all other APIs are built based on?
Yunwei Wang (Aug 23 2021 at 02:12):
US Core v4.0.0 is based on FHIR v4.0.1
Eric Haas (Aug 23 2021 at 14:22):
Sounds like they are confused by the versioning between the various standards FHIR Standard (4.0.1) and the implementation guide standard (in this case US Core 4.0.0).
Josh Mandel (Aug 25 2021 at 20:38):
I think the requirements are:
-
Expose the same SMART on FHIR APIs as a certified EHR would, for USCDI core data set
-
Alongside the USCDI resources, also support Coverage, ExplanationOfBenefit, and other resources needed for beneficiary access to benefits data (following CARIN BlueButton is the wa to go here, but not strictly required... yet)
Last updated: Apr 12 2022 at 19:14 UTC
