Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Now that the setup is complete, let's take a look at the user experience we have created. First, in field: 

Field

Your field user can select this new sample type the same way as a test form you have fully built in MetaField. There is no difference in the field between tests done manually in MetaField or externallexternal. This means that field users can use the same chain of custody (pickup and checkin pick-up and check-in process) as all other samples.

Image Added

When logging the sample, they can also choose our test as a part of the lab instructions. This is not required of course, but it shows up just like a test performed in MetaField.

Image Added

LIMS

Once the Field technician check the specimen into a lab, the specimen goes through the LIMS process just like any other specimen. The receiving process and the test assignment process are identical. Even though you are not performing this test within MetaField, the LIMS module still recognizes this as a test type. Image RemovedYou can also schedule the test as usual as well as assign a lab technician.

Image Added

The test will go through the Testable and To Test queues just like any other test. The main difference is when you actually go to enter the test results. You will now be able to attach the external report done in another system or in Excel instead of entering test results. You will still need to be in the completion date to move it out of To Test.

Image Added

This is the external report we are attaching:

Image Added

At this point, the test must be approved by the lab manager and then can be reported in the usual ways, either in QC or in LIMS. The report that is generated will have whatever information from MetaField you chose to include as well as your external report.