Home/ Questions/Q 8958075
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-15T15:08:14+00:00

So, I’m researching methods for building a client interface for existing EMRs. I’ve read

  • 0

So, I’m researching methods for building a client interface for existing EMRs. I’ve read tons of info on HL7, as well as the various coding schemes, but I’m still really clueless.

For anyone whose worked with an EMR before: is it possible to build a web interface that can use HTTP-POST and HTTP-GET requests to pull/push data to the server database? Or would you have a separate database for the client, say a web application, then use some interface engine like Mirth to communicate between the EMR database and the web application?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    A web service API is definitely a way to go. One benefit to this is that you can get https almost out-of-the box for encryption of data in transit.

    The way we have configured our EMR is that we have a tcp server accepting incoming hl7 messages from certain IPs which connects directly to our EMR database. This can be beneficial by separating emr and interface processes (You don’t have to restart your whole EMR if the interface goes down, for instance).

    Another good feature would be to have a token system for pseudo-authentication. This only works if you are going over a secure connection though.

    If you aren’t into writing your own tcp server (not that hard), an api-based server is probably just as good.

    EDIT: What language(s) do you think you’ll be using?

    Other things that you might run into:

    1. Some applications prefer file drops to direct calls (either url or tcp)
    2. Some vendors will have their own software that sits on a server of yours
    3. Don’t forget the ACK.
    • 0