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

From LIMSWiki
Jump to navigationJump to search
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
Whether conducting the request for information (RFI) or request for proposal (RFP) process, a quality set of questions for potential vendors to respond to provides a solid base for helping evaluate and narrow down a vendor for your service. The RFI in particular is good for this sort of "fact finding," acting as an ideal means for learning more about a potential solution and how it can solve your problems, or when you're not even sure how to solve your problem yet. However, the RFI should not be unduly long and tedious to complete for prospective vendors; it should be concise, direct, and honest. This means not only presenting a clear and humble vision of your own organization and its goals, but also asking just the right amount of questions to allow potential vendors to demonstrate their expertise and provide a clearer picture of who they are. Some take a technical approach to an RFI, using dense language and complicated spreadsheets for fact finding. However, vendors appreciate a slightly more inviting approach, with practical questions or requests that are carefully chosen because they matter to you.<ref name="HolmesItsAMatch">{{cite web |url=https://allcloud.io/blog/its-a-match-how-to-run-a-good-rfi-rfp-or-rfq-and-find-the-right-partner/ |title=It's a Match: How to Run a Good RFI, RFP, or RFQ and Find the Right Partner |author=Holmes, T. |work=AllCloud Blog |date=n.d. |accessdate=21 August 2021}}</ref>
===Broad feature set of a pathology information management solution===


What follows are a carefully selected set of "questions" for cloud computing and cloud-related providers posed as, well, requests for information. This collection of questions is admittedly long. Keeping with advice about maintaining a concise RFI, you may not use all of these as part of your RFI process. Remember that an RFI is not meant to answer all of your questions, but rather is meant as a means to help narrow down your search to a few quality candidates while learning more about each other.<ref name="HolmesItsAMatch" /> Feel free to narrow this list down to those questions that are most important to you as part of this fact finding mission.
A pathology information management solution (PIMS) ...


