OpenHIE Architecture Call - Friday, July 27 - Canceled

The OpenHIE Architecture call scheduled for Friday, July 27 has been canceled since many people will be preparing for travel to the OpenHIE Community Meeting in Tanzania.

The next regularly-scheduled call will take place on Monday, August 13th.

Thanks!

**Michelle Cox ** |****Program Coordinator, Global Health Informatics

image001.png

1101 West Tenth Street

Indianapolis, IN 46202

Tel 317-274-9324 | Fax 317-274-9305

Skype ID: miclcox | Facebook.com/regenstriefinstitute |
www.regenstrief.org

My normal work hours are Monday – Friday, 7:15 a.m. – 4:00 p.m. Eastern Time

Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged information and are intended solely for the use of the named addressee(s).
Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and State laws prohibit you from making further disclosure of such information
without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical or other information is not sufficient for this purpose.

If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention, disclosure, copying, distribution or use of this information
by anyone other than the intended recipient is strictly prohibited.

Dear architects,

I have a few questions and apologies if the answers are available somewhere and I have not done my homework (too busy hehe):

Is there a recommended structure of the SHR?

Are the data in the SHR identifiable or de-identified? why and why not?

How will the SHR submit data to the HMIS? is this via ADX? who defines the ADX schema?

TIA

image001.png

···

On Fri, Jul 20, 2018 at 9:19 PM, Cox, Michelle Louise miclcox@regenstrief.org wrote:

The OpenHIE Architecture call scheduled for Friday, July 27 has been canceled since many people will be preparing for travel to the OpenHIE Community Meeting in Tanzania.

The next regularly-scheduled call will take place on Monday, August 13th.

Thanks!

**Michelle Cox ** |****Program Coordinator, Global Health Informatics

1101 West Tenth Street

Indianapolis, IN 46202

Tel 317-274-9324 | Fax 317-274-9305

Skype ID: miclcox | Facebook.com/regenstriefinstitute |
www.regenstrief.org

My normal work hours are Monday – Friday, 7:15 a.m. – 4:00 p.m. Eastern Time

Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged information and are intended solely for the use of the named addressee(s).
Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and State laws prohibit you from making further disclosure of such information
without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical or other information is not sufficient for this purpose.

If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention, disclosure, copying, distribution or use of this information
by anyone other than the intended recipient is strictly prohibited.

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Alvin B. Marcelo, MD, FPCS, CGEIT, TOGAF, COBIT5 F/I, ArchiMate

https://orcid.org/0000-0001-6250-9169

Disclaimer:

*** This
e-mail, together with any attachments, is intended for the named recipients only and is confidential. It may also be privileged or otherwise protected by law. If you have received it in error, please notify the sender immediately by reply e-mail and delete it and any attachments from your system. You may
not copy or disclose its contents to anyone.***

Hi Alvin,

I’l try answer were I can. The structure for the SHR will depend on the use cases being implemented but it is recommended to try use content profiles where possible that standardise the data that is captured and often structures it as a document such as a CDA document. Although, more recent HIEs are preferring to go the FHIR route and profiling FHIR for the implementation needs may be a more moderns way to go. It is also possible to consume documents in FHIR.

The data in the SHR is identifiable as it is designed to be the central store for a patient’s medical records (or at least a summary of them) because of that it needs to be identifiable so that data can be queried for a particular patient. It also relies on their being an MPI/Client registry in place to be able to find that patient and resolve their identity.

ADX would be the preferred method to submit to the HMIS. The schema would be implementation specific in most cases and would need to be agreed on by the implementing partners.

Hope this helps.

Cheers,

Ryan

image001.png

···

On Fri, Jul 20, 2018 at 9:19 PM, Cox, Michelle Louise miclcox@regenstrief.org wrote:

The OpenHIE Architecture call scheduled for Friday, July 27 has been canceled since many people will be preparing for travel to the OpenHIE Community Meeting in Tanzania.

The next regularly-scheduled call will take place on Monday, August 13th.

Thanks!

**Michelle Cox ** |****Program Coordinator, Global Health Informatics

1101 West Tenth Street



Indianapolis, IN 46202

Tel 317-274-9324 | Fax 317-274-9305

Skype ID: miclcox | Facebook.com/regenstriefinstitute |
www.regenstrief.org

