Please take a look at this code that adds the option to subtype an Issue:
This is actually three commits from based off of Brady’s master file. I am slowly conquering Git…
A method for subcategorizing Issue items:
Allowing subcategorization does not affect any current feature, but extends the display options for future uses. It does not affect reporting functions, as items with subtypes are still categorized using their parent/original attribute. New Issues can still be created, and they too could be extended with subtypes.
Use Case Examples:
A provider might like to subcategorize medicines they prescribed for their particular specialty. For an oncologist this medications_issue_list may have a subtype of “onc”. For Ophthalmologists, eye diseases, usually listed as a medical problem, can be displayed as a new category by adding “eye” as a subcategory to a medical_problem_issue_list item. In the browser, if a user looks at the Administration->Lists->Medical Problem Issue List (medical_problem_issue_list), a new column “subtype” appears.
The Eye Form uses this feature to create a new separate element “Past Ocular History” for display purposes, but items in this category are actually medical problems, subtype eye, to the back end. For my purposes this is accomplished by adding the subtype to the table alone, but I found if a user made changes to the “list” in the Browser, without this new feature, they would wipe out the stored “subtype” values.
Please review the code and test it. I don’t think it breaks anything else ;).
Looks like you linked to just the last of your 3 commits, where you added and then deleted a bunch of stuff. Would be much easier to review if you combine them into 1 commit.
Hi Ray,
I placed some comments on github. I think that allowing subtype for both list_options and lists(Issues) makes a lot of sense(allows further differentiation of issues when needed(showing optho meds separately, for example), while supporting general reporting(showing all meds when print a patient ccda) ).
-brady OpenEMR