Clovertech

ICD10

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › ICD10

  • Creator
    Topic
  • September 10, 2014 at 5:13 pm #54376
    Bob Schmid
    Participant

      Need some support for you all.

      We have, what I belive to be, an outside consulting group run amuck on the ICD10 project.

      They are now asking us to REMOVE all DRG information if the app analyst on the receiving sending end says its not used or needed?…

      so out of 2000 interfaces…all receive adt…and gues what…..>DG1 and DRG in most cases…..so we are not being asked to remove this information because it might be a HIPPA violation or ..just because they dont need it.

      Can anyone say “180”…….I see proprietary FRL’s in our future for all interfaces because of this…..or beginnig to remove all fields not used :-/

      Quite a bit of testing and remediation.  Not sure…why the “standard”

      and yes..we have Business service agreements with our vendors and subscribe to HIPPA agreements…..whats next?…patient name, address, sex, …….”Secret agent man….they;re giving you a number and theyll take away your name….” 👿  ðŸ‘¿  ðŸ‘¿  ðŸ‘¿  ðŸ‘¿  ðŸ‘¿  ðŸ‘¿

      Please post your thoughts on how firm I should stand or whether I should accept this as a good practice…and do what I’m told.

    • Creator
      Topic
    Viewing 3 reply threads
    • Author
      Replies
      • September 10, 2014 at 5:53 pm #81223
        Vince Angulo
        Participant

          DRG is a mushy example… Most receiving organizations will ignore a received DRG at best as they will almost always want to use their own grouper to calculate the DRG for their own use. I’m not surprised one of them just asked to have it not be sent at all.

        • September 10, 2014 at 6:29 pm #81224
          Jim Kosloskey
          Participant

            There was recently a fairly lively discussion vis-

            email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

          • September 11, 2014 at 1:33 pm #81225
            Bob Richardson
            Participant

              Greetings,

              Maybe too simplistic here:  why not just tack on a post xlate TCL to pop off the DRG segments?   We have a simple TCL program called “tps_rem_segs_fr_msg” that takes an argument list of what to drop

              as some customers come up with exactly what you describe.

              Ok… too simple?

              Beats changing hundreds of configurations.

              Back to my nightmares now…

            • September 16, 2014 at 2:57 pm #81226
              Bob Schmid
              Participant

                No problem with the technical if we need to start removing this information.

                Thought it is fascinating how history repeats itself…

            • Author
              Replies
            Viewing 3 reply threads
            • The forum ‘Cloverleaf’ is closed to new topics and replies.