Location as Client possible?

Hi,

Patients apprars as client in senaite. Can we set up location of mrs as clients?

Thanks

Hi @ersan,

Clearly we need to know more about the details of the HIS workflow that you envision here. Are you able to share that with us?

If there was a flow like the one your describe, then how would you envision remapping the test results to the actual patient?

2 Likes

Thank you for your interest @mksd .

I am a central laboratory. We are working on tests in hospitals in different locations.

Each location provides results to its own patients. Each location may have its own CRM or LIMS software. They can get the results I publish via senaite with their own username and password. It is their responsibility to integrate the results into their own software if they wish.

I only provide genetic counseling and genetic test results to patients who come to my laboratory.

Senaite alone serves this function well. Test templates and test approval flow are very good and comprehensive. We also use Senaite with the patient module.

Senaite openmrs is exactly the system we need with odoo.

I tried and tested Ozone HIS, every patient in Senaite appears as a client. Instead, the client in Senaite should come as a location in open mrs. Is it possible for the patient in Open MRS to come to the patient module in Senaite?

Thanks @ersan for providing further details.

What I am missing in your use case is the process that creates the analysis requests that you eventually manipulate in SENAITE. This is important because this will help me understand how each request is connected with the patient in the first place.

Looks like you describe a situation where results are bundled by facility - the facility that ordered those tests for (some of) their patients. If that’s correct then I find it to be quite interesting :slight_smile: but two things:

  1. What’s a client really in SENAITE? Looks like it was named like that precisely because it could be “anything” (patient, clinic, group of clinics, etc).
  2. Assuming a client can be anything, some work would be needed to put together messaging routes that handle those bundled results so that they can be re-associated with the correct patients elsewhere.
1 Like

I have illustrated the road map I wanted to explain. @mksd

Hospitals are unaware and independent of each other.

  1. client is hospital or clinics.
  2. I share pdf and results to clients.

Senaite gives me opportunity user name and passwords for our clients. Our clients input patient information and their tests. They send their sapmles via cargo. We accepts their samples from our lab and then reporting. Clients follow their patient from their(clients) username and password.

Could you show a SENAITE screenshot of this specific action done by a client? It would be great if the screenshot could show that data for multiple patients of the client are mixed up.

1 Like

I will try to show an example workflow. I have installed senaite newly and originally(i dont edit any code).

I have two clients they have named Hospital 01 and Hospital 02

01 - Hospital 01 is logining our web.

02 - Hospital 01 is entering their patent informations.

03- Hospital sent their patient sample to our lab.

04 - Our lab is now checking our web while logging as oursampler username.

05- Our lab accept the sample.

06 - Then, other our client Hospital 02 is sending us a sample.

07 - Then Our lab show their account 2 samples they comes from Hospital 01 and Hospital 02.

Is it possible to Locations as Hospital 01 and Hospital 02 … ? Like that:

Thanks @ersan ok, I think I see :slight_smile: The key here is the fact that you have used SENAITE Patient.

Disclaimer: what you envision will require to do some coding :disappointed:

The current SENAITE routes assume that client = patient. Your use case would require to make the routes configurable to put in place an opt-in mechanism for the below changes:

  • OpenMRS patient = SENAITE client
  • OpenMRS location → SENAITE client
    • And yet not all locations, only some locations that will have to be flagged accordingly.
  • OpenMRS patient → SENAITE patient

Two questions for you:

  1. Are you confident that SENAITE Patient can be used? I’m asking because of this (fairly recent) comment for example. This is key to ensuring that this all can become part of Ozone HIS FOSS.
  2. Do you (or your group) have capacity to engage in EIP middleware business analysis & development, or will you require to outsource this to the Ozone Dev Team?
1 Like

@mksd , first of all, I want to express my sincere gratitude for your attention and assistance in this process.

1: Yes, I am confident that SENAITE Patient is the right choice for us, and its current state suits our needs. We are a clinical genetics laboratory, and SENAITE is essential for our workflow. 2: We believe that we currently have the capacity for development :slight_smile:

In case I can’t use SENAITE patient, I have an alternative way: @mksd

In lab tests entered from OpenMRS, I might look for a way to try to send Location information to SENAITE instead of Providers.

This way, I have the chance to send the test results to Providers via SENAITE by e-mail.

I currently only provide services to a few Providers. The primary issue for me in the first place is to send each of my providers the test results of their patients.

Is there a way to send the Location information sent from OpenMRS to SENAITE as Client’s Contact?

@mksd How can I get support from Ozone Dev Team on this issue?

@ersan do you mean in a paid-for capacity?

If not then best is to open questions here on Talk or on #ozone on Slack, which you have joined already.


Please note that you should at least wait for the release of alpha.7 to start developing custom routes. The good news is that this release is literally imminent, see table below.

Better even would be to wait for beta.1, this is the ~timeline:

Date Release
This week alpha.7
Nov 17th alpha.8
Mid/end of Dec alpha.9
Q1 2024 beta.1

I will repeat and detail all this when I make the formal announcement of the alpha.7 release.

Cc @caseynth2 :point_up:

2 Likes