Groupsites are branded collaboration communities that empower groups of all types and sizes to communicate, collaborate and connect around a shared mission, organization, cause or company.
$99/month
All-inclusive
No per-user fees
Try FREE for 30 days
No credit card required
After free trial ends, 30 days notice prior to cancellation
I am going through all our POCT tests and how they are entered into EPIC. It seems like we are all over the place and there is no standard. What do you have as fields under the Components? Right now we have QC/Patient logs for all tests, None of our instruments are interfaced and we are not accredited.
1. Lot number 2. Exp. Date 3. Result 3. Internal Control (does not have right now) 4. Anything else I am forgetting. image.png
Hi Anastasia, There is no other component that we use that you didn't list.
One note on the 'internal control'. I wasn't the contact with the builder when someone else added the 'internal control' as a component (originally when the POC Director and I did work with the builder, we had to resort to use a dot phrase for 'internal control' documentation). My disappointment was that whomever did build in the 'internal control' component only considered 'the C line' in the component text; technically, that does not capture all the onboard/internal controls in waived testing (e.g. background clearing, if a reagent goes from one color to another color after addition of a 2nd reagent to the 1st reagent), electronic internal controls that shut down the instrument/reader if they do not 'pass'.
Hi there, the POCT program I manage uses Epic and Enter/Edit in Ambulatory for non-interfaced tests as well. This is how our result field is set up. Also, I had our Epic report writers build a weekly report that pulls all Resulted POCT, and all Unresulted POCT (ordered but not resulted) to reconcile the manual test result logs from the offices to ensure all POCT is ordered, resulted and correct. This is the CLIA required audit mechanism for supervisory review of manually resulted POCT. image.png
There is no other component that we use that you didn't list.
One note on the 'internal control'.
I wasn't the contact with the builder when someone else added the 'internal control' as a component (originally when the POC Director and I did work with the builder, we had to resort to use a dot phrase for 'internal control' documentation).
My disappointment was that whomever did build in the 'internal control' component only considered 'the C line' in the component text; technically, that does not capture all the onboard/internal controls in waived testing (e.g. background clearing, if a reagent goes from one color to another color after addition of a 2nd reagent to the 1st reagent), electronic internal controls that shut down the instrument/reader if they do not 'pass'.
Good job!