Hi All,
I wanted to give you a quick status update of where we are with the OpenInfoMan, which is intended to be the engine behind the CSD compliant Provider Registry and to be incorporated in OpenHIM.
We have a “beta” version of it running here: http://csd.ohie.org:8984/CSD
and is populated with sample provider data.
The OpenInfoMan has almost all of the required functionality needed for use in the connect-a-thon, with the notable exception that it does not yet validate the data provided by the Service Directories. This is due to the fact that none us yet have Service Directories which are CSD compliant, making it hard to test against. I would suggest the next task is to get all of our registries CSD compliant
This endpoint has been linked to the OpenInfoMan to support further testing and development.
Once we have one of the facility registries acting as a Services Directory, we can start testing the required validation of data for interlinked registries.
Cheers.
-carl
···
On Monday, November 4, 2013 6:12:39 AM UTC-5, Carl Leitner wrote:
Hi All,
I wanted to give you a quick status update of where we are with the OpenInfoMan, which is intended to be the engine behind the CSD compliant Provider Registry and to be incorporated in OpenHIM.
We have a “beta” version of it running here: http://csd.ohie.org:8984/CSD
and is populated with sample provider data.
The OpenInfoMan has almost all of the required functionality needed for use in the connect-a-thon, with the notable exception that it does not yet validate the data provided by the Service Directories. This is due to the fact that none us yet have Service Directories which are CSD compliant, making it hard to test against. I would suggest the next task is to get all of our registries CSD compliant
We, at Jembi, have managed to setup the OpenInfoMan behind the OpenHIM to allow the OpenHIM to facilitate CSD transactions. We have this up on a test instance at the moment so that other service finders can test against. Here is the endpoint:
password: password
Let me know if there are any issues with this endpoint.
Cheers,
Ryan
···
On Thu, Nov 7, 2013 at 10:04 AM, Ryan Crichton ryan@jembi.org wrote:
Hi Carl,
Great, that is good news.
I’ve got the openinfoman setup locally and did some minor updates to the documentation to get people started. I’l try add this endpoint to my local openinfoman.
Cheers,
Ryan
–
Ryan Crichton
Software Developer, Jembi Health Systems | SOUTH AFRICA
This endpoint has been linked to the OpenInfoMan to support further testing and development.
Once we have one of the facility registries acting as a Services Directory, we can start testing the required validation of data for interlinked registries.
Cheers.
-carl
On Monday, November 4, 2013 6:12:39 AM UTC-5, Carl Leitner wrote:
Hi All,
I wanted to give you a quick status update of where we are with the OpenInfoMan, which is intended to be the engine behind the CSD compliant Provider Registry and to be incorporated in OpenHIM.
We have a “beta” version of it running here: http://csd.ohie.org:8984/CSD
and is populated with sample provider data.
The source code is available on github here under the “his-interop” group.
The OpenInfoMan has almost all of the required functionality needed for use in the connect-a-thon, with the notable exception that it does not yet validate the data provided by the Service Directories. This is due to the fact that none us yet have Service Directories which are CSD compliant, making it hard to test against. I would suggest the next task is to get all of our registries CSD compliant
Let me know if you run into any issues.
Cheers.
-carl
–
You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.