My normal work hours are Monday – Friday, 7:15 a.m. – 4:00 p.m. Eastern Time

Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged information and are intended solely for the use of the named addressee(s).
Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and State laws prohibit you from making further disclosure of such information
without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical or other information is not sufficient for this purpose.

If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention, disclosure, copying, distribution or use of this information
by anyone other than the intended recipient is strictly prohibited.

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


Alvin B. Marcelo, MD, FPCS, CGEIT, TOGAF, COBIT5 F/I, ArchiMate

https://orcid.org/0000-0001-6250-9169

Disclaimer:

*** This
e-mail, together with any attachments, is intended for the named recipients only and is confidential. It may also be privileged or otherwise protected by law. If you have received it in error, please notify the sender immediately by reply e-mail and delete it and any attachments from your system. You may
not copy or disclose its contents to anyone.***

Ryan Crichton
Lead Developer

Jembi Health Systems NPC | SOUTH AFRICA

Mobile: +27

This is great, thank you!

···

On Fri, Jul 20, 2018 at 9:19 PM, Cox, Michelle Louise miclcox@regenstrief.org wrote:

The OpenHIE Architecture call scheduled for Friday, July 27 has been canceled since many people will be preparing for travel to the OpenHIE Community Meeting in Tanzania.

The next regularly-scheduled call will take place on Monday, August 13th.

Thanks!

**Michelle Cox ** |****Program Coordinator, Global Health Informatics

1101 West Tenth Street



Indianapolis, IN 46202

Tel 317-274-9324 | Fax 317-274-9305

Skype ID: miclcox | Facebook.com/regenstriefinstitute |
www.regenstrief.org

My normal work hours are Monday – Friday, 7:15 a.m. – 4:00 p.m. Eastern Time

Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged information and are intended solely for the use of the named addressee(s).
Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and State laws prohibit you from making further disclosure of such information
without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical or other information is not sufficient for this purpose.

If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention, disclosure, copying, distribution or use of this information
by anyone other than the intended recipient is strictly prohibited.

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


Alvin B. Marcelo, MD, FPCS, CGEIT, TOGAF, COBIT5 F/I, ArchiMate

https://orcid.org/0000-0001-6250-9169

Disclaimer:

*** This
e-mail, together with any attachments, is intended for the named recipients only and is confidential. It may also be privileged or otherwise protected by law. If you have received it in error, please notify the sender immediately by reply e-mail and delete it and any attachments from your system. You may
not copy or disclose its contents to anyone.***

Dear Ryan,

The SHR therefore creates a tremendous risk for centralized storage of identifiable data? This poses a big challenge for LMICs…

Or is there a better risk-mitigated method?

Alvin

···

On Fri, Jul 20, 2018 at 9:19 PM, Cox, Michelle Louise miclcox@regenstrief.org wrote:

The OpenHIE Architecture call scheduled for Friday, July 27 has been canceled since many people will be preparing for travel to the OpenHIE Community Meeting in Tanzania.

The next regularly-scheduled call will take place on Monday, August 13th.

Thanks!

**Michelle Cox ** |****Program Coordinator, Global Health Informatics

1101 West Tenth Street



Indianapolis, IN 46202

Tel 317-274-9324 | Fax 317-274-9305

Skype ID: miclcox | Facebook.com/regenstriefinstitute |
www.regenstrief.org

My normal work hours are Monday – Friday, 7:15 a.m. – 4:00 p.m. Eastern Time

Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged information and are intended solely for the use of the named addressee(s).
Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and State laws prohibit you from making further disclosure of such information
without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical or other information is not sufficient for this purpose.

If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention, disclosure, copying, distribution or use of this information
by anyone other than the intended recipient is strictly prohibited.

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


Alvin B. Marcelo, MD, FPCS, CGEIT, TOGAF, COBIT5 F/I, ArchiMate

https://orcid.org/0000-0001-6250-9169

Disclaimer:

*** This
e-mail, together with any attachments, is intended for the named recipients only and is confidential. It may also be privileged or otherwise protected by law. If you have received it in error, please notify the sender immediately by reply e-mail and delete it and any attachments from your system. You may
not copy or disclose its contents to anyone.***

