How closely tied should the HIM and SHR be?

Legacy openhie-shr
1

Hi Everyone,

I just wanted to kickoff the following question from Mark Tucker’s email threads on this list:

How closely should the HIM and SHR be tied together? Where should the boundary be around them?

My feeling is very closely, given the need for splitting data up to stores such discrete or document,

tasks which might be better in the HIM rather than a little “logic processor” as part of the SHR (or not?).

I look forward to all responses :slight_smile:

Regards

Hannes

···

–
Hannes Venter
Software Developer, Jembi Health Systems | SOUTH AFRICA
Mobile: +27 73 276 2848 | Office: +27 21 701 0939 | Skype: venter.johannes
E-mail: hannes@jembi.org

2

Hi Odysseas, thank you for the great comments. Just cc’ing the list…

···

On Mon, Apr 22, 2013 at 1:07 PM, Odysseas Pentakalos, Ph.D. odysseas@sysnetint.com wrote:

Hi Hannes,

  My view is that the HIM provides the "glue" that ties together all

the other components of the OpenHIE.

  - It provides the data transformation services that may be needed

to adapt the messages in and out of the overall exchange to the
interfaces supported by

  any of the exchanges

  - It provides orchestration needed in the processing of individual

messages by one or more registries

  - It can provide the distribution that may be needed to support

multiple instances of the SHR (or the CR)

  - It provides centralized handling of security (and probably

adapts to the security scheme of the individual CRs)

  - It can provide transaction monitoring and performance monitoring

services since it sees every message go by

  In summary, I see the HIM forming the perimeter around the other

registries which would make the discussion

  about how to best store the clinical data in the SHR the focus of

only the SHR and which messaging format

  to use to exchange data the focus of the HIM.



  Best regards,

  Odysseas




  On 04/22/2013 06:22 AM, Hannes Venter wrote:

Hi Everyone,

      I just wanted to kickoff the following question from Mark

Tucker’s email threads on this list:

  •          How closely should the HIM and SHR be tied together?

Where should the boundary be around them?*

        My feeling is very closely, given the need for splitting

data up to stores such discrete or document,

        tasks which might be better in the HIM rather than a

little “logic processor” as part of the SHR (or not?).

I look forward to all responses :slight_smile:

Regards

Hannes

–
Hannes Venter
Software Developer, Jembi Health Systems | SOUTH AFRICA
Mobile: +27 73 276 2848 | Office: +27 21 701 0939 |
Skype: venter.johannes
E-mail: hannes@jembi.org

  --

  You received this message because you are subscribed to the Google

Groups “Shared Health Record (OpenHIE)” group.

  To unsubscribe from this group and stop receiving emails from it,

send an email to openhie-shr+unsubscribe@googlegroups.com.

  For more options, visit [https://groups.google.com/groups/opt_out](https://groups.google.com/groups/opt_out).

-- Odysseas Pentakalos, Ph.D., PMP
Chief Technology Officer
SYSNET International, Inc.
2930 Oak Shadow Drive
Oak Hill, Virginia 20171
mailto:odysseas@sysnetint.com
(703) 855-2029

–
Hannes Venter
Software Developer, Jembi Health Systems | SOUTH AFRICA
Mobile: +27 73 276 2848 | Office: +27 21 701 0939 | Skype: venter.johannes
E-mail: hannes@jembi.org