Sources used to compile this selection of RFI questions include the six sources from section 6.4 (including APHL, Interfocus, ''Lab Manager'', LBMC, and Thomson Reuters)<ref name="APHLBreaking17">{{cite web |url=https://www.aphl.org/aboutAPHL/publications/Documents/INFO-2017Jun-Cloud-Computing.pdf |format=PDF |title=Breaking Through the Cloud: A Laboratory Guide to Cloud Computing |author=Association of Public Health Laboratories |publisher=Association of Public Health Laboratories |date=2017 |accessdate=21 August 2021}}</ref><ref name="IFAhelp20">{{cite web |url=https://www.mynewlab.com/blog/a-helpful-guide-to-cloud-computing-in-a-laboratory/ |title=A Helpful Guide to Cloud Computing in a Laboratory |work=InterFocus Blog |publisher=InterFocus Ltd |date=05 October 2020 |accessdate=21 August 2021}}</ref><ref name="LBMCNine21">{{cite web |url=https://www.lbmc.com/blog/questions-cloud-service-providers/ |title=Nine Due Diligence Questions to Ask Cloud Service Providers |author=LBMC |work=LBMC Blog |date=24 February 2021 |accessdate=21 August 2021}}</ref><ref name="WardCloud19">{{cite web |url=https://www.labmanager.com/business-management/cloud-computing-for-the-laboratory-736 |title=Cloud Computing for the Laboratory: Using data in the cloud - What it means for data security |author=Ward, S. |work=Lab Manager |date=09 October 2019 |accessdate=21 August 2021}}</ref><ref name="EusticeUnder18">{{cite web |url=https://legal.thomsonreuters.com/en/insights/articles/understanding-data-privacy-and-cloud-computing |title=Understand the intersection between data privacy laws and cloud computing |author=Eustice, J.C. |work=Legal Technology, Products, and Services |publisher=Thomson Reuters |date=2018 |accessdate=21 August 2021}}</ref><ref name="TRThree21">{{cite web |url=https://legal.thomsonreuters.com/blog/3-questions-you-need-to-ask-your-cloud-vendors/ |title=Three questions you need to ask your cloud vendors |author=Thomson Reuters |work=Thomson Reuters Legal Blog |date=03 March 2021 |accessdate=21 August 2021}}</ref>, the five sources from the managed security services provider (MSSP) RFI/RFP template included in Appendix 3 of this guide (there's a lot of crossover, actually)<ref name="Korff12Rev19">{{cite web |url=https://expel.io/blog/12-revealing-questions-when-evaluating-mssp-mdr-vendor/ |title=12 revealing questions to ask when evaluating an MSSP or MDR vendor |author=Korff, Y. |work=Expel blog |publisher=Expel, Inc |date=19 February 2019 |accessdate=21 August 2021}}</ref><ref name="NTTSHowTo16">{{cite web |url=https://www.nttsecurity.com/docs/librariesprovider3/resources/us_whitepaper_mssp_rfp_uea_v1 |title=How to Write an MSSP RDP |publisher=NTT Security |date=September 2016 |accessdate=21 August 2021}}</ref><ref name="SWGuideToBuild">{{cite web |url=https://pcdnscwx001.azureedge.net/~/media/Files/US/White%20Papers/SecureWorksNCO411PGuidetoBuildingaCloudRFPTemplate.ashx?modified=20170714201638 |archiveurl=https://web.archive.org/web/20210508225741/https://pcdnscwx001.azureedge.net/~/media/Files/US/White%20Papers/SecureWorksNCO411PGuidetoBuildingaCloudRFPTemplate.ashx?modified=20170714201638 |format=DOCX |title=Secureworks Guide to Building a Cloud MSSP RFP Template |publisher=Secureworks |archivedate=08 May 2021 |accessdate=21 August 2021}}</ref><ref name="SolutionaryRFP15">{{cite web |url=https://docecity.com/rfp-sample-questions-for-managed-security-services.html |title=RFP/RFI Questions for Managed Security Services: Sample MSSP RFP Template |publisher=Solutionary, Inc |date=September 2015 |accessdate=21 August 2021}}</ref><ref name="SAMCloudMiss20">{{cite web |url=https://beta.sam.gov/opp/91dc7217b32b459695b27339f4b5d9aa/view |title=Cloud Mission Support Request for Information |work=SAM.gov |author=U.S. Department of State |date=24 October 2020 |accessdate=21 August 2021}}</ref>, and the following:


* Cloud Security Alliance's ''Cloud Controls Matrix v4''<ref name="CSACloudCont4">{{cite web |url=https://cloudsecurityalliance.org/artifacts/cloud-controls-matrix-v4/ |format=xlsx |title=Cloud Controls Matrix v4 |publisher=Cloud Security Alliance |date=15 March 2021 |accessdate=21 August 2021}}</ref>
* '''automated reflex testing''': Some PIMS vendors include pre-loaded, customizable lists of reflex tests associated with certain pathology procedures and their associated diagnoses. Optimally, these reflex texts are automatically suggested at specimen reception, based on specimen and/or pathology test type.<ref name="NPSoftware13">{{cite web |url=https://www.novopath.com/content/pdf/novopathbrochure.pdf |format=PDF |title=NovoPath - Software Advancing Patient Diagnostics |publisher=NovoPath, Inc |date=2013 |accessdate=05 September 2020}}</ref><ref name="PsycheWindo">{{cite web |url=https://psychesystems.com/enterprise-laboratory-information-software/windopath/ |title=WindoPath Ē.ssential |publisher=Psychē Systems Corporation |accessdate=05 September 2020}}</ref> Examples of pathology-driven reflex testing in use today include testing for additional biomarkers for non-small-cell lung carcinoma (NSCLC) adenocarcinoma<ref name="SundinPath19">{{cite journal |url=https://www.medlabmag.com/article/1619 |title=Pathology-Driven Reflex Testing of Biomarkers |journal=Medical Lab Management |author=Sundin, T. |volume=8 |issue=11 |page=6 |year=2019}}</ref>, HPV testing in addition to cervical cytology examination<ref name="FDANewApproaches19">{{cite web |url=https://www.fda.gov/media/122799/download |title=New Approaches in the Evaluation for High-Risk Human Papillomavirus Nucleic Acid Detection Devices |author=U.S. Food and Drug Administration |publisher=U.S. Food and Drug Administration |date=08 March 2019 |accessdate=05 September 2020}}</ref><ref name="StolerAdjunctive15">{{cite book |chapter=Chapter 9: Adjunctive Testing |title=The Bethesda System for Reporting Cervical Cytology |author=Stoler, M.H.; Raab, S.S.; Wilbur, D.C. |editor=Nayar, R.; Wilbur, D. |publisher=Springer |pages=287–94 |year=2015 |doi=10.1007/978-3-319-11074-5_9 |isbn=9783319110745}}</ref> (discussed further in "adjunctive testing"), and additional automatic testing based off routine coagulation assays at hemostasis labs.<ref name="MohammedDevel19">{{cite journal |title=Development and implementation of an expert rule set for automated reflex testing and validation of routine coagulation tests in a large pathology network |journal=International Journal of Laboratory Hematology |author=Mohammed, S.; Priebbenow, V.U.; Pasalic, L. et al. |volume=41 |issue=5 |pages=642–49 |year=2019 |doi=10.1111/ijlh.13078 |pmid=31271498}}</ref>
* Ireland's Office of Government Procurement ''Cloud Services Procurement Guidance Note''<ref name="OGPInform21">{{cite web |url=https://ogp.gov.ie/information-notes/ |title=Cloud Services Procurement Guidance Note |publisher=Ireland Office of Government Procurement |date=09 February 2021 |accessdate=21 August 2021}}</ref>
* U.S. Internal Revenue Service RFI Cloud Response document<ref name="IRSRFICloud18">{{cite web |url=https://cic.gsa.gov/documents/IRS-Cloud-Services-RFI.docx |format=DOCX |title=IRS RFI Cloud Response |publisher=Internal Revenue Service |date=January 2018 |accessdate=21 August 2021}}</ref>


* '''adjunctive testing''': Adjunctive testing is testing "that provides information that adds to or helps interpret the results of other tests, and provides information useful for risk assessment."<ref name="SegensAdjunct11">{{cite web |url=https://medical-dictionary.thefreedictionary.com/adjunct+test |title=adjunct test |work=Segen's Medical Dictionary |date=2011 |accessdate=05 September 2020}}</ref> A common adjunctive test performed in [[cytopathology]] is HPV testing.<ref name="FDANewApproaches19" /><ref name="StolerAdjunctive15" /> The FDA described this as such in 2003, specifically in regards to expanding the use of the Digene HC2 assay as an adjunct to cytology<ref name="FDANewApproaches19" />:


==RFI/RFP introduction==
<blockquote>In women 30 years and older, the HC2 High-Risk HPV DNA test can be used with Pap to adjunctively screen to assess the presence or absence of high-risk HPV types. This information, together with the physician’s assessment of cytology history, other risk factors, and professional guidelines, may be used to guide patient management.</blockquote>
If you're conducting a full RFI or RFP, you're going to lead with the standard components of an RFI or RFP, including:


* a table of contents;
:Some PIMS vendors allow users to manually add an adjunctive test to a primary pathology test, or in some cases this may be enabled as part of an automated reflex testing process.<ref name="TDHistoCyto">{{cite web |url=https://www.technidata-web.com/solutions-services/disciplines/anatomic-pathology |title=TD HistoCyto Livextens |publisher=Technidata SAS |accessdate=05 September 2020}}</ref> However, ensure that any such solution is capable of feeding any adjunctive test results into the final report (see the subsection on this topic).
* an honest introduction and overview of your organization, its goals and problems, and the services sought to solve them;
* details on how the RFI or RFP evaluation process will be conducted;
* basis for award (if an RFP);
* the calendar schedule (including times) for related events;
* how to submit the document and any related questions about it, including response format; and
* your organization's background, business requirements, and current technical environment.


* '''demand management''': Similar to test optimization or clinical decision support, demand management mechanisms help laboratories reduce the amount of unnecessary and duplicate testing they perform. The idea of using demand management to reduce unnecessary pathology testing has been around since at least the beginning of the twenty-first century, if not well before, in the form of decision support systems and order request menus of informatics systems.<ref name="RaoPath03">{{cite journal |title=Pathology tests: is the time for demand management ripe at last? |journal=Journal of Clinical Pathology |author=Rao, G.G.; Crook, M.; Tillyer, M.L. |volume=56 |issue=4 |pages=243–48 |year=2003 |doi=10.1136/jcp.56.4.243 |pmid=12663633 |pmc=PMC1769923}}</ref> Lang described what the process of demand management would look like in a system like a [[laboratory information management system]] (LIMS) in 2013<ref name="LangLab13">{{cite journal |title=Laboratory demand management of repetitive testing – time for harmonisation and an evidenced based approach |journal=Clinical Chemistry and Laboratory Medicine |author=Lang, T. |volume=51 |issue=6 |pages=1139–40 |year=2013 |doi=10.1515/cclm-2013-0063 |pmid=23420284}}</ref>:


==Organization basics==
<blockquote>When implementing a demand management tool it is important that the system used to manage a laboratory workload can correctly identify the patient and match requests with the patient’s medical record. Ideally there should be one unique identifier used (e.g., NHS number in the UK), which will allow the LIMS to interrogate the patient’s previous pathology result to allow identification of duplicate or inappropriate requests. If a subsequent request is blocked, then it is also important that there is real-time notification of a potential redundant test so that the requestor can make an informed choice on the clinical need of the test and if it is required to override the rule. It is important that there is a facility whereby the laboratory or requestor can record the reason for blocking a request or overriding the rule.</blockquote>


===Primary business objectives===
:Today, some PIMS are designed to allow configurable rules and parameters to check for duplicate and unnecessary tests at various levels (e.g., by test ID or catalog type, activity type, or some other order level).<ref name="MorrisDemand18">{{cite journal |title=Demand management and optimization of clinical laboratory services in a tertiary referral center in Saudi Arabia |journal=Annals of Saudi Medicine |author=Morris, T.F.; Ellison, T.L.; Mutabbagani, M. et al. |volume=38 |issue=4 |pages=299–304 |year=2018 |doi=10.5144/0256-4947.2018.299 |pmid=30078029 |pmc=PMC6086671}}</ref><ref name="DXCLab">{{cite web |url=https://www.dxc.technology/healthcare/offerings/139499/139776-dxc_laboratory_information_management_lims |title=DXC Laboratory Information Management (LIMS) |publisher=DXC Technology Services, LLC |accessdate=05 September 2020}}</ref>
Please describe the primary business objectives for your organization.


* '''consent management''': In clinical medicine, patients typically must sign a form indicating informed consent to medical treatment.<ref name="AMAInformed">{{cite web |url=https://www.ama-assn.org/delivering-care/ethics/informed-consent |title=Informed Consent |work=Code of Medical Ethics |publisher=American Medical Association |accessdate=22 September 2020}}</ref> Biobanking facilities, which store biospecimens, also must collect consent forms regarding how a patient's biospecimens may be used.<ref name="AveryBiobank18">{{cite web |url=https://www.biobanking.com/biobanking-consent-informing-human-subjects-of-the-possibilities/ |title=Biobanking Consent: Informing Human Subjects of the Possibilities |author=Avery, D. |work=Biobanking.com |date=16 July 2018 |accessdate=22 September 2020}}</ref> In all cases, these consent documents drive how and when certain actions take place. Though not common, some LIMS like LabVantage Pathology by Software Point<ref name="SPLabVantPath">{{cite web |url=https://softwarepoint.com/solutions/product/labvantage-pathology |title=LabVantage Pathology |publisher=Software Point Oy |accessdate=22 September 2020}}</ref> provide consent management mechanisms within their PIMS, giving pathologists the ability to quickly verify consent details electronically. In biobanking solutions, this consent management process may be more rigorous to ensure biospecimen donors' preferences and regulatory requirements are being carefully followed. For example, the system may need to be able to prevent further use of a biospecimen and trigger sample and data deletion protocols when a donor withraws their consent to use.<ref name="BikaNCV15">{{cite web |url=https://www.bikalims.org/downloads/bika-open-source-biobank-management-system/at_download/file |format=PDF |title=NCB-H3A Cape Town Biobank Management System - Functional Requirements Overview & Phase I Objectives |author=SANBI; Bika Lab Systems |publisher=Bika Lab Systems |date=20 November 2015 |accessdate=22 September 2020}}</ref>


* '''case management and review''': Most PIMS provide a means for managing pathology cases, recorded instances of disease and its attendant circumstances.<ref name="FarlexCase12">{{cite web |url=https://medical-dictionary.thefreedictionary.com/case |title=case |work=Farlex Partner Medical Dictionary |date=2012 |accessdate=25 September 2020}}</ref> This includes the management of case history, a collection of data concerning an individual, their family, their environment, their medical history, and other other information valuable for analyzing, diagnosing, reviewing, or otherwise instructing others on the case.<ref name="MKECase03">{{cite web |url=https://medical-dictionary.thefreedictionary.com/case |title=case |work=Miller-Keane Encyclopedia and Dictionary of Medicine, Nursing, and Allied Health, Seventh Edition |date=2003 |accessdate=25 September 2020}}</ref> Having an information system to better manage data entry, data analysis, case tracking, and case storage may aid in secondary and internal case reviews before final report, which have been shown to improve diagnostic accuracies and overall experiential knowledge of pathologists.<ref name="HuckKnowledge15">{{cite book |chapter=Chapter 7: Knowledge, Training, and Experience |title=Error Reduction and Prevention in Surgical Pathology |author=Huck, A.; Nosé, V. |editor=Nakhleh, R.E. |publisher=Springer |pages=103–114 |year=2015 |isbn=9781493923397 |url=https://books.google.com/books?id=HXAKBwAAQBAJ&pg=PA103}}</ref> Aspects of case manamagement and review that a PIMS may handle include automatic case creation, automatic and priority case assignment, and automatic case tracking, as well as limit case acces based on user permissions, and send alerts for clinical history follow-ups and other case statuses.<ref name="LLAnatom" /><ref name="PIMSPathX">{{cite web |url=http://pathxlis.com/downloads/PDFs/PathX%20-%20Capabilities%20Brochure.pdf |format=PDF |title=PathX Laboratory Information System |publisher=Physicians Independent Management Services |accessdate=25 September 2020}}</ref><ref name="LBAperioPathDX">{{cite web |url=https://www.leicabiosystems.com/digital-pathology/manage/aperio-path-dx/ |title=Aperio Path DX - Case Management Software |publisher=Leica Biosystems Nussloch GmbH |accessdate=25 September 2020}}</ref> Note that a handful of vendors such as Leica Biosystems provide stand-alone case management solutions that can be integrated with instruments and other LIS systems.<ref name="LBAperioPathDX" />


* '''workflow management''': The tools for workflow management have become increasingly common in PIMS and other laboratory informatics applications over the years, with the idea of using automation to improves efficiencies and accuracies in the lab. However, workflows and protocols can differ—sometimes significantly—from one pathology lab to another. Being able to configure workflow pathways in the PIMS to be compliant with required testing protocols is vital. This is especially important with the gradual transition to more digital pathology methods, where digitally sharing cases and automatically scanned slide images has great value.<ref name="XifinIsYour20">{{cite web |url=https://www.xifin.com/resources/blog/201912/your-lab-ready-ai-digital-pathology-workflow |title=Is Your Lab Ready for an AI Digital Pathology Workflow? |publisher=XIFIN, Inc |date=03 January 2020 |accessdate=25 September 2020}}</ref> As such, vendors such as Orchard Software and XIFIN provide solutions with configurable workflows to help labs translate their workflows into the system.<ref name="OSOrchPath" /><ref name="XIFINLabInfoSys">{{cite web |url=https://www.xifin.com/products/laboratory-information-system |title=Laboratory Information System |publisher=XIFIN, Inc |accessdate=25 September 2020}}</ref>


* '''speech recognition and transcription management''': Like other medical fields, pathologists may utilize dictation and transcription services within their workflow. This has traditionally involved the pathologist speaking while a transcriptionist manually records the words to paper, or the pathologist scribbling notes in shorthand, with the transcriptionist "translating" the notes to usable clinical documentation. This could include anything from specimen descriptions and diagnoses to pathology obsevations and procedure notes. PIMS vendors have over the years added more automated methods to such tasks in their solutions, however, such as speech recognition modules and transcription management tools that, for example, automatically assign recordings to a transcriber's pending work list.<ref name="NPSoftware13" /><ref name="SPLabVantPath" /><ref name="AspyraAnaPath" /><ref name="PIMSPathX" />


:It's important to note, however, though PIMS vendors may market the speech recognition component of their solution at being 99 percent effective, past studies have shown 88.9 to 96 percent accuracy, though with tiny annual gains as the technology matures.<ref name="HodgsonRisks16">{{cite journal |title=Risks and benefits of speech recognition for clinical documentation: A systematic review |journal=JAMIA |author=Hodgson, T.; Coiera, E. |volume=23 |issue=e1 |pages=e169–79 |year=2016 |doi=10.1093/jamia/ocv152 |pmid=26578226 |pmc=PMC4954615}}</ref><ref name="ZhouAnal18">{{cite journal |title=Analysis of Errors in Dictated Clinical Documents Assisted by Speech Recognition Software and Professional Transcriptionists |journal=JAMA Network Open |author=Zhou, L.; Blackley, S.V.; Kowalski, L. et al. |volume=1 |issue=3 |at=e180530 |year=2018 |doi=10.1001/jamanetworkopen.2018.0530 |pmid=30370424 |pmc=PMC6203313}}</ref> If speech recognition is being used in lieu of a hired transcriptionist, it's especially vital to add manual editing and review before reporting.<ref name="ZhouAnal18" /><ref name="MatthewsWhyMed19">{{cite web |url=https://www.healthitoutcomes.com/doc/why-medical-dictation-is-still-better-than-voice-recognition-for-now-0001 |title=Why Medical Dictation Is Still Better Than Voice Recognition ... For Now |author=Matthews, K. |work=Health IT Outcomes |date=20 December 2019 |accessdate=25 September 2020}}</ref>


* '''storage and tissue bank management''': Biorepositories and pathology laboratories go hand-in-hand. A significant example can be found with the relationship medical school biorepositories have with their pathology labs and departments, as with, for example, Duke University<ref name="DukeBiorep">{{cite web |url=https://pathology.duke.edu/core-facilities-services/biorepository-precision-pathology-center |title=Biorepository & Precision Pathology Center |publisher=Duke University School of Medicine |accessdate=22 September 2020}}</ref>, University of Illinois Chicago<ref name="UIC_UIHealthBio">{{cite web |url=https://rrc.uic.edu/cores/rsd/biorepository/ |title=UI Health Biorepository |publisher=University of Illinois Chicago |accessdate=22 September 2020}}</ref>, and the Icahn School of Medicine at Mount Sinai.<ref name="IcahnBiorep">{{cite web |url=https://icahn.mssm.edu/research/portal/resources/deans-cores/biorepository-and-pathology |title=Biorepository and Pathology |publisher=Icahn School of Medicine at Mount Sinai |accessdate=22 September 2020}}</ref> However, even small pathology laboratories must also responsibly store and track their specimens, blocks, and slides, as well as the storage variables affecting them. Any reputable laboratory informatics solution will be able to track the location of such items through barcode or RFID support, as well as allowing for the creation of named storage locations in the system. However, some informatics solutions like AgileBio's LabCollector go a step further, providing data logging modules that are capable of connecting to data logger hardware and other sensors that capture environmental storage information such as temperature, humidity, light level, carbon dioxide level, and pressure. When a variable is out of range, an alert can be sent and logged.<ref name="AgileBioDataLog">{{cite web |url=https://www.labcollector.com/labcollector-lims/add-ons/data-logger/ |title=Data Logger |publisher=AgileBio |accessdate=22 September 2020}}</ref> And full-fledged biorepository management LIMS may have all the bells and whistles, including randomized biospecimen location auditing.<ref name="AIBiobank">{{cite web |url=https://www.autoscribeinformatics.com/industries/biobank-management-systems |title=Biobank Management LIMS |publisher=Autoscribe Informatics, Inc |date=22 September 2020}}</ref>


===Organization history===
* '''task management''': Task management is a typical feature of a laboratory informatics solution, giving laboratorians the ability to assign tasks to individuals or groups of individuals, including analyses, results review, and more. In pathology labs, additional task and even management may include, for example, case assignment, slide or block assignment, grossing, staining, or some other pathology task. Additionally, some may incorporate this task management and tracking into a dashboard, to facility timely access to short-term status individual cases and specimens, and long-term aggregate data about cases, workflow, and workloads.<ref name="HalwaniAReal16">{{cite journal |title=A real-time dashboard for managing pathology processes |journal=Journal of Pathology Informatics |author=Halwani, F.; Li, W.C.; Banerjee, D. et al. |volume=7 |at=24 |year=2016 |doi=10.4103/2153-3539.181768 |pmid=27217974 |pmc=PMC4872478}}</ref>
Please give some background on your organization's history, including how long it has been offering cloud computing services.


* '''billing management with code support''': Instead of turning to a separate billing solution, pathology labs can often turn to PIMS for billing management. Vendors of LIS and LIMS have recognized not only the value of adding billing management to their solutions but also the many benefits that come with tying in diagnosis and billing code support. For example, a pathologist scanning a specimen into the system can not only have a case automatically generated but also auto-generate diagnosis codes based on the specimen or slide's code. Additionally, as has been witnessed during the [[COVID-19]] pandemic, billing rules may change rapidly during extraordinary events, requiring rapid used-defined billing rule changes.<ref name="FerranteCOVID20">{{cite web |url=https://www.foley.com/en/insights/publications/2020/04/covid19-cms-monumental-changes-medicare-telehealth |title=COVID-19: CMS Issues Monumental Changes to Medicare Telehealth: What You Need to Know |author=Ferrante, T.B.; Goodman, R.B.; Wein, E.H. |work=Insights, a Foley & Lardner LLP Blog |date=03 April 2020 |accessdate=25 September 2020}}</ref> As such, support for CPT, ICD-10, SNOMED CT, and other types of autocoding are somewhat common in today's PIMS.<ref name="NPSoftware13" /><ref name="LLAnatom" /><ref name="PIMSPathX" /><ref name="AspyraAnaPath" />


* '''reflex and adjunctive test reporting''': Ensure that a PIMS is capable of feeding any adjunctive test results into the final report, along with the results from the primary tests. Using adjunctive HPV test results as an example, the report should optimally include details such as assay name, manufacturer, the HPV types it covers, results, and any applicable educational notes and suggestions.<ref name="StolerAdjunctive15" /> Be careful with simple color-coding of results for interpretation, as they can be easily misinterpreted, including by the colorblind. A combination of symbol with color will help limit such misinterpretation.<ref name="SundinPath19" />


* '''structured data entry''': The concept of structured data entry (SDE) is relatively simple, but it may still get taken for granted. At its core, SDE is all about ensuring that entered data is based on a set of predefined conditions or rules, usually implemented through standardized forms with pre-determined drop-down and auto-populated fields.<ref name="PHIIUnderst">{{cite web |url=https://www.phii.org/sites/default/files/resource/files/Understanding%20Clinical%20Data%20and%20Workflow%20Guide.docx |format=DOCX |title=Analyzing Clinical Data and Workflows - 4. Understanding Clinical Data and Workflow |work=EHR Toolkit |author=Public Health Informatics Institute |accessdate=22 September 2020}}</ref> This typically confers numerous advantages, including easier data entry, easier and more standardized reporting, decrease costs, improve translational research, and ensure better compatibility and integration across different information systems.<ref name="PHIIUnderst" /><ref name="BataviaUsing18">{{cite journal |title=Using structured data entry systems in the electronic medical record to collect clinical data for quality and research: Can we efficiently serve multiple needs for complex patients with spina bifida? |journal=Journal of Pediatric Rehabilitative Medicine |volume=11 |issue=4 |pages=303–09 |year=2018 |doi=10.3233/PRM-170525 |pmid=30507591 |pmc=PMC6491202}}</ref> As such, some PIMS vendors like NovoPath and Orchard Software describe their solutions as having SDE elements such as enabling intelligent auto-loading of diagnosis and billing codes during case loading, allowing input fields to be required, and synoptic reporting support.<ref name="NPSoftwarePDF">{{cite web |url=https://www.novopath.com/content/pdf/novopathbrochure.pdf |format=PDF |title=NovoPath - Software Advancing Patient Diagnostics |publisher=NovoPath, Inc |date=2013 |accessdate=22 September 2020}}</ref><ref name="OSOrchPath">{{cite web |url=https://www.orchardsoft.com/orchard-pathology.html |title=Orchard Pathology |publisher=Orchard Software Corporation |accessdate=22 September 2020}}</ref>


* '''synoptic reporting''': [[LIS feature#Synoptic reporting|Synoptic reporting]] involves a structured, pre-formatted "checklist" of clinically and morphologically relevant data elements that help make pathology reporting more efficient, uniform, and relevant to internal and external stakeholders. Another way to put this is that synoptic reporting is SDE applied to the pathology report, often based upon specific reporting protocols by professional or standards organizations like the College of American Pathologists (CAP).<ref name="LLAnatom">{{cite web |url=https://www.ligolab.com/solutions/anatomic-pathology-solution |title=Anatomic Pathology Solutions |publisher=LigoLab, LLC |accessdate=23 September 2020}}</ref><ref name="NPSoftwarePDF" /> Support for synoptic reporting methods is typical within PIMS solutions, including support for configurable templates that can be adapted to changing and custom reporting protocols.


* '''correlative and consultive reporting''': In the late 1930s, the concept of correlating pathology results with clinical observations (and pathology) was beginning to be addressed in student textbooks.<ref name="JAMATextbook40">{{cite journal |title=''Textbook of Pathology. A Correlation of Clinical Observations and Pathological Findings'' |journal=JAMA |volume=114 |issue=2 |page=184 |year=1940 |doi=10.1001/jama.1940.02810020088032}}</ref> Today, the concept remains integral in medical practice and toxicologic study reporting.<ref name="SmithConstruct16">{{cite journal |title=Constructing Comments in a Pathology Report: Advice for the Pathology Resident |journal=Archives of Pathology & Laboratory Medicine |author=Smith, S.M.; Yearsley, M. |volume=140 |issue=10 |pages=1023–24 |year=2016 |doi=10.5858/arpa.2016-0220-ED |pmid=27684971}}</ref><ref name="RamaiahInterp17">{{cite journal |title=Interpreting and Integrating Clinical and Anatomic Pathology Results: Pulling It All Together |journal=Toxicologic Pathology |author=Ramaiah, L.; Hinrichs, M.J.; Skuba, E.V. et al. |volume=45 |issue=1 |pages=223–37 |year=2017 |doi=10.1177/0192623316677068 |pmid=27879439}}</ref><ref name="AulbachOver19">{{cite journal |title=Overview and considerations for the reporting of clinical pathology interpretations in nonclinical toxicology studies |journal=Veterinary Clinical Pathology |author=Aulbach, A.; Vitsky, A.; Arndt, T. et al. |volume=48 |issue=3 |pages=389–99 |year=2019 |doi=10.1111/vcp.12772 |pmid=31556157}}</ref> On the clinical side, a pathologist may include the phrase "clinical correlation is recommended" and additional comments. And in some cases, a third-party pathology consultation, with their own respective comments, is involved with specimen analysis.<ref name="KaplanWhatIs14">{{cite web |url=https://blog.corista.com/corista-digital-pathology-blog/bid/389513/What-is-a-Pathology-Consultation-When-is-it-Used |title=What is a Pathology Consultation? When is it Used? |author=Kaplan, K. |work=Corista Digital Pathology Blog |date=19 June 2014 |accessdate=23 September 2020}}</ref> These correlative and consultive comments or reports play an important part in the overall final pathology report and should not be omitted, particularly if differing opinions are involved. Vendors such as Orchard Software, LigoLab, and Aspyra tout their solutions' ability to tie together multiple reports and comments across pathology disciplines and consultants into one concise report.<ref name="OSOrchPath" /><ref name="LLAnatom" /><ref name="AspyraAnaPath">{{cite web |url=http://aspyra.com/anatomic-pathology/ |title=Anatomic Pathology |publisher=Aspyra, LLC |accessdate=23 September 2020}}</ref>


* '''CAP Cancer Reporting Protocol support''': Previously mentioned was CAP and its reporting protocols. In particular, CAP has its Cancer Reporting Protocols, which the CAP describe as providing "guidelines for collecting the essential data elements for complete reporting of malignant tumors and optimal patient care."<ref name="CAPCancerProt20">{{cite web |url=https://www.cap.org/protocols-and-guidelines/cancer-reporting-tools/cancer-protocol-templates |title=Cancer Protocol Templates |publisher=College of American Pathologists |date=April 2020 |accessdate=23 September 2020}}</ref> In conjunction with its electronic Cancer Checklists (eCCs)<ref name="CAPeCC">{{cite web |url=https://www.cap.org/laboratory-improvement/proficiency-testing/cap-ecc |title=CAP eCC |publisher=College of American Pathologists |accessdate=23 September 2020}}</ref>, pathologists are able to integrate CAP cancer reporting protocols of tumors, resections, and select biopsies into their PIMS' workflow and ensure proper reporting outcomes. Some PIMS vendors (e.g., Orchard Software, LigoLab<ref name="OSOrchPath" /><ref name="LLAnatom" />) explicitly indicate their solution integrates CAP's eCC templates and reporting protocols into their solution.


===Financial stability===
* '''annotated organ mapping''': In the world of PIMS, organ mapping refers to the concept of placing location-specific diagnostic information from specimen analyses into an anatomical diagram, typically during reporting, to more clearly communicate the results of those analyses. PIMS vendor WebPathLab, Inc. demonstrates this concept well with its Auto Organ Map Module, which not only shows an organ map in the rport but also simplifies data entry for the pathologist using SDE.<ref name="WPLAuto19">{{cite web |url=https://www.youtube.com/watch?v=NLr5_pLgYpg |title=AutoProstateMap |work=YouTube |author=WebPathLab, Inc |date=22 April 2019 |accessdate=23 September 2020}}</ref><ref name="WPLGUAuto">{{cite web |url=http://webpathlab.com/solutions/gu-auto-organ-map/ |title=GU Auto Organ Map Module |publisher=WebPathLab, Inc |accessdate=23 September 2020}}</ref> They use the prostate as an example, and explain that "selecting the predetermined number of quadrants in the prostate &#91;diagram&#93;, the system autopopulates the specimen description to each corresponding quadrant, and autofills the text for the Gross Description field, leaving only the dimension of each core to be entered by the grosser." NovoPath and Psyche Systems Corporation are additional examples of vendors incorporating organ mapping into their PIMS.<ref name="PsycheWindo" /><ref name="NPSoftwarePDF" />
Please provide information concerning the financial stability of your organization. If your organization is public, please include relevant documents such as annual reports and supporting financial statements. If private, please include documentation that supports the representation of your organization as a stable, profitable, and sustainable one. If not profitable, please provide details about your organization's path towards profitability.
 
 
 
 
 
 
 
===Cloud services offered===
Please describe the primary cloud computing or cloud-related services (e.g., software as a service or SaaS) offered by your organization, particularly any of which may be relevant based upon our company's stated needs. If the services are tiered, explain the different levels of service and any significant exceptions and differences separating the levels. Don't forget to describe the capabilities of your hybrid and multicloud offerings.
 
 
 
 
 
 
 
===Expected level of integration or interoperability===
Please describe how you anticipate your cloud solutions being able to readily integrate or have base interoperability with a client's systems and business processes, while making it easier for the client to perform their tasks in the cloud.
 
 
 
 
 
 
 
===Details about those cloud services===
Please provide details about:
 
* number of clients specifically using your organization's cloud computing or cloud-related services;
* how long each of those services has been offered;
* the growth rate of those services over the prior fiscal year;
* the average historical downtime of a given cloud service;
* how those services or your organization overall are ranked by top research firms such as Gartner and Forrester; and
* any awards received for your organization's cloud computing or cloud-related services.
 
 
 
 
 
 
 
===Vision and investment in those cloud services===
Please provide details about the vision and future direction for choosing, developing, and implementing new in-house or third-party technologies as part of your organization's cloud computing initiative. Additionally, discuss the level of investment made by your organization towards researching, adopting, and integrating newer, more secure technologies and processes into your organization's operations.
 
 
 
 
 
 
 
===Experience and references===
Please provide details on:
 
* how many clients you provide (or have provided) cloud computing and cloud-related services to in our organization's industry;
* whether any of them are willing to act as references for your services;
* what experience your organization has in meeting the unique regulatory requirements of our industry;
* any examples of clients being a learning source for improving your service; and
* any whitepapers, reports, etc. authored by your organization that are relevant to our industry.
 
 
 
 
 
 
 
==Infrastructure, security, and related policies==
 
===Internal security policy and procedure===
Please describe your internal policy and procedure (P&P) regarding security within your organization, including any standards your organization has adopted as part of that P&P. Address any ancillary security policies regarding, e.g., acceptable use of technology, remote and from-home work, and security awareness training.
 
 
 
 
 
 
 
===Business continuity and disaster recovery policy===
Please describe your organization's P&P regarding business continuity and disaster recovery.
 
 
 
 
 
 
 
===Data centers and related infrastructure===
Please describe how your organization organizes its data centers and related infrastructure to optimally provide its cloud computing and cloud-related services. Additionally, address concerns about:
 
* whether or not your organization owns and manages the data centers;
* where those data centers are located;
* where our data will be located;
* what specifications and encryption types are used for in-transit and at-rest data;
* what level of availability is guaranteed for each data center;
* what level of redundancy is implemented within the data centers;
* what disposal and data destruction policies are in place for end-of-life equipment;
* how that redundancy limits service interruptions should a particular data center go offline;
* what level of cloud-based scalability is available to clients with growth or contraction states; and
* what qualifications and certifications apply to each data center.
 
 
 
 
 
 
 
===Physical security at data centers===
Please describe the physical security (e.g., locks, badges, physical security perimeters, surveillance systems, etc.) and continuity (e.g., fire suppression, backup power, etc.) measures put in place at your organization's data centers. Also address visitor procedures and how they are conducted. How are unauthorized access attempts at data centers responded to?
 
 
 
 
 
 
 
===Staffing at data centers===
Please describe the staffing procedures at these data centers, including what percentage of overall staff will actually have authorized access to client data. Clearly define any implemented classifications of staff based on level of support or data sensitivity, as well as any related certifications and training required at each support or data sensitivity level. Are contractors treated any differently? Finally, describe what background checks or screening procedures, if any, are implemented towards any organizational personnel and third-parties (e.g., contractors, service technicians) interacting with systems containing client data.
 
 
 
 
 
 
 
===Independent infrastructure review===
If your organization has received an independent review of its cloud infrastructure and services (e.g., SOC 2), please provide details of this review, preferably with the full report, but if not, with critical details such as who, what, when, where, scope, frequency of testing, and a summary. If your organization has not completed such an independent review, please provide details of any plans or ongoing efforts towards such a review.
 
 
 
 
 
 
 
===Internal infrastructure review===
If your organization has performed an internal review of its cloud infrastructure and services, please provide details of this review, with critical details such as who, what, when, where, scope, frequency of testing, and a summary. If your organization has not completed such an internal review, please provide details of any plans or ongoing efforts towards such a review. If your organization conducts internal "red team" or "attack-and-defense" exercises, describe them, their frequency, and how resulting information is acted upon.
 
 
 
 
 
 
 
===Auditing of your operations===
If the results of your independent and/or internal review cannot be shared, will your organization allow us to—on our own or through a third party—audit your operations, with the goal of determining the appropriateness of your organization's implemented safeguards?
 
 
 
 
 
 
 
===Auditing of client data===
Please describe how your organization handles requests from outside entities for client data and notifies clients when such requests are made. If subpoenas, court orders, search warrants, or other law enforcement actions were to take place, describe how you would maintain any privileged, confidential, or otherwise sensitive information as being protected. Do you have legal representation should these issues arise?
 
 
 
 
 
 
===Extraction of client data===
Please explain how clients may extract data from your cloud service (i.e., address data portability) on-demand, including particulars about data formats and transfer methods.
 
 
 
 
 
 
 
==Base cloud security==
 
===Company philosophy or approach===
Please describe how your cloud services address the ephemeral nature of cloud computing while at the same time helping clients maintain their overall security posture. Explain your organization's approach to its security team, including whether or not a dedicated team of security researchers are utilized. If such a team exists, also explain how that research from that team is incorporated into protecting your organization's cloud solution or infrastructure. Finally, describe your team's overall approach to monitoring, analysis, and correlation of security threats, including how automated and human-based analyses are balanced in their approaches and in their handoff to each other.
 
 
 
 
 
 
 
===Philosophy or approach to client security===
Please provide relevant considerations a client should have—and primary risks a client should mitigate—when securing information in your organization's cloud infrastructure. Does a clear "shared responsibility" model exist, and if so, how is it effectively communicated to potential and existing clients? If you have documented data security policies, please describe how new and existing clients may access them. Additionally, explain how those policies better ensure client data integrity.
 
 
 
 
 
 
 
===Technology and security===
Please describe the organizational and client-based availability and use of cloud security technologies such as:
 
* device management tools,
* firewalls and related performance monitoring tools,
* identity and access management mechanisms,
* intrusion prevention and detection systems,
* integration tools, and
* any other security-related analysis and prevention tools (e.g., rules engines).
 
 
 
 
 
 
 
===Data storage===
Please describe how sensitive and regulated data is able to be stored on a machine dedicated to complying with the laws and regulations relevant to the data owner. How is that type of data segregated from other clients' data, and will lapses in security of other clients' data affect our own?
 
 
 
 
 
 
 
===Data transmission, sharing, and transfer===
Please describe how your cloud services allow for secure transmission and sharing of data across network boundaries, including across other cloud provider environments. Additionally, provide details about any dependencies or technical challenges associated with seamlessly transferring an application, system, or database 1. from a client or third-party cloud environment to your cloud environment and 2. from your cloud environment to another cloud environment. What solutions do you provide towards this seamless transfer?
 
 
 
 
 
 
 
===Logging===
Please describe your approach to collecting, analyzing, correlating, and acting upon cloud log and event data, particularly in relation to client data and services. Describe how thorough those logs are and provide background on your organizational policy in regards to retaining and making available collected log and event data to clients on-demand. Finally, explain how long those logs and associated data are accessible after creation, as well as whether or not any of that information is kept in secure retention.
 
 
 
 
 
 
 
===Monitoring===
If your organization has its own cloud infrastructure, please describe how your organization monitors that infrastructure for security purposes. What self-monitoring services and tools are made available to clients, if any?
 
 
 
 
 
 
 
===Incident response and reporting===
Should a security threat be identified by your monitoring activities, please explain how your incident response team cooperates with the monitoring team for efficiency. Additionally, describe how your incident response team works together with clients during a security incident. Provide details on how your organization handles reporting of intrusions, hacks, or other types of breaches to effected clients. Also explain how teams associated with incident response and threat remediation use their capabilities to provide value to the client.
 
 
 
 
 
 
 
===Hybrid and multicloud security===
Please explain how your cloud services and their associated technology enable and improve secure integrations and activities in hybrid and multicloud scenarios.
 
 
 
 
 
 
 
==Threat intelligence==
 
===Research team===
If your organization has a research team dedicated to discovering cloud threats and vulnerabilities, please describe the team, how it's integrated with the organization's operations, and what services that team supports beyond research. If the research team has a mission, please state that mission.
 
 
 
 
 
 
 
===Threat detection===
Please describe the information sources the research team (or, if no research team, the overall security team) uses to gather threat intelligence. Provide specifics about any anomaly detection, behavioral analysis, malicious host detection, signature analysis, and volume analysis detection methods.
 
 
 
 
 
 
 
===Use of and access to threat intelligence===
Please describe how gathered threat intelligence is analyzed and validated. Additionally, describe how that analyzed and validated threat intelligence is used in the management and monitoring of your cloud services and infrastructure. Also describe what level of visibility and access a client has into this intelligence, as well as the research team itself. If any bug bounty programs or the like exist, please explain them here as well.
 
 
 
 
 
 
 
===Examples of action on threat intelligence===
Please provide examples of how threat intelligence generated by your organization's research team (or someone else) has been effectively used to protect clients. Also provide examples of organization white papers, use cases, threat reports, or internal write-ups (if available) regarding threat intelligence and its effective use in the organizational cloud infrastructure.
 
 
 
 
 
 
 
==Vulnerability testing==
 
===Vulnerability testing basics===
Please describe the extent of vulnerability testing your organization may conduct on its cloud infrastructure, including the origin of any testing protocols.
 
 
 
 
 
 
 
===Vulnerability identification and confirmation===
Please describe how vulnerabilities are identified and confirmed within your cloud infrastructure. If your organization has a process for identifying and reporting false positives, provide details. Is vulnerability data incorporated into overall cloud security monitoring processes, and if so, in what ways?
 
 
 
 
 
 
 
===Client-based vulnerability testing===
If a client or a representative third party of a client is allowed to perform vulnerability testing on your organization's cloud infrastructure, provide details. If your cloud services support web application scanning and testing for database vulnerabilities, please provide important details.
 
 
 
 
 
 
 
==Additional cloud security==
 
===Endpoint protection===
Please describe any managed service, software solution, hardware solution, or other mechanism your organization provides or makes available to clients in regard to helping clients maintain endpoint security in the cloud. If such a service or tool is offered, describe what types of alerts are given in association with it and what, if any, remediation recommendations are provided. Be sure to address whether or not threat intelligence is integrated into the service or tool and what operating system (OS) endpoints are covered.
 
 
 
 
 
 
 
===Malware protection===
Please describe any managed service, software solution, or other mechanism your organization provides or makes available to clients in regard to helping clients with malware protection. If such a service or tool is offered, describe whether or not it uses sandboxing technology, and if so, what type. Be sure to address whether or not threat intelligence is integrated into the service or tool and what zero-day threat capabilities it may have.
 
 
 
 
 
 
 
===Other ancillary services===
Please describe if your organization is capable of assisting clients with security audits and analyses of their own instances. If your organization also provides consulting, technical testing, penetration testing, forensic investigation, and threat remediation services, please describe them, as well as any associated service tiers.
 
 
 
 
 
 
 
==Account management and support==
 
===Account management basics===
Please describe how accounts are established on your organization's service and what level of visibility clients and their authorized users will have into the cloud services administered, including consumption metrics, security metrics, and various account logs.
 
 
 
 
 
 
 
===Support basics===
Please describe your organizational approach to client support and how that support is structured, including the processes and mechanisms for handling client inquiries and issues. Describe the communication mechanisms primarily and secondarily used for support, including mailed documentation, phone calls, electronic communication, and face-to-face communication. Explain how the escalation process for inquiries and reported issues should be handled.
 
 
 
 
 
 
 
===Help desk and support ticketing===
Please indicate what help desk or ticketing functionality is available for clients having cloud service issues. Describe how clients should go about using such tools to initiate the support process. Do clients receive comprehensive downtime support in the case of service downtime?
 
 
 
 
 
 
 
===Availability, provisioning, and responsiveness===
Please indicate the availability of your organization's support services, including hours offered. Also indicate who is provisioning the service, whether it's in-house or a third party, and from where the service is provisioned. Note whether or not support services change hands at any point. Finally, describe how support quality is guaranteed at all times, including any guarantees on responsiveness.
 
 
 
 
 
 
 
===Client satisfaction===
Please describe how your organization measures and reports (including frequency) client satisfaction with support, account, and overall services. Describe how deficiencies in client satisfaction are addressed and resolved within the organization.
 
 
 
 
 
 
 
===Ancillary services===
Please indicate whether or not your organization provides value-added support services, and if so what type. Can a dedicated account manager with sufficient technical knowledge be provided, and if so, at what cost?
 
 
 
 
 
 
 
==Service level agreements (SLAs) and contracts==
 
===SLA basics===
Please describe the details of your SLAs for the various services you provide, including any negotiable aspects of the SLAs. Provide examples. Any relevant measurements and ranges for work performed by you (e.g., service speed, response times, and accuracy) should also be clearly defined and stated. Explain what the cost implications related to any differing service levels are. Finally, explain whether or not your organization provides clients with a 30-day proof of concept test of the services to ensure your organization can prove its marketing and operational claims.
 
 
 
 
 
 
 
===SLAs for SaaS===
In the case of SaaS-related cloud agreements (if applicable) with your organization, please explain how software customization, upgrades, testing, and versioning are addressed in such agreements.
 
 
 
 
 
 
 
===SLA failure===
Please explain how your organization monitors and measures its compliance with an SLA. Describe what options are available to clients upon your organization failing to meet an agreed-upon SLA.
 
 
 
 
 
 
 
===Business associate agreements===
State whether or not your organization will sign a business associate agreement or addendum for purposes of ensuring your organization appropriately safeguards protected health information, as dictated by the Health Insurance Portability and Accountability Act (HIPAA).
 
 
 
 
 
 
 
===Contract termination===
Please describe your policy on archiving, deleting, and helping transition client data from any of your systems upon contract termination, including particulars about data formats, deletion methodologies, and transfer methods. Any explanation should include the respective termination rights of both the organization and the client.
 
 
 
 
 
 
 
===Organization termination or catastrophic loss===
Please describe what would happen to a client's data in the event of your organization going out of business or suffering a catastrophic loss.
 
 
 
 
 
 
 
==Service implementation==
 
===Implementation basics===
Please describe your approach to implementing your cloud computing or cloud-based services for clients. You should address:
 
* the standard timeframe for implementation and onboarding (overall average or last 10 customers);
* whether or not a dedicated point of contact will be maintained throughout implementation, to the end of the contract;
* what resources clients will require to support the implementation and throughout the contract's duration;
* what client processes and procedures your organization has found to be vital to optimal cloud implementation and operation;
* what device and database integrations are supported in an implementation;
* whether or not unsupported devices and databases can be added for support;
* how the impact or disruption of client resources is minimized during implementation; and
* what your normalization and fine-tuning procedures are.
 
 
 
 
 
 
 
===Completion and handoff===
Please describe what steps are taken to ensure the implementation is complete, as well as how the service is handed off to the client afterwards. If your organization provides training and documentation at handoff, describe how this training and documentation is administered, and at what additional cost, if any.
 
 
 
 
 
 
 
===Multi-site implementations===
Please describe the process used when implementing a service to a client with many geographically dispersed facilities.
 
 
 
 
 
 
 
==Pricing==
 
===Pricing basics===
Please describe how your company's pricing and payment models meet industry standard practices (e.g., payment per actual services consumed, per GB of storage, per server, per annual subscription, etc.). Provide pricing estimates and examples based upon the various services provided using a current published catalog, standard market pricing, and/or web enabled price calculators. Explain how any metered services are clearly reported and billed. Ensure all costs are accurately reflected, including any:
 
* underlying "implied" costs,
* initial "stand up" costs,
* ongoing maintenance or subscription costs,
* renewal-related price increases
* data download costs, and
* termination costs.


* '''stain panel and unstained/control slide support''': A positive control slide is typically used to qualitatively assess how well a non-hematoxylin-eosin (non-H&E) or "special" stain performs against a gold standard like H&E, and the positive control is usually included with manufactured unstained slides (e.g., see Newcomer Supply's [https://www.newcomersupply.com/documents/product-flyers/Control%20Slide%20Brochure.pdf control slide catalog]). These slides may be used in histopathology (gauging the manifestation of disease in a tissue) and immunopathology (gauging immune response through visualization of an antibody-antigen interaction in a tissue). In particular, immunopathology and its associated immunohistochemistry may turn to special stain panels, which utilize multiple immunochemical stains to visualize the presence of more than one biomarker expression at the same time.<ref name="ShieldImmuno96">{{cite journal |title=Immunocytochemical staining of cytologic specimens. How helpful is it? |journal=American Journal of Clinical Pathology |author=Shield, P.W.; Perkins, G.; Wright, R.G. |volume=105 |issue=2 |pages=157–62 |year=1996 |doi=10.1093/ajcp/105.2.157 |pmid=8607438}}</ref><ref name="MartinEval14">{{cite journal |title=Evaluation of intestinal biopsies for pediatric enteropathy: A proposed immunohistochemical panel approach |journal=American Journal of Surgical Pathology |author=Martin, B.A.; Kerner, J.A.; Hazard, F.K. et al. |volume=38 |issue=10 |pages=1387–95 |year=2014 |doi=10.1097/PAS.0000000000000314 |pmid=25188866}}</ref><ref name="TorbensonImmuno19">{{cite web |url=https://abdominalkey.com/immunohistochemistry-and-special-stains-in-liver-pathology/ |title=Chapter 4. Immunohistochemistry and Special Stains in Liver Pathology |author=Torbenson, M.S. |work=Abdominalkey |date=24 November 2019 |accessdate=23 September 2020}}</ref> Vendors like NovoPath and Integrated Business Solutions Group explicitly state their solution supports the management of these types of slides and stain panels.<ref name="NPSoftwarePDF" /><ref name="IBSGLabLion">{{cite web |url=https://www.lablion.com/lablion-lis-laboratory-information-system |title=LABLION Software Suite |publisher=Integrated Business Solutions Group, LLC |accessdate=23 September 2020}}</ref>


* '''grossing support''': In medical terms, the adjective "gross" means "visible without the aid of a microscope."<ref name="MWGross">{{cite web |url=https://www.merriam-webster.com/dictionary/gross |title=Gross |work=Merriam-Webster.com Dictionary |publisher=Merriam-Webster |accessdate=23 September 2020}}</ref> By extension, gross examination (i.e., grossing) involves a macroscopic visual assessment of a biospecimen before preparation for microscopy, in order to gleen diagnostic information. Grossing remains a valuable skill used in modern pathology.<ref name="RutgushreeGrossing18">{{cite journal |title=Grossing of tissue specimens in oral pathology - Elemental guidelines |journal=International Journal of Oral Health Sciences |author=Ruthushree, T.; Harsha, M.; Amberkar, V.S. |volume=8 |issue=2 |pages=63–7 |year=2018 |doi=10.4103/ijohs.ijohs_32_18}}</ref><ref name="SchubertTheArt19">{{cite web |url=https://thepathologist.com/inside-the-lab/the-art-of-grossing |title=The Art of Grossing: Gross examination underpins all diagnoses based on tissue samples – but is this vital skill given the credit it deserves? |author=Schubert, M.; Nashm C; McCoy, J. |work=The Pathologist |date=26 November 2019 |accessdate=23 September 2020}}</ref> Some PIMS provide a grossing menu for pathologists to scan in and include commentary about a gross examination of a specimen.<ref name="LLAnatom" />


* '''high-risk patient follow-up''': A 2015 study published in ''Annals of Family Medicine'' showed evidence that "patients with high clinical complexity and high risk of readmission" benefited from early outpatient follow-up.<ref name="JosztHigh15">{{cite web |url=https://www.ajmc.com/view/high-risk-patients-benefit-significantly-from-early-follow-up-post-hospital-discharge |title=High-Risk Patients Benefit Significantly From Early Follow-up Post Hospital Discharge |author=Joszt, L. |work=The American Journal of Managed Care |date=20 April 2015 |accessdate=23 September 2020}}</ref><ref name="JacksonTimeli15">{{cite journal |title=Timeliness of Outpatient Follow-up: An Evidence-Based Approach for Planning After Hospital Discharge |journal=Annals of Family Medicine |author=Jackson, C.; Shahsahebi, M.; Wedlake, T. et al. |volume=13 |issue=2 |pages=115–22 |year=2015 |doi=10.1370/afm.1753}}</ref> The authors concluded : "Follow-up within seven days was associated with meaningful reductions in readmission risk for patients with multiple chronic conditions and a greater than 20% baseline risk of readmission, a group that represented 24% of discharged patients." Presumably some health care systems are synthesizing that information into their patient workflows, likely through some sort of scheduled event and alert in their primary informatics system, e.g., an [[electronic health record]] (EHR) system.<ref name="FutrellHealth18">{{cite web |url=https://www.mlo-online.com/information-technology/lis/article/13009479/health-information-technology-can-support-population-health-management |title=Health information technology can support population health management |author=Futrell, K. |work=Medical Laboratory Observer |date=18 April 2018 |accessdate=23 September 2020}}</ref> Though not common, at least one PIMS vendor—LigoLab, LLC—indicates their solution helps address high-risk patient follow-up, though it's not clear how.<ref name="LLAnatom" />


* '''research animal support''': Non-clinical pathology and toxicology laboratories assisting with research and evaluation studies may be handling non-human specimens or even live research animals. Additional data about these animals, animal groups, and animal tissues may need to be carefully documented as part of a study. As such, some solutions such as Instem's Provantis preclinical pathology solution are designed to record specific animal and group identifiers, animal cross-reference information, organ weight ratios, palpable mass diagnoses, and other attributes for reporting.<ref name="InstemProvantis">{{cite web |url=https://www.instem.com/solutions/provantis/index.php#2 |title=Provantis: Integrated preclinical software |publisher=Instem LSS Limited |accessdate=23 September 2020}}</ref>





Latest revision as of 13:27, 6 September 2021

Broad feature set of a pathology information management solution

A pathology information management solution (PIMS) ...


  • automated reflex testing: Some PIMS vendors include pre-loaded, customizable lists of reflex tests associated with certain pathology procedures and their associated diagnoses. Optimally, these reflex texts are automatically suggested at specimen reception, based on specimen and/or pathology test type.[1][2] Examples of pathology-driven reflex testing in use today include testing for additional biomarkers for non-small-cell lung carcinoma (NSCLC) adenocarcinoma[3], HPV testing in addition to cervical cytology examination[4][5] (discussed further in "adjunctive testing"), and additional automatic testing based off routine coagulation assays at hemostasis labs.[6]
  • adjunctive testing: Adjunctive testing is testing "that provides information that adds to or helps interpret the results of other tests, and provides information useful for risk assessment."[7] A common adjunctive test performed in cytopathology is HPV testing.[4][5] The FDA described this as such in 2003, specifically in regards to expanding the use of the Digene HC2 assay as an adjunct to cytology[4]:

In women 30 years and older, the HC2 High-Risk HPV DNA test can be used with Pap to adjunctively screen to assess the presence or absence of high-risk HPV types. This information, together with the physician’s assessment of cytology history, other risk factors, and professional guidelines, may be used to guide patient management.

Some PIMS vendors allow users to manually add an adjunctive test to a primary pathology test, or in some cases this may be enabled as part of an automated reflex testing process.[8] However, ensure that any such solution is capable of feeding any adjunctive test results into the final report (see the subsection on this topic).
  • demand management: Similar to test optimization or clinical decision support, demand management mechanisms help laboratories reduce the amount of unnecessary and duplicate testing they perform. The idea of using demand management to reduce unnecessary pathology testing has been around since at least the beginning of the twenty-first century, if not well before, in the form of decision support systems and order request menus of informatics systems.[9] Lang described what the process of demand management would look like in a system like a laboratory information management system (LIMS) in 2013[10]:

When implementing a demand management tool it is important that the system used to manage a laboratory workload can correctly identify the patient and match requests with the patient’s medical record. Ideally there should be one unique identifier used (e.g., NHS number in the UK), which will allow the LIMS to interrogate the patient’s previous pathology result to allow identification of duplicate or inappropriate requests. If a subsequent request is blocked, then it is also important that there is real-time notification of a potential redundant test so that the requestor can make an informed choice on the clinical need of the test and if it is required to override the rule. It is important that there is a facility whereby the laboratory or requestor can record the reason for blocking a request or overriding the rule.

Today, some PIMS are designed to allow configurable rules and parameters to check for duplicate and unnecessary tests at various levels (e.g., by test ID or catalog type, activity type, or some other order level).[11][12]
  • consent management: In clinical medicine, patients typically must sign a form indicating informed consent to medical treatment.[13] Biobanking facilities, which store biospecimens, also must collect consent forms regarding how a patient's biospecimens may be used.[14] In all cases, these consent documents drive how and when certain actions take place. Though not common, some LIMS like LabVantage Pathology by Software Point[15] provide consent management mechanisms within their PIMS, giving pathologists the ability to quickly verify consent details electronically. In biobanking solutions, this consent management process may be more rigorous to ensure biospecimen donors' preferences and regulatory requirements are being carefully followed. For example, the system may need to be able to prevent further use of a biospecimen and trigger sample and data deletion protocols when a donor withraws their consent to use.[16]
  • case management and review: Most PIMS provide a means for managing pathology cases, recorded instances of disease and its attendant circumstances.[17] This includes the management of case history, a collection of data concerning an individual, their family, their environment, their medical history, and other other information valuable for analyzing, diagnosing, reviewing, or otherwise instructing others on the case.[18] Having an information system to better manage data entry, data analysis, case tracking, and case storage may aid in secondary and internal case reviews before final report, which have been shown to improve diagnostic accuracies and overall experiential knowledge of pathologists.[19] Aspects of case manamagement and review that a PIMS may handle include automatic case creation, automatic and priority case assignment, and automatic case tracking, as well as limit case acces based on user permissions, and send alerts for clinical history follow-ups and other case statuses.[20][21][22] Note that a handful of vendors such as Leica Biosystems provide stand-alone case management solutions that can be integrated with instruments and other LIS systems.[22]
  • workflow management: The tools for workflow management have become increasingly common in PIMS and other laboratory informatics applications over the years, with the idea of using automation to improves efficiencies and accuracies in the lab. However, workflows and protocols can differ—sometimes significantly—from one pathology lab to another. Being able to configure workflow pathways in the PIMS to be compliant with required testing protocols is vital. This is especially important with the gradual transition to more digital pathology methods, where digitally sharing cases and automatically scanned slide images has great value.[23] As such, vendors such as Orchard Software and XIFIN provide solutions with configurable workflows to help labs translate their workflows into the system.[24][25]
  • speech recognition and transcription management: Like other medical fields, pathologists may utilize dictation and transcription services within their workflow. This has traditionally involved the pathologist speaking while a transcriptionist manually records the words to paper, or the pathologist scribbling notes in shorthand, with the transcriptionist "translating" the notes to usable clinical documentation. This could include anything from specimen descriptions and diagnoses to pathology obsevations and procedure notes. PIMS vendors have over the years added more automated methods to such tasks in their solutions, however, such as speech recognition modules and transcription management tools that, for example, automatically assign recordings to a transcriber's pending work list.[1][15][26][21]
It's important to note, however, though PIMS vendors may market the speech recognition component of their solution at being 99 percent effective, past studies have shown 88.9 to 96 percent accuracy, though with tiny annual gains as the technology matures.[27][28] If speech recognition is being used in lieu of a hired transcriptionist, it's especially vital to add manual editing and review before reporting.[28][29]
  • storage and tissue bank management: Biorepositories and pathology laboratories go hand-in-hand. A significant example can be found with the relationship medical school biorepositories have with their pathology labs and departments, as with, for example, Duke University[30], University of Illinois Chicago[31], and the Icahn School of Medicine at Mount Sinai.[32] However, even small pathology laboratories must also responsibly store and track their specimens, blocks, and slides, as well as the storage variables affecting them. Any reputable laboratory informatics solution will be able to track the location of such items through barcode or RFID support, as well as allowing for the creation of named storage locations in the system. However, some informatics solutions like AgileBio's LabCollector go a step further, providing data logging modules that are capable of connecting to data logger hardware and other sensors that capture environmental storage information such as temperature, humidity, light level, carbon dioxide level, and pressure. When a variable is out of range, an alert can be sent and logged.[33] And full-fledged biorepository management LIMS may have all the bells and whistles, including randomized biospecimen location auditing.[34]
  • task management: Task management is a typical feature of a laboratory informatics solution, giving laboratorians the ability to assign tasks to individuals or groups of individuals, including analyses, results review, and more. In pathology labs, additional task and even management may include, for example, case assignment, slide or block assignment, grossing, staining, or some other pathology task. Additionally, some may incorporate this task management and tracking into a dashboard, to facility timely access to short-term status individual cases and specimens, and long-term aggregate data about cases, workflow, and workloads.[35]
  • billing management with code support: Instead of turning to a separate billing solution, pathology labs can often turn to PIMS for billing management. Vendors of LIS and LIMS have recognized not only the value of adding billing management to their solutions but also the many benefits that come with tying in diagnosis and billing code support. For example, a pathologist scanning a specimen into the system can not only have a case automatically generated but also auto-generate diagnosis codes based on the specimen or slide's code. Additionally, as has been witnessed during the COVID-19 pandemic, billing rules may change rapidly during extraordinary events, requiring rapid used-defined billing rule changes.[36] As such, support for CPT, ICD-10, SNOMED CT, and other types of autocoding are somewhat common in today's PIMS.[1][20][21][26]
  • reflex and adjunctive test reporting: Ensure that a PIMS is capable of feeding any adjunctive test results into the final report, along with the results from the primary tests. Using adjunctive HPV test results as an example, the report should optimally include details such as assay name, manufacturer, the HPV types it covers, results, and any applicable educational notes and suggestions.[5] Be careful with simple color-coding of results for interpretation, as they can be easily misinterpreted, including by the colorblind. A combination of symbol with color will help limit such misinterpretation.[3]
  • structured data entry: The concept of structured data entry (SDE) is relatively simple, but it may still get taken for granted. At its core, SDE is all about ensuring that entered data is based on a set of predefined conditions or rules, usually implemented through standardized forms with pre-determined drop-down and auto-populated fields.[37] This typically confers numerous advantages, including easier data entry, easier and more standardized reporting, decrease costs, improve translational research, and ensure better compatibility and integration across different information systems.[37][38] As such, some PIMS vendors like NovoPath and Orchard Software describe their solutions as having SDE elements such as enabling intelligent auto-loading of diagnosis and billing codes during case loading, allowing input fields to be required, and synoptic reporting support.[39][24]
  • synoptic reporting: Synoptic reporting involves a structured, pre-formatted "checklist" of clinically and morphologically relevant data elements that help make pathology reporting more efficient, uniform, and relevant to internal and external stakeholders. Another way to put this is that synoptic reporting is SDE applied to the pathology report, often based upon specific reporting protocols by professional or standards organizations like the College of American Pathologists (CAP).[20][39] Support for synoptic reporting methods is typical within PIMS solutions, including support for configurable templates that can be adapted to changing and custom reporting protocols.
  • correlative and consultive reporting: In the late 1930s, the concept of correlating pathology results with clinical observations (and pathology) was beginning to be addressed in student textbooks.[40] Today, the concept remains integral in medical practice and toxicologic study reporting.[41][42][43] On the clinical side, a pathologist may include the phrase "clinical correlation is recommended" and additional comments. And in some cases, a third-party pathology consultation, with their own respective comments, is involved with specimen analysis.[44] These correlative and consultive comments or reports play an important part in the overall final pathology report and should not be omitted, particularly if differing opinions are involved. Vendors such as Orchard Software, LigoLab, and Aspyra tout their solutions' ability to tie together multiple reports and comments across pathology disciplines and consultants into one concise report.[24][20][26]
  • CAP Cancer Reporting Protocol support: Previously mentioned was CAP and its reporting protocols. In particular, CAP has its Cancer Reporting Protocols, which the CAP describe as providing "guidelines for collecting the essential data elements for complete reporting of malignant tumors and optimal patient care."[45] In conjunction with its electronic Cancer Checklists (eCCs)[46], pathologists are able to integrate CAP cancer reporting protocols of tumors, resections, and select biopsies into their PIMS' workflow and ensure proper reporting outcomes. Some PIMS vendors (e.g., Orchard Software, LigoLab[24][20]) explicitly indicate their solution integrates CAP's eCC templates and reporting protocols into their solution.
  • annotated organ mapping: In the world of PIMS, organ mapping refers to the concept of placing location-specific diagnostic information from specimen analyses into an anatomical diagram, typically during reporting, to more clearly communicate the results of those analyses. PIMS vendor WebPathLab, Inc. demonstrates this concept well with its Auto Organ Map Module, which not only shows an organ map in the rport but also simplifies data entry for the pathologist using SDE.[47][48] They use the prostate as an example, and explain that "selecting the predetermined number of quadrants in the prostate [diagram], the system autopopulates the specimen description to each corresponding quadrant, and autofills the text for the Gross Description field, leaving only the dimension of each core to be entered by the grosser." NovoPath and Psyche Systems Corporation are additional examples of vendors incorporating organ mapping into their PIMS.[2][39]
  • stain panel and unstained/control slide support: A positive control slide is typically used to qualitatively assess how well a non-hematoxylin-eosin (non-H&E) or "special" stain performs against a gold standard like H&E, and the positive control is usually included with manufactured unstained slides (e.g., see Newcomer Supply's control slide catalog). These slides may be used in histopathology (gauging the manifestation of disease in a tissue) and immunopathology (gauging immune response through visualization of an antibody-antigen interaction in a tissue). In particular, immunopathology and its associated immunohistochemistry may turn to special stain panels, which utilize multiple immunochemical stains to visualize the presence of more than one biomarker expression at the same time.[49][50][51] Vendors like NovoPath and Integrated Business Solutions Group explicitly state their solution supports the management of these types of slides and stain panels.[39][52]
  • grossing support: In medical terms, the adjective "gross" means "visible without the aid of a microscope."[53] By extension, gross examination (i.e., grossing) involves a macroscopic visual assessment of a biospecimen before preparation for microscopy, in order to gleen diagnostic information. Grossing remains a valuable skill used in modern pathology.[54][55] Some PIMS provide a grossing menu for pathologists to scan in and include commentary about a gross examination of a specimen.[20]
  • high-risk patient follow-up: A 2015 study published in Annals of Family Medicine showed evidence that "patients with high clinical complexity and high risk of readmission" benefited from early outpatient follow-up.[56][57] The authors concluded : "Follow-up within seven days was associated with meaningful reductions in readmission risk for patients with multiple chronic conditions and a greater than 20% baseline risk of readmission, a group that represented 24% of discharged patients." Presumably some health care systems are synthesizing that information into their patient workflows, likely through some sort of scheduled event and alert in their primary informatics system, e.g., an electronic health record (EHR) system.[58] Though not common, at least one PIMS vendor—LigoLab, LLC—indicates their solution helps address high-risk patient follow-up, though it's not clear how.[20]
  • research animal support: Non-clinical pathology and toxicology laboratories assisting with research and evaluation studies may be handling non-human specimens or even live research animals. Additional data about these animals, animal groups, and animal tissues may need to be carefully documented as part of a study. As such, some solutions such as Instem's Provantis preclinical pathology solution are designed to record specific animal and group identifiers, animal cross-reference information, organ weight ratios, palpable mass diagnoses, and other attributes for reporting.[59]


References

  1. 1.0 1.1 1.2 "NovoPath - Software Advancing Patient Diagnostics" (PDF). NovoPath, Inc. 2013. https://www.novopath.com/content/pdf/novopathbrochure.pdf. Retrieved 05 September 2020. 
  2. 2.0 2.1 "WindoPath Ē.ssential". Psychē Systems Corporation. https://psychesystems.com/enterprise-laboratory-information-software/windopath/. Retrieved 05 September 2020. 
  3. 3.0 3.1 Sundin, T. (2019). "Pathology-Driven Reflex Testing of Biomarkers". Medical Lab Management 8 (11): 6. https://www.medlabmag.com/article/1619. 
  4. 4.0 4.1 4.2 U.S. Food and Drug Administration (8 March 2019). "New Approaches in the Evaluation for High-Risk Human Papillomavirus Nucleic Acid Detection Devices". U.S. Food and Drug Administration. https://www.fda.gov/media/122799/download. Retrieved 05 September 2020. 
  5. 5.0 5.1 5.2 Stoler, M.H.; Raab, S.S.; Wilbur, D.C. (2015). "Chapter 9: Adjunctive Testing". In Nayar, R.; Wilbur, D.. The Bethesda System for Reporting Cervical Cytology. Springer. pp. 287–94. doi:10.1007/978-3-319-11074-5_9. ISBN 9783319110745. 
  6. Mohammed, S.; Priebbenow, V.U.; Pasalic, L. et al. (2019). "Development and implementation of an expert rule set for automated reflex testing and validation of routine coagulation tests in a large pathology network". International Journal of Laboratory Hematology 41 (5): 642–49. doi:10.1111/ijlh.13078. PMID 31271498. 
  7. "adjunct test". Segen's Medical Dictionary. 2011. https://medical-dictionary.thefreedictionary.com/adjunct+test. Retrieved 05 September 2020. 
  8. "TD HistoCyto Livextens". Technidata SAS. https://www.technidata-web.com/solutions-services/disciplines/anatomic-pathology. Retrieved 05 September 2020. 
  9. Rao, G.G.; Crook, M.; Tillyer, M.L. (2003). "Pathology tests: is the time for demand management ripe at last?". Journal of Clinical Pathology 56 (4): 243–48. doi:10.1136/jcp.56.4.243. PMC PMC1769923. PMID 12663633. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC1769923. 
  10. Lang, T. (2013). "Laboratory demand management of repetitive testing – time for harmonisation and an evidenced based approach". Clinical Chemistry and Laboratory Medicine 51 (6): 1139–40. doi:10.1515/cclm-2013-0063. PMID 23420284. 
  11. Morris, T.F.; Ellison, T.L.; Mutabbagani, M. et al. (2018). "Demand management and optimization of clinical laboratory services in a tertiary referral center in Saudi Arabia". Annals of Saudi Medicine 38 (4): 299–304. doi:10.5144/0256-4947.2018.299. PMC PMC6086671. PMID 30078029. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6086671. 
  12. "DXC Laboratory Information Management (LIMS)". DXC Technology Services, LLC. https://www.dxc.technology/healthcare/offerings/139499/139776-dxc_laboratory_information_management_lims. Retrieved 05 September 2020. 
  13. "Informed Consent". Code of Medical Ethics. American Medical Association. https://www.ama-assn.org/delivering-care/ethics/informed-consent. Retrieved 22 September 2020. 
  14. Avery, D. (16 July 2018). "Biobanking Consent: Informing Human Subjects of the Possibilities". Biobanking.com. https://www.biobanking.com/biobanking-consent-informing-human-subjects-of-the-possibilities/. Retrieved 22 September 2020. 
  15. 15.0 15.1 "LabVantage Pathology". Software Point Oy. https://softwarepoint.com/solutions/product/labvantage-pathology. Retrieved 22 September 2020. 
  16. SANBI; Bika Lab Systems (20 November 2015). "NCB-H3A Cape Town Biobank Management System - Functional Requirements Overview & Phase I Objectives" (PDF). Bika Lab Systems. https://www.bikalims.org/downloads/bika-open-source-biobank-management-system/at_download/file. Retrieved 22 September 2020. 
  17. "case". Farlex Partner Medical Dictionary. 2012. https://medical-dictionary.thefreedictionary.com/case. Retrieved 25 September 2020. 
  18. "case". Miller-Keane Encyclopedia and Dictionary of Medicine, Nursing, and Allied Health, Seventh Edition. 2003. https://medical-dictionary.thefreedictionary.com/case. Retrieved 25 September 2020. 
  19. Huck, A.; Nosé, V. (2015). "Chapter 7: Knowledge, Training, and Experience". In Nakhleh, R.E.. Error Reduction and Prevention in Surgical Pathology. Springer. pp. 103–114. ISBN 9781493923397. https://books.google.com/books?id=HXAKBwAAQBAJ&pg=PA103. 
  20. 20.0 20.1 20.2 20.3 20.4 20.5 20.6 "Anatomic Pathology Solutions". LigoLab, LLC. https://www.ligolab.com/solutions/anatomic-pathology-solution. Retrieved 23 September 2020. 
  21. 21.0 21.1 21.2 "PathX Laboratory Information System" (PDF). Physicians Independent Management Services. http://pathxlis.com/downloads/PDFs/PathX%20-%20Capabilities%20Brochure.pdf. Retrieved 25 September 2020. 
  22. 22.0 22.1 "Aperio Path DX - Case Management Software". Leica Biosystems Nussloch GmbH. https://www.leicabiosystems.com/digital-pathology/manage/aperio-path-dx/. Retrieved 25 September 2020. 
  23. "Is Your Lab Ready for an AI Digital Pathology Workflow?". XIFIN, Inc. 3 January 2020. https://www.xifin.com/resources/blog/201912/your-lab-ready-ai-digital-pathology-workflow. Retrieved 25 September 2020. 
  24. 24.0 24.1 24.2 24.3 "Orchard Pathology". Orchard Software Corporation. https://www.orchardsoft.com/orchard-pathology.html. Retrieved 22 September 2020. 
  25. "Laboratory Information System". XIFIN, Inc. https://www.xifin.com/products/laboratory-information-system. Retrieved 25 September 2020. 
  26. 26.0 26.1 26.2 "Anatomic Pathology". Aspyra, LLC. http://aspyra.com/anatomic-pathology/. Retrieved 23 September 2020. 
  27. Hodgson, T.; Coiera, E. (2016). "Risks and benefits of speech recognition for clinical documentation: A systematic review". JAMIA 23 (e1): e169–79. doi:10.1093/jamia/ocv152. PMC PMC4954615. PMID 26578226. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4954615. 
  28. 28.0 28.1 Zhou, L.; Blackley, S.V.; Kowalski, L. et al. (2018). "Analysis of Errors in Dictated Clinical Documents Assisted by Speech Recognition Software and Professional Transcriptionists". JAMA Network Open 1 (3): e180530. doi:10.1001/jamanetworkopen.2018.0530. PMC PMC6203313. PMID 30370424. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6203313. 
  29. Matthews, K. (20 December 2019). "Why Medical Dictation Is Still Better Than Voice Recognition ... For Now". Health IT Outcomes. https://www.healthitoutcomes.com/doc/why-medical-dictation-is-still-better-than-voice-recognition-for-now-0001. Retrieved 25 September 2020. 
  30. "Biorepository & Precision Pathology Center". Duke University School of Medicine. https://pathology.duke.edu/core-facilities-services/biorepository-precision-pathology-center. Retrieved 22 September 2020. 
  31. "UI Health Biorepository". University of Illinois Chicago. https://rrc.uic.edu/cores/rsd/biorepository/. Retrieved 22 September 2020. 
  32. "Biorepository and Pathology". Icahn School of Medicine at Mount Sinai. https://icahn.mssm.edu/research/portal/resources/deans-cores/biorepository-and-pathology. Retrieved 22 September 2020. 
  33. "Data Logger". AgileBio. https://www.labcollector.com/labcollector-lims/add-ons/data-logger/. Retrieved 22 September 2020. 
  34. "Biobank Management LIMS". Autoscribe Informatics, Inc. 22 September 2020. https://www.autoscribeinformatics.com/industries/biobank-management-systems. 
  35. Halwani, F.; Li, W.C.; Banerjee, D. et al. (2016). "A real-time dashboard for managing pathology processes". Journal of Pathology Informatics 7: 24. doi:10.4103/2153-3539.181768. PMC PMC4872478. PMID 27217974. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4872478. 
  36. Ferrante, T.B.; Goodman, R.B.; Wein, E.H. (3 April 2020). "COVID-19: CMS Issues Monumental Changes to Medicare Telehealth: What You Need to Know". Insights, a Foley & Lardner LLP Blog. https://www.foley.com/en/insights/publications/2020/04/covid19-cms-monumental-changes-medicare-telehealth. Retrieved 25 September 2020. 
  37. 37.0 37.1 Public Health Informatics Institute. "Analyzing Clinical Data and Workflows - 4. Understanding Clinical Data and Workflow" (DOCX). EHR Toolkit. https://www.phii.org/sites/default/files/resource/files/Understanding%20Clinical%20Data%20and%20Workflow%20Guide.docx. Retrieved 22 September 2020. 
  38. "Using structured data entry systems in the electronic medical record to collect clinical data for quality and research: Can we efficiently serve multiple needs for complex patients with spina bifida?". Journal of Pediatric Rehabilitative Medicine 11 (4): 303–09. 2018. doi:10.3233/PRM-170525. PMC PMC6491202. PMID 30507591. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6491202. 
  39. 39.0 39.1 39.2 39.3 "NovoPath - Software Advancing Patient Diagnostics" (PDF). NovoPath, Inc. 2013. https://www.novopath.com/content/pdf/novopathbrochure.pdf. Retrieved 22 September 2020. 
  40. "Textbook of Pathology. A Correlation of Clinical Observations and Pathological Findings". JAMA 114 (2): 184. 1940. doi:10.1001/jama.1940.02810020088032. 
  41. Smith, S.M.; Yearsley, M. (2016). "Constructing Comments in a Pathology Report: Advice for the Pathology Resident". Archives of Pathology & Laboratory Medicine 140 (10): 1023–24. doi:10.5858/arpa.2016-0220-ED. PMID 27684971. 
  42. Ramaiah, L.; Hinrichs, M.J.; Skuba, E.V. et al. (2017). "Interpreting and Integrating Clinical and Anatomic Pathology Results: Pulling It All Together". Toxicologic Pathology 45 (1): 223–37. doi:10.1177/0192623316677068. PMID 27879439. 
  43. Aulbach, A.; Vitsky, A.; Arndt, T. et al. (2019). "Overview and considerations for the reporting of clinical pathology interpretations in nonclinical toxicology studies". Veterinary Clinical Pathology 48 (3): 389–99. doi:10.1111/vcp.12772. PMID 31556157. 
  44. Kaplan, K. (19 June 2014). "What is a Pathology Consultation? When is it Used?". Corista Digital Pathology Blog. https://blog.corista.com/corista-digital-pathology-blog/bid/389513/What-is-a-Pathology-Consultation-When-is-it-Used. Retrieved 23 September 2020. 
  45. "Cancer Protocol Templates". College of American Pathologists. April 2020. https://www.cap.org/protocols-and-guidelines/cancer-reporting-tools/cancer-protocol-templates. Retrieved 23 September 2020. 
  46. "CAP eCC". College of American Pathologists. https://www.cap.org/laboratory-improvement/proficiency-testing/cap-ecc. Retrieved 23 September 2020. 
  47. WebPathLab, Inc (22 April 2019). "AutoProstateMap". YouTube. https://www.youtube.com/watch?v=NLr5_pLgYpg. Retrieved 23 September 2020. 
  48. "GU Auto Organ Map Module". WebPathLab, Inc. http://webpathlab.com/solutions/gu-auto-organ-map/. Retrieved 23 September 2020. 
  49. Shield, P.W.; Perkins, G.; Wright, R.G. (1996). "Immunocytochemical staining of cytologic specimens. How helpful is it?". American Journal of Clinical Pathology 105 (2): 157–62. doi:10.1093/ajcp/105.2.157. PMID 8607438. 
  50. Martin, B.A.; Kerner, J.A.; Hazard, F.K. et al. (2014). "Evaluation of intestinal biopsies for pediatric enteropathy: A proposed immunohistochemical panel approach". American Journal of Surgical Pathology 38 (10): 1387–95. doi:10.1097/PAS.0000000000000314. PMID 25188866. 
  51. Torbenson, M.S. (24 November 2019). "Chapter 4. Immunohistochemistry and Special Stains in Liver Pathology". Abdominalkey. https://abdominalkey.com/immunohistochemistry-and-special-stains-in-liver-pathology/. Retrieved 23 September 2020. 
  52. "LABLION Software Suite". Integrated Business Solutions Group, LLC. https://www.lablion.com/lablion-lis-laboratory-information-system. Retrieved 23 September 2020. 
  53. "Gross". Merriam-Webster.com Dictionary. Merriam-Webster. https://www.merriam-webster.com/dictionary/gross. Retrieved 23 September 2020. 
  54. Ruthushree, T.; Harsha, M.; Amberkar, V.S. (2018). "Grossing of tissue specimens in oral pathology - Elemental guidelines". International Journal of Oral Health Sciences 8 (2): 63–7. doi:10.4103/ijohs.ijohs_32_18. 
  55. Schubert, M.; Nashm C; McCoy, J. (26 November 2019). "The Art of Grossing: Gross examination underpins all diagnoses based on tissue samples – but is this vital skill given the credit it deserves?". The Pathologist. https://thepathologist.com/inside-the-lab/the-art-of-grossing. Retrieved 23 September 2020. 
  56. Joszt, L. (20 April 2015). "High-Risk Patients Benefit Significantly From Early Follow-up Post Hospital Discharge". The American Journal of Managed Care. https://www.ajmc.com/view/high-risk-patients-benefit-significantly-from-early-follow-up-post-hospital-discharge. Retrieved 23 September 2020. 
  57. Jackson, C.; Shahsahebi, M.; Wedlake, T. et al. (2015). "Timeliness of Outpatient Follow-up: An Evidence-Based Approach for Planning After Hospital Discharge". Annals of Family Medicine 13 (2): 115–22. doi:10.1370/afm.1753. 
  58. Futrell, K. (18 April 2018). "Health information technology can support population health management". Medical Laboratory Observer. https://www.mlo-online.com/information-technology/lis/article/13009479/health-information-technology-can-support-population-health-management. Retrieved 23 September 2020. 
  59. "Provantis: Integrated preclinical software". Instem LSS Limited. https://www.instem.com/solutions/provantis/index.php#2. Retrieved 23 September 2020.