Michael Bossart

Forum Replies Created

Viewing 4 replies – 1 through 4 (of 4 total)
  • Author
    Replies
  • in reply to: HTTP Guidance #116921
    Michael Bossart
    Participant

      I was just informed yesterday that Epic, our HIS, can do this now with multiple connections, so we do not have to go through Cloverleaf.  It’s a bit disappointing as I really wanted to get a webservice interface “under my belt”, but realistically, this wasn’t the best time to do it, since this all has to be done by the end of June, and this would be pretty tight figuring everything out by the end of June.

      I was also thinking that since every connection goes to the same URL, and just the username/password changes that there should be a way to dynamically change that based on a message.

      @Michael Sierra, I’d be interested in seeing what you came up with, if you able to share; if not, I understand as well.  From your other thread, you doing all this via tcl script and not using the web service thread protocol?

       

      Thanks,

      Mike

      in reply to: HTTP Guidance #116906
      Michael Bossart
      Participant

        Thanks Jim,

        I’m trying to get confirmation from my Epic resource regarding the synchronous vs asynchronous.

        As for the state acknowledgments, I’m also trying to get example of those, since they are currently captured in Epic and not displayed.

        …So not much at this point, just wanted to acknowledge and thank you for the reply.

        in reply to: Cloverleaf 19.1.0.1 issue with iterate variables in Xlate #113494
        Michael Bossart
        Participant

          Well, it’s hard to believe, but I think I found the issue.  In doing the above testing, I was recreateing the iterates and saving different versions.  I later starting doing some diffs on the xlt files.  Then I saw that the xlt that was failing had the first iterate type as list, not segment.  Fixing that, everything still runs fine in 19, even reusing the same iterate variable.  I can’t believe how much time I just wasted on this issue, good thing it’s Friday.

           

          I still think we will go back and fix all the iterate variables, but it’s nice to know that things actually do function fine converting from 6.1.2 to 19.1.0.1.

           

          If anything, I uncovered that in 6.1.2 you can define an iterate for a segment as a list and it still functions, but in 19 it doesn’t, which is more of a bug with 6.1.2.

           

          If the admins would like to delete this thread I understand, I don’t want to have misinformation out there.

          in reply to: Cloverleaf 19.1.0.1 issue with iterate variables in Xlate #113492
          Michael Bossart
          Participant

            After the first iterate (and before the next iterate trying to use %s1), echoing $%s1 outputs 0

          Viewing 4 replies – 1 through 4 (of 4 total)