Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merging Prescription and PRN Presription #8116

Open
5 tasks
aparnacoronasafe opened this issue Jul 5, 2024 · 3 comments
Open
5 tasks

Merging Prescription and PRN Presription #8116

aparnacoronasafe opened this issue Jul 5, 2024 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@aparnacoronasafe
Copy link
Member

aparnacoronasafe commented Jul 5, 2024

Is your feature request related to a problem? Please describe.
Prescription and PRN prescription are not 2 distinct items. PRN prescription is simply a prescription given by a doctor where the direction is to administer the medicine is based on any clinical condition, which is different from a normal prescription where medicine is administered daily twice, or repeatedly at said intervals.

Eg: Normal prescription-
Paracetamol 500mg once daily for 5 days
Screenshot 2024-07-04 at 5 21 30 PM

PRN prescription-
Take Paracetamol 500 mg if temp goes above 100F. Take up to 1000mg a day, with min 2hrs between the doses.
Screenshot 2024-07-04 at 5 22 40 PM

Therefore PRN is actually an indication of frequency in prescription.

Merging Prescription and PRN prescription would make data entry simpler

Describe the solution you'd like

The Prescription form will contain the following fields

Screenshot 2024-07-05 at 3 44 37 PM
NOTE: The text in red are the mandatory fields and the blue boxes are the various options available to the user.

To Do:

  • Merge Prescription and PRN prescription in the UI as well as the database
  • Add an option in Dropdown for Frequency with "PRN" as an option
  • Reorder the content of the prescription in the given order
  • Add start and end date and time. Start date should contain default date and time of data entry. Allow user to pre-date the start time up to the date and time of admission. End time should not be before start time.
  • Wherever Days and start date-time is given, Auto- calculate the end date time
@gigincg
Copy link
Member

gigincg commented Jul 9, 2024

@aparnacoronasafe Can you add some clarity to this?

Is it apt, to make PRN one option of frequency? FHIR Does this quite differently. Is frequency never applicable for PRN Prescriptions

Alt Reference: https://mn.gov/boards/assets/prescription%20abbreviations_tcm21-26882.pdf

@aparnacoronasafe aparnacoronasafe changed the title Merging Prescription and PRM Presription Merging Prescription and PRN Presription Jul 10, 2024
@aparnacoronasafe
Copy link
Member Author

aparnacoronasafe commented Aug 19, 2024

@gigincg

Referring to FHIR structure here: https://build.fhir.org/medicationrequest0307.json.html
The PRN medication request is written as
Medicine:
Dosage instruction: Take if pain persists
Dosage: 1 tab
frequency 4 hrs

The problem with defining prescription this way is, in MAR, the medicine may come up as needing administration every 4 hrs. Which may arise confusion.

Medicine frequency is not applicable for PRN prescription. A more accurate way to define it is to simply define "min time between 2 dose" and "Max dose in 24 hrs". This is also the practice among doctors.

Hence, I believe it is better to follow the structure above.

You are right in saying that PRN is not an option within Frequency. The more apt way to do it is to let the user select between "PRN/Scheduled", if, scheduled, then have the option for frequency.

It is recommended to provide all options under frequency only with the intention to avoid having two input fields, instead of 1

@bodhish
Copy link
Member

bodhish commented Sep 6, 2024

@gigincg @aparnacoronasafe

How important is this now? I am quite convinced that our UI/UX for prescription is quite broken so can this be done as part of a refactor?

@bodhish bodhish added the enhancement New feature or request label Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Blocked
Development

No branches or pull requests

4 participants