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

Change the LineNumber Extension

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci CDex (FHIR)
    • Payer/Provider Information Exchange
    • CDex Task Attachment Request Profile
    • Hide

      remap as follows (based on the PAS mappings in X12 glass):

       

      Data Element CDex Request Attachment Task Profile Element X12 277RFAI-v6020 X12n 278 Response-v5010 Request Attachments Comments
      Tracking ID Task.identifier Loop: 2200D Segment: TRN02 Notes: TRN01 = "1" Loop: 2000E - Patient Event Level or Loop: 2000F Service Level Segment: TRN02 Notes: TRN01 = "1", patient event tracking numberNotes: TRN01 = “1”: Payer Supplied TRN01 = “2” : Provider Supplied (echoed back) Notes: TRN01 = "1" or TRN01 = "2" Payer-assigned tracking/control number

       

      and 

       

      Line Item(s) “code” Task.input.extension Loop: 2220D Notes: SVC01 = id code qualifier, SVC02 is the claim amount, SVC04 is REV Code, Does not list line item Loop: 2000F Segment: TRN02 Notes: TRN01 = "1" Loop: 2000F Segment: HL01 Claim/prior authorization line item numbers

      and 

       

      LOINC Attachment Code “code” Task.input Loop: 2220D Segments: STC01-02, STC10-02, STC11-02 Loop: 2000E - Patient Event Level or Loop: 2000F Service Level Segment: HI (LOINC) Segment: HI?? or Segment: PWK Loop: 2000F  or Segment: PWK01 Report Type Codes  Notes: Clarify! LOINC attachment codes or PWK01 attachment codes
      Show
      remap as follows (based on the PAS mappings in X12 glass):   Data Element CDex Request Attachment Task Profile Element X12 277RFAI-v6020 X12n 278 Response-v5010 Request Attachments Comments Tracking ID Task.identifier Loop: 2200D Segment: TRN02 Notes: TRN01 = "1" Loop: 2000E - Patient Event Level or Loop: 2000F Service Level Segment: TRN02   Notes: TRN01 = "1", patient event tracking number .  Notes: TRN01 = “1”: Payer Supplied TRN01 = “2” : Provider Supplied (echoed back)   Notes: TRN01 = "1" or TRN01 = "2" Payer-assigned tracking/control number   and    Line Item(s) “code” Task.input.extension Loop: 2220D Notes: SVC01 = id code qualifier, SVC02 is the claim amount, SVC04 is REV Code, Does not list line item Loop: 2000F Segment: TRN02 Notes: TRN01 = "1"   Loop: 2000F Segment: HL01 Claim/prior authorization line item numbers and    LOINC Attachment Code “code” Task.input Loop: 2220D Segments: STC01-02, STC10-02, STC11-02 Loop: 2000E - Patient Event Level or Loop: 2000F Service Level Segment: HI (LOINC) Segment: HI?? or Segment: PWK Loop: 2000F   or Segment: PWK01 Report Type Codes   Notes: Clarify! LOINC attachment codes or PWK01 attachment codes
    • Enhancement
    • Non-compatible

    Description

      Proposal:

      For the CDEX Task, Change the extensionServiceLineNumber (http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-serviceLineNumber)

      in Task to ItemTraceNumber extension (http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-itemTraceNumber)

       

       

      Rationale: 

      Per the CDex mapping of X12n 278 Response-v5010,  a specific line number associated with the attachment maps to the Loop: 2000F Segment: TRN02 Notes: TRN01 = “1”. 

      Per the X12 spec: 

       

      TRN

      To uniquely identify a transaction to an application

      TRN02 :

      Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

       

      Therefore it is an identifier, and not an integer.

      Attachments

        Activity

          People

            Unassigned Unassigned
            ehaas Eric Haas
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: