Difference between revisions of "User:Shawndouglas/sandbox/sublevel4"

From LIMSWiki
Jump to navigationJump to search
Line 1: Line 1:
[[File:Blood Research- Saving Lives (8352) (9759352093).jpg|right|400px]]While clinical diagnostic and other related labs will interact with blood, blood banking and transfusion labs have different workflows and end goals, requiring a specialized informatics solution. Activities driving the need for a purpose-built LIMS include screening specimens against high-risk donors such as commercial sex workers and drug users, testing potential donors for infection diseases, documenting and reviewing (lookback of) donors and recipients, ensuring sufficient time is given for blood testing and cross-matching, and ensuring staff are appropriately trained concerning the risks to them and patients.<ref name="CurlessInfection18">{{cite web |url=http://reprolineplus.org/system/files/resources/IPC_M8_BloodbanksLabs.pdf |archiveurl=https://web.archive.org/web/20200108173322/http://reprolineplus.org/system/files/resources/IPC_M8_BloodbanksLabs.pdf |format=PDF |title=Module 8. Laboratories and Blood Banks |work=Infection Prevention and Control |author=Curless, M.S.; Forrester, L.A.; Gavin, M.A. |publisher=Jhpiego Corporation |date=2018 |archivedate=08 January 2020 |accessdate=09 March 2022}}</ref> These specialized workflows and responsibilities require a LIMS that is flexible enough to these specialized testing, documentation and training needs.
[[File:MarkhamStouffvilleHospital23.jpg|right|300px]]The hospital lab is a unique creature in that it encompasses many departments within a hospital, often spread out over multiple areas. Most of the prior mentioned specialties, as well as many more, will make up the bulk of laboratory testing in a hospital.<ref name="EspositoHospital15">{{cite web |url=https://health.usnews.com/health-news/patient-advice/articles/2015/01/30/hospital-labs-behind-the-scenes |title=Hospital Labs: Behind the Scenes |work=U.S. News & World Report |author=Esposito, L. |date=30 January 2015 |accessdate=09 March 2022}}</ref> By extension, the informatics solution used in the hospital must be equally robust. This means the LIMS should be sufficiently feature-rich to allow for pathology, hematology, microbiology, virology, molecular diagnostic and blood banking workflows (to name a few) to be readily implemented. Just about any type of specimen you could imagine may be taken<ref name="EspositoHospital15" />, so the LIMS should have vast flexibility in its specimen types. Additionally, given the multiple departments and high daily specimen load of a hospital[1], the LIMS should be automation-friendly and support a wide array of instruments and equipment.


In addition to the essential features of a standard LIMS, the blood bank and transfusion lab will also be looking for a system that can (or allows users to)<ref name="SunquestBloodBank20">{{cite web |url=https://www.sunquestinfo.com/software-and-services/blood-bank-management/ |title=Sunquest Blood Bank |publisher=Sunquest Information Systems, Inc |date=2021 |accessdate=18 November 2021}}</ref><ref name="SCCBlood20">{{cite web |url=https://www.softcomputer.com/products-services/blood-services/ |title=SCC's Blood Services Information Systems Suite |publisher=SCC Soft Computer |date=2021 |accessdate=18 November 2021}}</ref><ref name="HemasoftHome20">{{cite web |url=http://www.hemasoft.com/ |title=Hemasoft |publisher=Hemasoft Software SL |date=2021 |accessdate=18 November 2021}}</ref><ref name="TDMS_TDBloodBank20">{{cite web |url=https://www.technidata-web.com/en-gb/solutions-services/solutions/blood-banking |title=TD BloodBank |publisher=Technidata SAS |date=2021 |accessdate=18 November 2021}}</ref>:
All this culminates into multiple points:


* Manage inventory across multiple facilities.
* The hospital LIMS should have not only the essential clinical diagnostic functionality mentioned in the second chapter, but also most of the specialized functionality mentioned with the other laboratory types above.
* Manage donor and harvested tissues.
* The hospital LIMS should have the potential to take the place of the multiple informatics systems that typically run within a hospital lab, reducing data silos and minimizing the impact of system updates.
* Support positive patient identification (PPID).
* The hospital LIMS should have robust integration capabilities with EHRs and any other informatics systems that can’t be replaced by the LIMS.
* Support the ISBT 128 standard for medical products of human origin.
* The hospital LIMS should be highly flexible and configurable to take advantage of new test types, new departments, and more rapid testing (e.g., point-of-care testing).
* Support for both autologous and directed medical product management.
* Allow for emergency release of inventory.
* Allow for electronic crossmatch of human-based medical products.
* Manage medical product recall and documentation.
* Manage donor demographics, notification, scheduling and history.
* Manage donation drives and other campaigns.
* Track bag and supply lot numbers.
* Track quality control testing.
* Monitor access to and environmental conditions of supply fridges.
* Provide workflow management for non-standard patients.
* Support antibody screening processes.


==References==
==References==
{{Reflist|colwidth=30em}}
{{Reflist}}

Revision as of 19:27, 9 March 2022

MarkhamStouffvilleHospital23.jpg

The hospital lab is a unique creature in that it encompasses many departments within a hospital, often spread out over multiple areas. Most of the prior mentioned specialties, as well as many more, will make up the bulk of laboratory testing in a hospital.[1] By extension, the informatics solution used in the hospital must be equally robust. This means the LIMS should be sufficiently feature-rich to allow for pathology, hematology, microbiology, virology, molecular diagnostic and blood banking workflows (to name a few) to be readily implemented. Just about any type of specimen you could imagine may be taken[1], so the LIMS should have vast flexibility in its specimen types. Additionally, given the multiple departments and high daily specimen load of a hospital[1], the LIMS should be automation-friendly and support a wide array of instruments and equipment.

All this culminates into multiple points:

  • The hospital LIMS should have not only the essential clinical diagnostic functionality mentioned in the second chapter, but also most of the specialized functionality mentioned with the other laboratory types above.
  • The hospital LIMS should have the potential to take the place of the multiple informatics systems that typically run within a hospital lab, reducing data silos and minimizing the impact of system updates.
  • The hospital LIMS should have robust integration capabilities with EHRs and any other informatics systems that can’t be replaced by the LIMS.
  • The hospital LIMS should be highly flexible and configurable to take advantage of new test types, new departments, and more rapid testing (e.g., point-of-care testing).

References

  1. ↑ 1.0 1.1 Esposito, L. (30 January 2015). "Hospital Labs: Behind the Scenes". U.S. News & World Report. https://health.usnews.com/health-news/patient-advice/articles/2015/01/30/hospital-labs-behind-the-scenes. Retrieved 09 March 2022. 
Retrieved from "https://www.limswiki.org/index.php?title=User:Shawndouglas/sandbox/sublevel4&oldid=46942"