Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-42713

need to separate CDex into discrete use cases

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Highest Highest
    • US Da Vinci CDex (FHIR)
    • current
    • Payer/Provider Information Exchange
    • (many)
    • Hide

      Although we welcome specific suggestions to make the guide more coherent and recognize that separate guides for each use case may be easier for some readers, we do not think the costs of splitting up CDEX and maintaining separate guides per use case is justified at this time.  We have designed CDex with the goal of clearly delineating its transaction patterns and Attachment use cases. Furthermore, recent updates to the PAS IG document how to use CDex to get additional information and address some of the commenters' concerns.

      Show
      Although we welcome specific suggestions to make the guide more coherent and recognize that separate guides for each use case may be easier for some readers, we do not think the costs of splitting up CDEX and maintaining separate guides per use case is justified at this time.  We have designed CDex with the goal of clearly delineating its transaction patterns and Attachment use cases. Furthermore, recent updates to the PAS IG document how to use CDex to get additional information and address some of the commenters' concerns.
    • 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

        Activity

          People

            Unassigned Unassigned
            celine_lefebvre Celine Lefebvre
            Celine Lefebvre
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: