It does explain what happens when HTTP is the transport. I like the positioning of the OpenEMPI adaptor, and the ResMap adaptor, and how it separates those services from the Patient Encounter Mediator.
One question is: What would you do if LLP were used ?
If you said “V2 (in |pipe| or in V2.xml” will be the payload exchanged by HTTP, then I would be fine.
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
I think using HTTP makes a lot of sense and you are correct, I would say that if we were to go with HL7 v2 we could exchange the message over HTTP rather than relying on LLP. We do this for the RHIE and it works quite well.
@All:
On the call we are all feeling like we are getting to a design that we all are happy with. As discussed on the call, I will work to add some description/depiction of how synchronous and asynchronous messages can be handled as well as adding in a workflow engine (under domain services and mediators) as we discussed.
Also, we though that it made sense to start prototyping this architecture to vet it, so Jembi will take on creating a prototype from the existing OpenHIM in the coming weeks.
It does explain what happens when HTTP is the transport. I like the positioning of the OpenEMPI adaptor, and the ResMap adaptor, and how it separates those services from the Patient Encounter Mediator.
One question is: What would you do if LLP were used ?
If you said “V2 (in |pipe| or in V2.xml” will be the payload exchanged by HTTP, then I would be fine.
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 “Interoperability Layer (OpenHIE)” group.