Generalize and move to FHIR Extensions in Core - PAS #21

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • US Da Vinci PAS (FHIR)
    • STU3
    • Financial Mgmt
    • (profiles) [deprecated]
    • Hide

      This extension would not be relevant in a general FHIR updates.  It is needed as part of the conversion process to X12.  The conversion tool won't have access to the prior version of the prior authorization request, but needs to understand whether content was added or changed so as to know how to encode the X12 record.  This is not a generalized requirement and doesn't make sense to be defined in the core specification.

      Show
      This extension would not be relevant in a general FHIR updates.  It is needed as part of the conversion process to X12.  The conversion tool won't have access to the prior version of the prior authorization request, but needs to understand whether content was added or changed so as to know how to encode the X12 record.  This is not a generalized requirement and doesn't make sense to be defined in the core specification.
    • Laurie Burckhardt/Mark Scrimshire: 31-0-0

      Comment:

      Generalize and move to FHIR Extensions in Core, rather than making this PAS Specific, or perhaps as an extension supported in Provenance to denote kinds of changes made to a request.

      Alternatively, I see no reason why this isn't simply computable from the previous edition of the resource in which it is used. Therefore, it seems reduntant. What happens to a system in which these annoations are NOT provided but where they should have been? Seems like a recipe for later problems.

      Summary:

      Generalize and move to FHIR Extensions in Core

            Assignee:
            Unassigned
            Reporter:
            Keith W. Boone
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: