FHIR and OHIE Workflows

jennifer.e.shivers · October 17, 2018, 2:55pm

Dear workflow sponsors and OHIE sub community leads,

There is a request to have a discussion about where we are with FHIR. Can you please take a look at the workflows you sponsor or that impact your sub community
component and do the following:

If the workflow currently supports FHIR please ensure that the FHIR specifications are included in the workflow description.
If the workflow does not support FHIR, can you respond to Shaun, Jennifer and Jamie to let us know what you are thinking about the workflow and support of FHIR.

Thank you.

Jennifer

**Jennifer Shivers **|**Senior Integration Architect ***** | *** Senior
Business Analyst

Tel 317-797-1200 | Skype jennifer.shivers

···

**
1101 West Tenth Street**

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

Tel 317-274-9234 | Fax 317-274-9303

Twitter: @Regenstrief | Facebook.com/regenstriefinstitute

www.regenstrief.org

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.

jthomas · October 24, 2018, 5:57pm

Hi All,

Just bringing this back to the top of everyone’s email as I don’t see where anyone has updated the workflow page. Please make your revisions by October 31 or email Jennifer, Shaun and I has specified below.

Thank you for helping to keep wiki documentation up to date!

···

**Jamie Thomas **|****Health Information Project Manager/Communications

Center for Biomedical Informatics

1101 West Tenth Street

Indianapolis, IN 46202

Tel 317-274-9218 | Fax 317-274-9305

Email: jt48@regenstrief.org | Skype: jamie.thomas5670 | Twitter: @Regenstrief

www.regenstrief.org

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.

From: “ohie-architecture@googlegroups.com” ohie-architecture@googlegroups.com on behalf of “Shivers, Jennifer” jeshiver@regenstrief.org
Date: Wednesday, October 17, 2018 at 10:55 AM
To: “ohie-architecture@googlegroups.com” ohie-architecture@googlegroups.com
Subject: FHIR and OHIE Workflows

Dear workflow sponsors and OHIE sub community leads,

There is a request to have a discussion about where we are with FHIR. Can you please take a look at the workflows you sponsor or that impact your sub community
component and do the following:

If the workflow currently supports FHIR please ensure that the FHIR specifications are included in the workflow description.
If the workflow does not support FHIR, can you respond to Shaun, Jennifer and Jamie to let us know what you are thinking about the workflow and support of FHIR.

Thank you.

Jennifer

**Jennifer Shivers **|***Senior Integration Architect * **| Senior Business Analyst

Tel 317-797-1200 | Skype jennifer.shivers

**
1101 West Tenth Street**

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

Tel 317-274-9234 | Fax 317-274-9303

Twitter: @Regenstrief | Facebook.com/regenstriefinstitute

www.regenstrief.org

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_Marcelo · October 24, 2018, 11:55pm

Dear Jennifer,

Looping in Philip who’s our technical lead at the Standards and Interoperability Lab-Asia.

SILA used FHIR (+IHE) in the annual demo at the AeHIN General Meeting – connecting 3 different EMRs to the WHO app (DHIS2). Phil, could you share the blueprint with the group pls?

Jennifer, can you add Phil to this list? Thanks…

Alvin

···

On Wed, Oct 17, 2018, 10:55 PM Shivers, Jennifer, jeshiver@regenstrief.org wrote:

Dear workflow sponsors and OHIE sub community leads,

There is a request to have a discussion about where we are with FHIR. Can you please take a look at the workflows you sponsor or that impact your sub community
component and do the following:

If the workflow currently supports FHIR please ensure that the FHIR specifications are included in the workflow description.

If the workflow does not support FHIR, can you respond to Shaun, Jennifer and Jamie to let us know what you are thinking about the workflow and support of FHIR.

Thank you.

Jennifer

**Jennifer Shivers **|**Senior Integration Architect ***** | *** Senior
Business Analyst

Tel 317-797-1200 | Skype jennifer.shivers

**
1101 West Tenth Street**

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

Tel 317-274-9234 | Fax 317-274-9303

Twitter: @Regenstrief | Facebook.com/regenstriefinstitute

www.regenstrief.org

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.

jthomas · October 25, 2018, 1:06pm

Thank you for connecting us with Phil. We have sent him an invite to join the OpenHIE Architecture mailing list.

···

**Jamie Thomas **|****Health Information Project Manager/Communications

Center for Biomedical Informatics

1101 West Tenth Street

Indianapolis, IN 46202

Tel 317-274-9218 | Fax 317-274-9305

Email: jt48@regenstrief.org | Skype: jamie.thomas5670 | Twitter: @Regenstrief

www.regenstrief.org

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.

From: “ohie-architecture@googlegroups.com” ohie-architecture@googlegroups.com on behalf of Alvin Marcelo admarcelo@up.edu.ph
Reply-To: “admarcelo@up.edu.ph” admarcelo@up.edu.ph
Date: Wednesday, October 24, 2018 at 7:55 PM
To: “Shivers, Jennifer” jeshiver@regenstrief.org
Cc: “ohie-architecture@googlegroups.com” ohie-architecture@googlegroups.com, Philip Zuniga philip.zuniga@gmail.com
Subject: Re: FHIR and OHIE Workflows

Dear Jennifer,

Looping in Philip who’s our technical lead at the Standards and Interoperability Lab-Asia.

SILA used FHIR (+IHE) in the annual demo at the AeHIN General Meeting – connecting 3 different EMRs to the WHO app (DHIS2). Phil, could you share the blueprint with the group pls?

Jennifer, can you add Phil to this list? Thanks…

Alvin

On Wed, Oct 17, 2018, 10:55 PM Shivers, Jennifer, jeshiver@regenstrief.org wrote:

Dear workflow sponsors and OHIE sub community leads,

There is a request to have a discussion about where we are with FHIR. Can you please take a look at the workflows you sponsor or that impact your
sub community component and do the following:

If the workflow currently supports FHIR please ensure that the FHIR specifications are included in the workflow description.

If the workflow does not support FHIR, can you respond to Shaun, Jennifer and Jamie to let us know what you are thinking about the workflow and support of FHIR.

Thank you.

Jennifer

**Jennifer Shivers **|***Senior Integration Architect * **| Senior Business Analyst

Tel 317-797-1200 | Skype jennifer.shivers

**
1101 West Tenth Street**

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

Tel 317-274-9234 | Fax 317-274-9303

Twitter: @Regenstrief | Facebook.com/regenstriefinstitute

www.regenstrief.org

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.

–
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.