Is it intentional to bind processNote.text to a discrete code set, or is it meant to be a true textual field?

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Highest
    • US CARIN Real-time Pharmacy Benefit Check (RTPBC) (FHIR)
    • Pharmacy
    • RTPBC Response Profile (ClaimResponse) [deprecated]
    • Profiles and Extensions
    • Hide

      Add an extension (coding) to ClaimRespones.item.adjudication and ClaimResponse.addItem.adjudication elements called "benefitRestriction":

      • coding
      • bind to the value set currently named "coverage-summary" (see below: rename to "benefit-restriction")

      Modify the "coverage-summary" code system / value set names to "benefit-restriction"

      Show
      Add an extension (coding) to ClaimRespones.item.adjudication and ClaimResponse.addItem.adjudication elements called "benefitRestriction": coding bind to the value set currently named "coverage-summary" (see below: rename to "benefit-restriction") Modify the "coverage-summary" code system / value set names to "benefit-restriction"
    • Pooja Babbrah / Jean Duteau : 8-0-1
    • Enhancement
    • Compatible, substantive
    • 0.1.0

      Is it intentional to bind processNote.text to a discrete code set, or is it meant to be a true textual field? If the former, should the element name be changed to something like processCode, coverageStatus, or some sort?

      Existing Wording:

      ClaimResponse > processNote > text (string type) binding to CARIN RTPBC Coverage Summary Value Set

            Assignee:
            Unassigned
            Reporter:
            Daniel Zhang
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: