Records For Living Community

Share Information about HealthFrame and taking control of your own healthcare
Welcome to Records For Living Community Sign in | Join | Help
in Search

Adding and editing tests

Last post 04-24-2018, 2:04 AM by dealio. 1 replies.
Sort Posts: Previous Next
  •  04-20-2018, 3:58 PM 1946

    Adding and editing tests

    Currently, in the Ordered section, populating the [During Visit] field auto-populates and locks the [By] and [Date] fields. It is possible to have tests ordered by different contacts during a visit. It is possible for tests to be ordered on multiple days of a visit. While auto-populating the fields might speed data entry in most cases, locking the fields is not helpful. We need to be able to record [During Visit], [By], and [Date] independently. Auto-fill of default values makes sense. Preventing them from being altered does not.

    Currently, in the Administered section, setting the section to "Same As Ordered" eliminates even seeing the values assumed for Administered [During Visit], [By], [Start Date], and [Start Time] fields. Even if all other information remains the same as ordered, the time administered may need to be recorded when a test occurs more than once during a visit or is administered at a significantly different time than the nominal time of the visit.

    If the Administered section is set to "Self" or "Additional Details", populating the [During Visit] field auto-populates and locks the [By] and [Date] fields. It is possible to have tests administered by different contacts during a visit. It is possible for tests to be administered on dates other than the nominal date of a visit. It is possible for the same type of test to be administered multiple times during a day; even if all other information remains the same, recording the time administered is necessary to differentiate between multiple tests of the same type on the same day or when a test is administered at a time significantly different from the nominal time of the visit. While auto-populating the fields might speed data entry in most cases, locking the fields is not helpful. We need to be able to record [During Visit], [By], and Start/End [Date] and [Time], independently. Auto-fill of default values makes sense. Preventing them from being altered does not.

    Consider the following scenarios:

    1. Single-day, multi-hour visit for therapy with tests ordered by Contact A, administered by Contact B, before and after therapy.

    2. Five-day hospitalization with multiple contacts assigned to the case, all capable of ordering tests on different days, administered by still other contacts at different times. Different contacts order CBCs and Basic Metabolics to be administered at different times on the same day. Same contact orders Troponin levels four times over a 24-hour period crossing dates that show a rise then fall in enzyme levels. Date and time are important for accurate recording and reporting even in the same visit.

    3. Visit to Clinic. Clinic Contact orders labs to be drawn at a free-standing lab. Tests administered during Lab visit on another day by two Lab Contacts over several hours.

    In addition to the data entry, lists and reports and charting would be more helpful if they included the test times in sort and display, especially in the cases where there are multiple tests of the same type on the same day or different days of a multi-day stay. Even if a test only occurs once in a visit, recording when it happened during a day can give additional context.
    - Tom
    Idea <i>You have the power to give life.
  •  04-24-2018, 2:04 AM 1949 in reply to 1946

    Re: Adding and editing tests

    Yes, this is one of the issues I've mentioned in a post or two before, and my work-around was to use self-administered wherever I could, but you are correct -- that isn't really accurate and context is lost as a result. I typically try to recover from that by addressing the fact in the notes, but that has it's issues as well.

    .
    - TIA for your help!
    David
View as RSS news feed in XML
Powered by Community Server, by Telligent Systems