The RHEA interoperability layer is currently up and running. It currently hosts MOCK services only and no real data is returned (the exception being the facilities registry queries where data is returned from the current Resource Map facility registry instance). The mock services will respond with the correct HTTP response code and, where need, the response message in the body of the HTTP request. See the transaction specification document below for API details.
The RHEA HIE API is currently hosted at the following endpoints:
The HTTPS endpoint accepts requests for all supported API calls to ensure that user of the API are properly authenticated. The HTTP service is publicly accessible however it only allows request for specific endpoints. The following endpoints are accessible through this endpoint:
- Get facility
- Query for facility
The endpoint HTTPS endpoint requires the use of basic auth to access the services.
HTTPS Basic Auth details:
- Username: test
- Password: test
Certificate for HTTPS:
- The attached file mule.cer or mule.pem should be added to the clients truststore to enable the trusted communicate between the client and the interoperability layer.
The messaging specification are outlined in the following wiki page along with the transaction formats (Note: some of these transaction formats are not yet defined, these will be updated shortly):
- See the RHEA Transactions wiki page for details about specific transactions
For more information on how to connect please see the tutorial on how to connect:
- Communicating with the HIE - a Java example - https://docs.google.com/document/d/1SMK4bm5DAtNY_AyGnLU6r1M947f4ahiXN3-Yy4mZGyU/edit
- See the Java Project attached to this page for the example code, alternatively, the code can be found here: https://github.com/jembi/rhea-client-mock