Investigations - Input Fields
Hi,
I am wondering if anyone has a good way to get histories typed into investigation letter documents.
Our system is set up so that to generate a pathology form you charge the item, it generates an investigation that has a path form associated with it, then you print the form associated with the investigation.
Is there a way to allow clinicians to input history into the form. I can't external edit the form that I can see.
I thought perhaps the notes field for the investigation could be renamed "history". Or a new history field could be created for investigations that is then inserted into the form?
Suggestions?
Re: Investigations - Input Fields
Adrian - it should be possible. If your "pathology form" is currently a Patient Form then you cannot have parameters for it. However, if you change its type to 'Patient Letter' then you could add a History parameter that would prompt for text. [and you can use macros to fast-fill the text]
You say "I can't external edit the form" - is this because it used jrxml content rather than odt content?
However, your idea of adding a History field to the investigation is not a bad one. Doing this would have the advantage that I suspect your staff would find it easier to edit the history text that if it were a prompted-for field in a Patient letter. Also doing this means that the 'I want to edit the history text in the path form' is independent of whether the form/letter template uses jrxml or odt content.
Regards, Tim G
Re: Investigations - Input Fields
Hi,
The way we currently print forms is by going to documents, selecting the investigation and clicking "Print". There is no external edit option.
Our forms are currently patient letters as OO documents, but when I put an input field into the document I still don't get prompted for an input. Form attached. Perhaps I added the input field incorrectly.
Re: Investigations - Input Fields
Adrian - I grabbed your form. It is correcctly set up - ie if I add it to the patient medical records as a patient letter, then I get prompted for the history.
However, it would appear that although one can attach a Patient Letter as a document to a product, it will be treated as a Patient Form and any input will NOT be prompted for - indeed the CSH text in https://openvpms.org/documentation/csh/1.9/product/tabs#document says:
This implies that the way to do what you want is to add a history field to the investigation - ie add the line
<node name="history" displayName="History" type="java.lang.String" path="/details/history" maxLength="2000" />
to act.patientInvestigation.adl and then import the modified archetype.
Then when the investigation is created you can enter any history test desired and then after tweaking the form to pull in the history field we get:
NOTE: rather than attaching the form as a document to the product, you will probably find it better to set it as the template for the investigation type via Administration|Types|Investigation - ie
Now when we edit the investigation we have:
and we can tweak the history and then use Print Form to reprint the submission form.
Regards, Tim G
Re: Investigations - Input Fields
Hi,
I have added the history field to the node. But not sure how to link this to the text into the Vetnostics form? Can you possibly send me the form you have modified?
Also, In the "Edit Investigation Type" screen. Is it possible to have a macro in the Description field that pulls the test name you are generating into this field?
What I would like to achieve is when I charge a vetnostics test, the investigation note field contains the text name....
Thanks,
Adrian
Re: Investigations - Input Fields
Adrian:
1) how to pull in the new field: from https://openvpms.org/documentation/csh/1.9/reference/reportFields - if you look about 2/5 the way down you will find the following table:
Now assuming that you added the history with the path /details/history, then we can access it simply via 'history' - ie
Note that we don't need any 'drill down' reference (as with product.entity.name) because we are pulling the field from the details part of the archetype.
2) pre-populating the Note field: if I understand you correctly, although the standard code fills the Note field with the name of the Investigation Type (eg 'Pathlab Test'), you wish this to contain the name of the actual product being sold (ie that which generated the investigation) - but as you can see below the name of the product is present.
So you need clarify what you want/need.
Regards, Tim G
Re: Investigations - Input Fields
Hi,
1) Working - Thanks.
2) Ok - perhaps better to describe what I am trying to achieve.
What we would like is for the product associated with investigations to appear in the description column of the documents and in the medical history. This assists in finding what test is where. Currently we have to manually add the test to the notes field to achieve this.
See attachments below. Here we had to manually write "Angylostrongylus Test" in the notes of the investigation for this information to appear in the medical history and document description field.
DEA Blood typing on the other hand did not have this information manually inserted so can't tell at a glance in these screens what this test is without clicking on it and opening the investigation or PDF.
Re: Investigations - Input Fields
Hi,
1) Working - Thanks.
2) Ok - perhaps better to describe what I am trying to achieve.
What we would like is for the product associated with investigations to appear in the description column of the documents and in the medical history. This assists in finding what test is where. Currently we have to manually add the test to the notes field to achieve this.
See attachments below. Here we had to manually write "Angylostrongylus Test" in the notes of the investigation for this information to appear in the medical history and document description field.
DEA Blood typing on the other hand did not have this information manually inserted so can't tell at a glance in these screens what this test is without clicking on it and opening the investigation or PDF.
Re: Investigations - Input Fields
Ahah - the light dawns - you want to adjust what shows in the medical records for an investigation. This is possible by over-riding the standard recipe - which is held in the file DefaultIMObjectTableModelFactory.xml which is part of (in my system) C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps\openvpms\WEB-INF\lib\openvpms-web-workspaces-1.9.3.jar - ie more generally <TOMCAT-HOME>\webapps\openvpms\WEB-INF\lib\openvpms-web-workspaces-1.9.3.jar
One can over-ride the default by putting a modified version of the this file named IMObjectTableModelFactory.xml in <TOMCAT-HOME>\webapps\openvpms\WEB-INF\classes. I have attached the 1.9 version of this file (I had to rename it with a .txt extension to attach it).
The 'how to display investigations' part is lines 41-46 - ie
so what we need to do is adjust line 43 as required and place this file in <TOMCAT-HOME>\webapps\openvpms\WEB-INF\classes\IMObjectTableModelFactory.xml so that we over-ride the default recipe.
If we adjust these to:
<string>act.patientInvestigation</string> <string>concat(openvpms:get(.,'investigationType.entity.name')," - Inv.ID=",/id," - ", /description, " - ",openvpms:get(.,'product.entity.name'), " [", substring(status,1,2), "]")then after restarting Tomcat we get:
Note that here the Investigation Type (eg 'Pathlab Test') is being repeated - the first is from the investigtionType.entity.name, and the second from the description (which you will recall, the code sets to the investigation name). Hence you may want to drop the description from the expression.
Note also that we use short names (eg IL, CE) for clinicians - yours will take more space, and that we show only the 1st two character of the status (ie [PO] == POSTED==Finalised).
Regards, Tim G
PS - Adrian - remember that if you do tweak this, then on any upgrade you will need to copy your saved adjusted IMObjectTableModelFactory.xml to <TOMCAT-HOME>\webapps\openvpms\WEB-INF\classes\ otherwise you will lose the customisation.
PPS - doing this customisation entitles you to add 'OpVexp' (OpenVPMS Expert) to your qualifications ;-)