Absolutely, so security should be considered from day one in an SHR implementation. Using the OpenHIE with an interoperability layer helps manage some of the security concerns however, there is no real way to fully mitigate risk as the HIE needs this information to function. One method that may help is to keep demographic details separately in the CR/MPI and link to a record in the SHR for clinical details. This means there would have to be two breaches to link medical data with identifiable data which would help. However, there would still be risk that the medical data still contains some information that could identify a patient.

The bottom line is that HIE infrastructure needs to be properly secured and perhaps as OpenHIE we should list some best practices on how to make that a reality.

Cheers,

Ryan

···

On Fri, Jul 20, 2018 at 9:19 PM, Cox, Michelle Louise miclcox@regenstrief.org wrote:

The OpenHIE Architecture call scheduled for Friday, July 27 has been canceled since many people will be preparing for travel to the OpenHIE Community Meeting in Tanzania.

The next regularly-scheduled call will take place on Monday, August 13th.

Thanks!

**Michelle Cox ** |****Program Coordinator, Global Health Informatics

1101 West Tenth Street



Indianapolis, IN 46202



Tel 317-274-9324 | Fax 317-274-9305

Skype ID: miclcox | Facebook.com/regenstriefinstitute |
www.regenstrief.org

My normal work hours are Monday – Friday, 7:15 a.m. – 4:00 p.m. Eastern Time

Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged information and are intended solely for the use of the named addressee(s).
Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and State laws prohibit you from making further disclosure of such information
without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical or other information is not sufficient for this purpose.

If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention, disclosure, copying, distribution or use of this information
by anyone other than the intended recipient is strictly prohibited.

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


Alvin B. Marcelo, MD, FPCS, CGEIT, TOGAF, COBIT5 F/I, ArchiMate

https://orcid.org/0000-0001-6250-9169

Disclaimer:

*** This
e-mail, together with any attachments, is intended for the named recipients only and is confidential. It may also be privileged or otherwise protected by law. If you have received it in error, please notify the sender immediately by reply e-mail and delete it and any attachments from your system. You may
not copy or disclose its contents to anyone.***

Ryan Crichton
Lead Developer

Jembi Health Systems NPC | SOUTH AFRICA

Mobile: +27

Hi all,

I think using synthetic data initially would be a useful way to test your stack for security and privacy concerns prior to using real data. I’m happy to discuss it more with those interested. In part this requires harmonizing the fake datasets already in use in the reference products. Synthea has a lot of promise and we at IntraHealth are proposing to work with it to generate millions of fake but realistic SHR for LMIC.

https://proposals.digitalsquare.io/63

HTH

···

On Jul 27, 2018, at 10:49, Ryan Crichton <ryan.crichton@jembi.org> wrote:

Absolutely, so security should be considered from day one in an SHR implementation. Using the OpenHIE with an interoperability layer helps manage some of the security concerns however, there is no real way to fully mitigate risk as the HIE needs this information to function. One method that may help is to keep demographic details separately in the CR/MPI and link to a record in the SHR for clinical details. This means there would have to be two breaches to link medical data with identifiable data which would help. However, there would still be risk that the medical data still contains some information that could identify a patient.

The bottom line is that HIE infrastructure needs to be properly secured and perhaps as OpenHIE we should list some best practices on how to make that a reality.

Cheers,
Ryan

On Fri, Jul 27, 2018 at 9:38 AM Alvin Marcelo <admarcelo@up.edu.ph> wrote:
Dear Ryan,

The SHR therefore creates a tremendous risk for centralized storage of identifiable data? This poses a big challenge for LMICs...

Or is there a better risk-mitigated method?

Alvin

On Fri, 27 Jul 2018, 3:18 PM Ryan Crichton <ryan.crichton@jembi.org> wrote:
Hi Alvin,

I'l try answer were I can. The structure for the SHR will depend on the use cases being implemented but it is recommended to try use content profiles where possible that standardise the data that is captured and often structures it as a document such as a CDA document. Although, more recent HIEs are preferring to go the FHIR route and profiling FHIR for the implementation needs may be a more moderns way to go. It is also possible to consume documents in FHIR.

The data in the SHR is identifiable as it is designed to be the central store for a patient's medical records (or at least a summary of them) because of that it needs to be identifiable so that data can be queried for a particular patient. It also relies on their being an MPI/Client registry in place to be able to find that patient and resolve their identity.

ADX would be the preferred method to submit to the HMIS. The schema would be implementation specific in most cases and would need to be agreed on by the implementing partners.

Hope this helps.

Cheers,
Ryan

On Thu, Jul 26, 2018 at 3:20 AM Alvin Marcelo <admarcelo@up.edu.ph> wrote:
Dear architects,

I have a few questions and apologies if the answers are available somewhere and I have not done my homework (too busy hehe):

Is there a recommended structure of the SHR?

Are the data in the SHR identifiable or de-identified? why and why not?

How will the SHR submit data to the HMIS? is this via ADX? who defines the ADX schema?

TIA

On Fri, Jul 20, 2018 at 9:19 PM, Cox, Michelle Louise <miclcox@regenstrief.org> wrote:
The OpenHIE Architecture call scheduled for Friday, July 27 has been canceled since many people will be preparing for travel to the OpenHIE Community Meeting in Tanzania.

The next regularly-scheduled call will take place on Monday, August 13th.

Thanks!

Michelle Cox | Program Coordinator, Global Health Informatics

1101 West Tenth Street

Indianapolis, IN 46202

Tel 317-274-9324 | Fax 317-274-9305

Skype ID: miclcox | Facebook.com/regenstriefinstitute | www.regenstrief.org

My normal work hours are Monday – Friday, 7:15 a.m. – 4:00 p.m. Eastern Time

Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged information and are intended solely for the use of the named addressee(s). Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and State laws prohibit you from making further disclosure of such information without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical or other information is not sufficient for this purpose.

If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention, disclosure, copying, distribution or use of this information by anyone other than the intended recipient is strictly prohibited.

--
You received this message because you are subscribed to the Google Groups "OpenHIE Architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Alvin B. Marcelo, MD, FPCS, CGEIT, TOGAF, COBIT5 F/I, ArchiMate
https://orcid.org/0000-0001-6250-9169

--
Disclaimer:

This e-mail, together with any attachments, is intended for the named recipients only and is confidential. It may also be privileged or otherwise protected by law. If you have received it in error, please notify the sender immediately by reply e-mail and delete it and any attachments from your system. You may not copy or disclose its contents to anyone.

--
You received this message because you are subscribed to the Google Groups "OpenHIE Architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Ryan Crichton
Lead Developer
Jembi Health Systems NPC | SOUTH AFRICA
Mobile: +27
--
Ryan Crichton
Lead Developer
Jembi Health Systems NPC | SOUTH AFRICA
Mobile: +27

--
You received this message because you are subscribed to the Google Groups "OpenHIE Architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

As a plug for the OpenHIE HacKonnect-AThon (KHAT) next week - we will be looking at a FHIR version of ADX.

Cheers,

-carl

···

On Fri, Jul 20, 2018 at 9:19 PM, Cox, Michelle Louise miclcox@regenstrief.org wrote:

The OpenHIE Architecture call scheduled for Friday, July 27 has been canceled since many people will be preparing for travel to the OpenHIE Community Meeting in Tanzania.

The next regularly-scheduled call will take place on Monday, August 13th.

Thanks!

**Michelle Cox ** |****Program Coordinator, Global Health Informatics

1101 West Tenth Street



Indianapolis, IN 46202

Tel 317-274-9324 | Fax 317-274-9305

Skype ID: miclcox | Facebook.com/regenstriefinstitute |
www.regenstrief.org

My normal work hours are Monday – Friday, 7:15 a.m. – 4:00 p.m. Eastern Time

Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged information and are intended solely for the use of the named addressee(s).
Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and State laws prohibit you from making further disclosure of such information
without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical or other information is not sufficient for this purpose.

If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention, disclosure, copying, distribution or use of this information
by anyone other than the intended recipient is strictly prohibited.

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


Alvin B. Marcelo, MD, FPCS, CGEIT, TOGAF, COBIT5 F/I, ArchiMate

https://orcid.org/0000-0001-6250-9169

Disclaimer:

*** This
e-mail, together with any attachments, is intended for the named recipients only and is confidential. It may also be privileged or otherwise protected by law. If you have received it in error, please notify the sender immediately by reply e-mail and delete it and any attachments from your system. You may
not copy or disclose its contents to anyone.***

Hi,

The FHIR experts as you may know have been working in Asia with ministries and SIL-Asia. James Agnew is there currently and our experience is FHIR changes things significantly. The processes and architecture are being documented for one national level implementation and it would be awesome to share specifics of what comes out of the connectathon in TZ and efforts elsewhere, perhaps in Aug or Sept on a call.

And look forward to hearing more about DHIS2 - FHIR happenings in Africa. Would be beneficial as we all prepare for the DHIS2 - FHIR integration workshop in Manila with UiO.

···

Thanks,

Donna

On Fri, Jul 27, 2018 at 12:22 PM, Carl Leitner litlfred@gmail.com wrote:

As a plug for the OpenHIE HacKonnect-AThon (KHAT) next week - we will be looking at a FHIR version of ADX.
Cheers,

-carl

On Jul 27, 2018, at 3:36 AM, Alvin Marcelo admarcelo@up.edu.ph wrote:

This is great, thank you!

On Fri, 27 Jul 2018, 3:18 PM Ryan Crichton ryan.crichton@jembi.org wrote:

Hi Alvin,

I’l try answer were I can. The structure for the SHR will depend on the use cases being implemented but it is recommended to try use content profiles where possible that standardise the data that is captured and often structures it as a document such as a CDA document. Although, more recent HIEs are preferring to go the FHIR route and profiling FHIR for the implementation needs may be a more moderns way to go. It is also possible to consume documents in FHIR.

The data in the SHR is identifiable as it is designed to be the central store for a patient’s medical records (or at least a summary of them) because of that it needs to be identifiable so that data can be queried for a particular patient. It also relies on their being an MPI/Client registry in place to be able to find that patient and resolve their identity.

ADX would be the preferred method to submit to the HMIS. The schema would be implementation specific in most cases and would need to be agreed on by the implementing partners.

Hope this helps.

Cheers,

Ryan

On Thu, Jul 26, 2018 at 3:20 AM Alvin Marcelo admarcelo@up.edu.ph wrote:

Dear architects,

I have a few questions and apologies if the answers are available somewhere and I have not done my homework (too busy hehe):

Is there a recommended structure of the SHR?

Are the data in the SHR identifiable or de-identified? why and why not?

How will the SHR submit data to the HMIS? is this via ADX? who defines the ADX schema?

TIA

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


Ryan Crichton
Lead Developer

Jembi Health Systems NPC | SOUTH AFRICA

Mobile: +27

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

On Fri, Jul 20, 2018 at 9:19 PM, Cox, Michelle Louise miclcox@regenstrief.org wrote:

The OpenHIE Architecture call scheduled for Friday, July 27 has been canceled since many people will be preparing for travel to the OpenHIE Community Meeting in Tanzania.

The next regularly-scheduled call will take place on Monday, August 13th.

Thanks!

**Michelle Cox ** |****Program Coordinator, Global Health Informatics

1101 West Tenth Street



Indianapolis, IN 46202

Tel 317-274-9324 | Fax 317-274-9305

Skype ID: miclcox | Facebook.com/regenstriefinstitute |
www.regenstrief.org

My normal work hours are Monday – Friday, 7:15 a.m. – 4:00 p.m. Eastern Time

Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged information and are intended solely for the use of the named addressee(s).
Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and State laws prohibit you from making further disclosure of such information
without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical or other information is not sufficient for this purpose.

If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention, disclosure, copying, distribution or use of this information
by anyone other than the intended recipient is strictly prohibited.

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


Alvin B. Marcelo, MD, FPCS, CGEIT, TOGAF, COBIT5 F/I, ArchiMate

https://orcid.org/0000-0001-6250-9169

Disclaimer:

*** This
e-mail, together with any attachments, is intended for the named recipients only and is confidential. It may also be privileged or otherwise protected by law. If you have received it in error, please notify the sender immediately by reply e-mail and delete it and any attachments from your system. You may
not copy or disclose its contents to anyone.***

Hi all… and sorry to be slow replying.

I’d like to expand a bit on Ryan’s excellent response. From a data-modeling point of view, the underlying “schema” for an SHR can be thought of as either a simple XML or json datastore or (more appropriately, in my view) as a searchable structured database where the “tables” can contain CDA templates or FHIR resources. Of course, a normalized design would require a family of related subtables to support storing content with a [0…*] cardinality.

