Ability for generate multiple accession against a given order

1

Hello All,

I want to understand the order fulfilment capability of OpenELIS Global

  1. Physician creates a service request for a test
    • I am assuming we can use the FHIR endpoint directly instead of following FHIR Exchange. Please let me know if not.
  2. Lab tech, creates an accession.
    • Is there a way to notify to any external system that the accession was created?
    • If not, I am assuming by polling the service request created at OpenELIS, one can get to know if an accession was generated for the test?
  3. Lab Tech, may need to draw multiple samples
    • Is there a possibility to have multiple accessions against a given order?
    • There are few scenarios where this can happen
      • Some of the samples may need to be referred out, while some can be done in house. (eg say some tests from a CBC panel). Having different accession, provides ability to track them separately.
      • Lets say the samples (out of a single accession) have been collected into 3 different tubes. One of the tube samples coagulated, and the patient needs to be called again (either the same day or subsequent). This leads to drawing another sample and not be mixed up with the same accession. This also relates to their process and compliance and QC requirements.
    • If multiple accessions for the same service request is not possible, what would be the alternative process?
2

@caseyi @Moses_Mutesasira any thoughts on the above?

3

Currently we only support this through the FHIR exchange but we are envisioning creating a direct FHIR facade for OpenELIS

For the FHIR HIE exchange, we use the FHIR Subscription API to notify an external system since the FHIR exchange is done through a FHIR server.
But we primarirly we rely on the external system polling for the specific Resource to get to know its current status

Currently OpenELIS doesnt support multiple accesions against a single order but can update the accession of a specific oder wheneber there are updates to that order ie when samples are removed or addied , etc , and all the updates gets tracked int audit traill of that oder

1 Like
4

For the multiple acession numbers, for your use case, each sample has it’s own ID, and some for each aliquot, so you will always be able to track them seperately, even if you refer some out. In fact, this makes is easier to trace back to the original order. I’d be happy to explain more if needed. The order/acession number is LABNO1234567 , sample 1 is LABNO1234567.1 and sample 2 LABNO1234567.2, the first aloquot of LABNO1234567.2 is LABNO1234567.2-1 , etc. I think this will over well your use case.