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

Increase binding strength for place of service codes

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Medium Medium
    • US CARIN Blue Button (FHIR)
    • current
    • Financial Mgmt
    • C4BB Explanation Of Benefit
      C4BB ExplanationOfBenefit Professional NonClinician
    • Hide

      Place of Service Codes are only applicable for Professional and NonClinician EOB and Oral EoB. Institutional locations are placed in supportingInfo typeofbill slice.

      Additional guidance requested via FHIR-34087 - Add guidance for use of place of service and type of bill

      Show
      Place of Service Codes are only applicable for Professional and NonClinician EOB and Oral EoB. Institutional locations are placed in supportingInfo typeofbill slice. Additional guidance requested via  FHIR-34087 - Add guidance for use of place of service and type of bill
    • Corey Spears / Mary Kay McDaniel : 13-0-2
    • Clarification
    • Non-substantive

    Description

      US Realm claims and EOBs are supposed to use the CMS Place of Service Code Set. I recommend we increase the terminology binding conformance level for ExplanationOfBenefit.item.location and ExplanationOfBenefit.addItem.location from example to extensible (or perhaps even required), and change the value set to CMSPlaceofServiceCodes

      Currently the C4BB ExplanationOfBenefit Professional NonClinician profile is inconsistent with our other EOB profiles because it has ExplanationOfBenefit.item.location conformance of required and is bound to the value set linked above. All of our EOB profile location element bindings should be consistent.

      Attachments

        Activity

          People

            Unassigned Unassigned
            nradov Nick Radov
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: