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

Need to split CDex up based on use cases

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • US Da Vinci CDex (FHIR)
    • current
    • Patient Care
    • (many)

    Description

      There is increasing pressure by the industry and HL7 to mandate CDex for prior authorization attachments.

      As it is currently written the CDex guide covers several use cases. It would be a lot cleaner for regulators to be able to mandate it for Prior Auth (as opposed to for example claims) if the CDex guide was use case specific.

      While 90% of the content would be the same, it makes a lot of sense to have one CDex guide for prior auth attachments, one for claims attachments, etc. It would also be a lot easier for the community to know what to implement in which case.

      Part of the reason we write IGs is so that business folks can digest the implications. However, because of the several and discrete use cases, the guide sometime is challenging to parse out.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: