Details
-
Change Request
-
Resolution: Not Persuasive
-
Highest
-
US Da Vinci CDex (FHIR)
-
current
-
Payer/Provider Information Exchange
-
(many)
-
-
Kyle Pelkey/Chris Johnson:15-0-1
Description
We highly recommend having several CDex implementation guides based on use case.
While the bulk of the content would be the same, having discrete IGs for each use case (e.g. Prior Auth, Claims, etc.) would make implementation a lot easier and clarify expectations. I have been on several calls where people have been confused as to when certain elements apply to claims vs. PA.
Furthermore, from a regulatory standpoint, it would be a lot cleaner to mandate CDex if it was limited to the use case in question. In order to "sell" CDex as an official piece of the burden reduction suite, from both a policy and technical standpoint, it would be helpful for it to be specifically tailored to PA.
Attachments
Issue Links
- is duplicated by
-
FHIR-42410 Need to split CDex up based on use cases
- Duplicate
- mentioned in
-
Page Loading...