We are having our OpenHIE Architecture call this
Monday, September 14th at 10:00 a.m. Eastern Time.
** PLEASE NOTE: There is a new code to access the conference call – 35104627. **
The dial-in number is unchanged…800-220-9875. The wiki page has been updated to reflect the updated information.
Agenda
- ARB Evaluation Step of MHD profile - Ryan C to provide overview and status
-
What is MHD?
-
How does it Impact other workflows?
-
Is IHE testing necessry?
-
Will software be ready for testing at IHE in January?
-
Will it be ready for inclusion in the next OpenHIE realease?
-
What’s the process for incorporating it into an upcoming release of OpenHIE?
- Update on IHE Testing Expectations
-
Registration closes Oct 9th
-
We currently believe that the following testing is needed to support the 1.5 and 2.0 releases that are being outlined in the
Roadmap -
- XDS.b with the on-demand document option. (SHR)
-
- mACM (Message Aggregator)
-
- ADX (HMIS)
-
Other possibilities that have been mentioned:
-
- PDQm (CRs)
-
- PIXm (CRs)
-
- MDH (SHR?)
-
- re-testing profiles tested last year
-
What resources are needed to support IHE testing needs for 1.5 and 2.0?
Thank you!
Michelle Cox| ** GHI Program Assistant**
Center for Biomedical Informatics
Regenstrief Institute
410 W. 10th Street
Indianapolis, IN 46202
317-274-9324 | Fax: 317-274-9305
Skype ID: miclcox
Facebook.com/regenstriefinstitute
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