In OpenHIEv1, the SHR workflows support the storage and retrieval of CDA documents. A CDA document is a bundle of CDA templates that also includes “header” information that identifies important metadata about the clinical encounter (subject, provider, facility, timestamp, unique ID, etc.). Our OpenHIEv2 work is focused on leveraging FHIR bundles in an analogous way. A FHIR bundle is a collection of FHIR resources that can be communicated and stored as a group and associated with an encounter (and its metadata) in the same way the CDA could.

At present, the OpenHIE community is evaluating the Mobile Health Data (MHD) IHE profile as a way to do this. On the “back end”, MHD is designed to be able to persist both FHIR and CDA content. Our hope is that it could potentially provide an elegant mechanism to support an organic “evolution” from CDA to FHIR as the FHIR spec matures, stabilizes, and grows its adoption base.

Mercifully, the data models for CDA templates and FHIR resources tend to be quite similar. This shouldn’t be surprising since they are (generally) based on the same underlying information models. An SHR database which is constructed to align to these underlying information models (e.g. leveraging a canonical model) could quite readily persist content that is conveyed using CDA, FHIR, HL7v2, and so on. This is the kind of thinking behind products such as SmileCDR and others (including HEARTH, I believe, but Ryan or Carl F can add more insight regarding this).

I hope this is helpful.

Warmest regards,

Derek

Derek Ritz, P.Eng, CPHIMS-CA

ecGroup Inc.

+1 (905) 515-0045

This communication is intended only for the party to whom it is addressed, and may contain information which is privileged or confidential. Any other delivery, distribution, copying or disclosure is strictly prohibited and is not a waiver of privilege or confidentiality.

···

Hi Alvin,

I’l try answer were I can. The structure for the SHR will depend on the use cases being implemented but it is recommended to try use content profiles where possible that standardise the data that is captured and often structures it as a document such as a CDA document. Although, more recent HIEs are preferring to go the FHIR route and profiling FHIR for the implementation needs may be a more moderns way to go. It is also possible to consume documents in FHIR.

The data in the SHR is identifiable as it is designed to be the central store for a patient’s medical records (or at least a summary of them) because of that it needs to be identifiable so that data can be queried for a particular patient. It also relies on their being an MPI/Client registry in place to be able to find that patient and resolve their identity.

ADX would be the preferred method to submit to the HMIS. The schema would be implementation specific in most cases and would need to be agreed on by the implementing partners.

Hope this helps.

Cheers,

Ryan

On Thu, Jul 26, 2018 at 3:20 AM Alvin Marcelo admarcelo@up.edu.ph wrote:

Dear architects,

I have a few questions and apologies if the answers are available somewhere and I have not done my homework (too busy hehe):

Is there a recommended structure of the SHR?

Are the data in the SHR identifiable or de-identified? why and why not?

How will the SHR submit data to the HMIS? is this via ADX? who defines the ADX schema?

TIA

On Fri, Jul 20, 2018 at 9:19 PM, Cox, Michelle Louise miclcox@regenstrief.org wrote:

The OpenHIE Architecture call scheduled for Friday, July 27 has been canceled since many people will be preparing for travel to the OpenHIE Community Meeting in Tanzania.

The next regularly-scheduled call will take place on Monday, August 13th.

Thanks!

**Michelle Cox ** |****Program Coordinator, Global Health Informatics

1101 West Tenth Street

Indianapolis, IN 46202

Tel 317-274-9324 | Fax 317-274-9305

Skype ID: miclcox | Facebook.com/regenstriefinstitute | www.regenstrief.org

My normal work hours are Monday – Friday, 7:15 a.m. – 4:00 p.m. Eastern Time

Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged information and are intended solely for the use of the named addressee(s). Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and State laws prohibit you from making further disclosure of such information without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical or other information is not sufficient for this purpose.

If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention, disclosure, copying, distribution or use of this information by anyone other than the intended recipient is strictly prohibited.


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Alvin B. Marcelo, MD, FPCS, CGEIT, TOGAF, COBIT5 F/I, ArchiMate

https://orcid.org/0000-0001-6250-9169

Disclaimer:

This e-mail, together with any attachments, is intended for the named recipients only and is confidential. It may also be privileged or otherwise protected by law. If you have received it in error, please notify the sender immediately by reply e-mail and delete it and any attachments from your system. You may not copy or disclose its contents to anyone.


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ryan Crichton

Lead Developer

Jembi Health Systems NPC | SOUTH AFRICA

Mobile: +27


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.