Add a line to the profiles that they are derived from US Core - PAS #113

XMLWordPrintableJSON

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

      At this point in time, the PAS-specific profiles are not derived from US-Core profiles. Because of "minimum necessary" rules, we don't want to inherit any additional requirements from US-Core. The focus of PAS is strictly on what data elements are needed to populate the 278. We may look at aligning portions of those profiles where code translation on the payer side would make it easier for providers to populate the prior authorization requests, but we don't want to include additional data elements. The alignment work is already in progress and will continue as EHRs are exposed to the X12 terminology requirements and provide feedback about where mapping is/is not possible.

      We will add a section to each of the profiles that describes the relation of the profile to the corresponding U.S. Core profile - including specifically highlighting any additional data elements and/or conflicting requirements where they exist.

      Show
      At this point in time, the PAS-specific profiles are not derived from US-Core profiles. Because of "minimum necessary" rules, we don't want to inherit any additional requirements from US-Core. The focus of PAS is strictly on what data elements are needed to populate the 278. We may look at aligning portions of those profiles where code translation on the payer side would make it easier for providers to populate the prior authorization requests, but we don't want to include additional data elements. The alignment work is already in progress and will continue as EHRs are exposed to the X12 terminology requirements and provide feedback about where mapping is/is not possible. We will add a section to each of the profiles that describes the relation of the profile to the corresponding U.S. Core profile - including specifically highlighting any additional data elements and/or conflicting requirements where they exist.
    • Kathleen Connor / Robert Dieterle: 20-0-1
    • Clarification
    • Non-substantive

      Existing Wording: It is my assumption that any profile for PAS of a resource that exists in US Core is based on US Core but there is ino reference to it, for example Condition, Encounter, Location, etc

      Proposed Wording: At a line to the profiles that they are derived from US Core

      Summary:

      Add a line to the profiles that they are derived from US Core

            Assignee:
            Unassigned
            Reporter:
            Linda Michaelsen
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: