endpoint REST del Test Catalog

Hello,

Yes, I meant to post this question on OpenELIS Global Talk. Thank you for pointing me in the right direction.

I am working on an integration between OpenELIS Global and OpenEMR. My goal is to access the OpenELIS test catalog programmatically, including information such as:

  • Test ID

  • Test name

  • Test description

  • Test section

  • Sample type

  • Units

  • Active/inactive status

  • Other related catalog information

I understand that there has been work on exposing the Test Catalog through a REST endpoint.

Could you please provide information about:

  1. The REST endpoint(s) currently available for accessing the Test Catalog.

  2. Whether the endpoint is already available in the develop branch.

  3. The authentication method required to access it.

  4. Whether it is possible to create a dedicated API/service user with read-only access.

  5. Any available documentation, OpenAPI/Swagger definition, or examples.

I am currently running OpenELIS Global 2 from the develop Docker images.

The purpose is to synchronize or query the OpenELIS Test Catalog from OpenEMR without accessing the PostgreSQL database directly.

Thank you very much.

Hloo @luis.uriarte

Incase u havent already… you could try GET /OpenELIS-Global/rest/TestCatalog from here? It seems to already be in develop… with the fields it fills as u want all there, see.

There is also a newer &paged one under /rest/test-catalog/tests here

And about the auth question, i think plain http basic should do, and i see both classes are also gated at the top.. i wonder if these cover u needs?

Hi. Thank you so much.

@wodpachua, this was incredibly helpful. What I need to figure out now is that the user accessing the system must have the Global Administrator role (I don’t like that).
Thanks again, my friend.

1 Like

Hloo @luis.uriarte

Glad it helped…

the other direction could be widening the gate itself.. i see other controllers already doing hasAnyRole(...)..

@Moses_Mutesasira @Agaba_Derrick_Junior what would be ur take on this one? would u say widening the catalog GETs to hasAnyRole be something acceptable, or is a read-only role already planned somewhere??