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

scope

    XMLWordPrintableJSON

Details

    • Change Request
    • Resolution: Persuasive with Modification
    • Highest
    • US Da Vinci CDex (FHIR)
    • 2.0.0-ballot
    • Patient Care
    • STU
    • Background
    • 2.6.4
    • Hide

      re: "STU2 level of maturity, given STU1 was only published a few days prior to the public ballot period?"

      STU is a ballot grouping or sequence and not an indication of maturity.  We will add maturity level indicators (FMM) to the guide.

       

      re:  " how Payer systems associate attachments to and processes the claim or prior authorization is out of scope"

      Clarify that the process how to associate the information with the original Claim/PA is OOS, not the data needed for association which is documented in the IG.

      Show
      re: "STU2 level of maturity, given STU1 was only published a few days prior to the public ballot period?" STU is a ballot grouping or sequence and not an indication of maturity.  We will add maturity level indicators (FMM) to the guide.   re:  " how Payer systems associate attachments to and processes the claim or prior authorization is out of scope" Clarify that the process how to associate the information with the original Claim/PA is OOS, not the data needed for association which is documented in the IG.
    • Eric Haas/Jay Lyle: 7-0-1
    • Clarification
    • Non-substantive

    Description

      The last sentence of the Background section states that how Payer systems associate attachments to and processes the claim or prior authorization is out of scope. However, later in the guide there is a lot of information about association. Can you explain why the out of scope statement? Further, is it appropriate that CDex is already at an STU2 level of maturity, given STU1 was only published a few days prior to the public ballot period?

      Attachments

        Issue Links

          is duplicated by

          Technical Correction - A non-substantive change to correct an obvious error with a non-debatable solution. E.g. Correcting a typo, grammar issue, formatting problem, broken tool function, incorrectly coded formal constraint, etc. FHIR-38322 Clarification regarding reassociation being out of scope

          • Highest - This problem will block progress.
          • Duplicate
          is voted on by

          Ballot Vote - The designation of a comment about a specification as related to an overall Ballot Submission BALLOT-39934 Negative - Celine Lefebvre : 2022-Sep-FHIR IG CDex R1 STU

          • Balloted
          mentioned in

          Page Loading...

          Activity

            People

              Unassigned Unassigned
              celine_lefebvre Celine Lefebvre
              Andrea Preisler, Celine Lefebvre
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: