Michael Sierra

Forum Replies Created

Viewing 5 replies – 1 through 5 (of 5 total)
  • Author
    Replies
  • in reply to: HTTP Guidance #116991
    Michael Sierra
    Participant

      Yes we are using a TCL script for the VXU messages. We were trying to use the HTTP protocol thread but couldn’t get it to work.

      But as for the QBP we are taking a similar approach to you. We are going to try and create separate epic Interfaces for each organization. We still plan to route the messages through cloverleaf at some point but are using this method as a workaround around until we can get everything figured out.

      in reply to: HTTP Guidance #116919
      Michael Sierra
      Participant

        Yes I agree. This project has been full of surprises like this.

        And yes that matches the control ID of the test message.

        in reply to: HTTP Guidance #116917
        Michael Sierra
        Participant

          We are working on a similar interface with CHIRP right now and we keep a table in cloverleaf that maps the location to their username and password. This like Jim mentioned will allow us to keep the architecture of the interface simple.

          Are you sending VXU or QBP? As far as ACKS/NAKS for VXU I will warn you that CHIRP always sends AE, even if the message is successful. If the message is not successful there will be additional error fields with more detail explaining what the issue is. Below is an example of a “ACK” from CHIRP for a successful message.

           

          MSH|^~\&|CHIRP^^|CHIRP^^|VAC^^|^^|20200528153020-0400||ACK^V04^ACK|7740168425.101180521|T|2.5.1|||NE|NE|
          MSA|AE|2|
          ERR|||0^Message accepted^HL70357|I||||Patient  with 1 vaccination accepted into vaccination staging table|

          in reply to: HTTP Interface Configuration Help #116635
          Michael Sierra
          Participant

            We weren’t able to do this using the HTTP-CLIENT  protocol. I still never figured out was wrong with our set up. We use similar set ups with other systems that work fine but CHIRP just wouldn’t accept the message.

            We ended up creating a route to a file thread pointed to dev/null. In the route we created a post proc script. In this script is where we connect to CHIRP and send the message.

            Keep in mind CHIRP acknowledges everything with an error so you may need to write code to handle those as well. Here is an example of an acknowledgment of a good message.

             

            MSA|AE|64|
            ERR|||0^Message accepted^HL70357|I||||Patient ***** “*****” with 1 vaccination accepted into vaccination staging table|

            in reply to: HTTP Interface Configuration Help #115887
            Michael Sierra
            Participant

              Thanks Jim, I have that option setup already but it looks like clovertech blocked that file. Let me try uploading it again.

              Attachments:
              You must be logged in to view attached files.
            Viewing 5 replies – 1 through 5 (of 5 total)