DG1 Segment to ZRV Segment

This topic has 7 replies, 3 voices, and was last updated 10 years, 7 months ago by Sallie Turner.

Creator

Topic
May 9, 2014 at 3:44 pm #54201
Jared Miller
Participant
Hi everyone,

Working on a BAR^P01 interface between Optum CAC and McKesson Star and getting stuck on a particular spot so looking for some help. In the DG1 segments, anytime there is a reason for visit diagnosis I need remove that instance of the segment from the message but at the same time move DG1-2 (will be I9 or I10) and DG1-3 (code) in a ZRV segment.

If there is only one DG1 that is a reason for visit then I’m ok, but if there is more than one is where I’m getting stumped. Instead of having a ZRV segment for each DG1, I need to add an additional field to the ZRV.

See attachment for a better visual of what I’m trying to do. Let me know if you need further clarification, thanks!
Creator

Topic

Viewing 6 reply threads

Author

Replies
- May 10, 2014 at 2:57 am #80567
  Jim Kosloskey
  Participant
  Jared,
  
  Is the ZRV field in question defined as repeating?
  
  If not how are the ‘pieces’ to be represented – as components?
  
  email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
- May 12, 2014 at 2:51 pm #80568
  Jared Miller
  Participant
  Jim,
  
  The ZRV segment is defined at optional/repeating, but the fields of the ZRV are just optional currently.
- May 12, 2014 at 6:51 pm #80569
  Jim Kosloskey
  Participant
  I am assuming the : is your field separator.
  
  Then it appears in the ZRV you have the first field is the coding system ID, the second field is a code, and the third field (maybe ore are additional fields).
  
  Is there a limit to the number of codes the receiving system will honor or can there be any number?
  
  From your example it looks like the ZRV is constructed for some sort of maximum number of codes.
  
  A more useful construct might be for the code field to repeat but of course the receiving system would need to support that.
  
  email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
- May 13, 2014 at 2:43 pm #80570
  Jared Miller
  Participant
  Yes, : the field separator for Star. I will have to clarify with the vendor, but according to their specs the ZRV will accept 3 codes. The segment needs to repeat if there are both ICD-9 and ICD-10 codes.
  
  Here’s the vendor spec for the ZRV:
  
  ZRV
- May 13, 2014 at 3:09 pm #80571
  Jim Kosloskey
  Participant
  Unless I am misunderstanding, I think you will not be able to use ITERATE on the inbound diagnosis codes to get the individual codes to the ZRV.
  
  Instead use direct addressing notation.
  
  So COPY the DG1 field something like this:
  
  COPY ….DG1(0).#n –> ZRV(0).#2
  
  COPY ….DG1(1).#n –> ZRV(0).#3
  
  COPY ….DG1(2).#n –> ZRV(0).#4
  
  Any iteration then of the DG1 which does not exist will populate the associated ZRV field with null and (if the ZRV-2 through ZRV-4 fields are defined as optional) no separators will appear.
  
  I think this should work for you.
  
  email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
- May 13, 2014 at 5:16 pm #80572
  Jared Miller
  Participant
  Well since I won’t know how many DG1 segments there will be in a given message or in which DG1 segment will have a ‘VI’ in DG1-6 (which indicates a reason for visit diagnosis) I think I have to use the ITERATE function, don’t I?
- May 14, 2014 at 5:39 pm #80573
  Sallie Turner
  Participant
  Jared,
  
  I already worked out this whole thing. Email me at sturner@gwinnettmedicalcenter.org and I can send you the variant, procs and xlate that I used to format the messages for Star. It was NOT pretty or easy!
Author

Replies

Viewing 6 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.