|Home > System 6000 > Hints and tips|
- Using exec
- Printing advice leaflets
- Sophie Runtime parameters
- Sophie error checker
- Sophie Hooks
- Graphical SOPHIE Editor v1.0 Known Bugs and Workarounds
- Heading attachments
- Sophie drugs
The Exec question was put in for this purpose on System 5 many years ago, andcan be used to view your own html files as follows
You will have to call internet explorer( or other ), and have it fully pathed( it’s not normally in the c: folder!). Then pass the URL and this should workfine. The forward slash ” / ” is used as a delimiter between thedifferent sections in the construct of the question so beware if it is part ofthe URL.
At the end of running a sophie a question box comes up asking if you want toinsert into the notes and also print an advice leaflet. Both default to yes. Wegot fed up with sophie printing advice sheets we didn’t want when people forgotto uncheck the latter.
You can change the defaults by editing the sys6000.ini file held on eachworkstation in c:windows. 0 is no and 1 is yes as you’d expect. eg:
Here are the runtime parameters that SOPHIE can accept
|-m<H|S>||mode hidden or show (defaults to show)|
|-p<ID>||patient id (defaults to none)|
|-g<string>||guideline (defaults to none) (prepends path defined in .ini file, if not an explicit path)
The mode can be used to run watchdog SOPHIE’s, so -mH will run the SOPHIE in the background, and pop up if any user input is required. If this command is not present then the SOPHIE will be fired in the foreground.
|-p$PATIENTID||will automatically load the current patient into SOPHIE.|
|-g||used to define which guideline is run (e.g. -gs:meddatas6000guidelinesmeditelwellpers.gdl). Multiple -g statements can be used to fire several SOPHIE’s from one Read Code. In this case the user will be presented with a dialog before running any of the guidelines, asking which of the guidelines they wish to run. They can run any combination of the hooked guidelines.|
The sys6000.ini file contains the following section
The default path can be used to state where the guidelines are, but this mustbe set up on each individual workstation, so it may be better to explicitly paththe guidelines.
Those of you who have loaded v1.4 will have noticed the error checker whichruns automatically on loading SOPHIE. This is outlined in the documentation -what is not described is the way of turning this on and off. Only guidelineauthors need to have the thing turned ON – it will worry other users and slowdown the loading of SOPHIE, so they can have the thing turned OFF.
The ON/OFF switching is done in s6000.ini, where all the best fun is to behad. Look at the section headed [Guidelines]. This may or may not include aline:
If the line isn’t there, then add it, but if it is there then 0=OFF and 1=ON.
From within the Hooks Editor the individual parameters can be set as follows
- The Hook Type must be “Callback”
- The Hook Event Name can be either “Add Read Code” or “Save Entry”. “Add Read Code” is triggered when the note is entered and every time it is edited, whereas “Save Entry” is only triggered when the note is first created.
- The Event Trigger Value contains a Read Code, and must have 5 characters, padded to the right with dots, for both four and five byte systems.
- The mode is only useful for triggering in hidden mode for Watchdogs, and is -mH, otherwise the normal mode (-mS )is the default and run when no mode is specified.
- Before and After don’t have a great deal of use for the Sophie hooks.
- Any Read Codes in the hooked SOPHIE that are not explicitly put under a particular problem will be put in the problem from which the hooked note was entered. If the hooked note was a problem, then they will be put in that problem.
Listed below are the currently known bugs and workarounds. Please e-mail anyfurther bugs that you find to firstname.lastname@example.org.Please also use that e-mail address for any other correspondence about theGraphical SOPHIE Editor including requests for it. All of these bugs will befixed in the next release of the editor within the next couple of months.
1. Importing LOOK question
Bug: Importing a LOOK question transposes the connections. Thus when you exportit back, the “read code found” response is directed to the “readcode not found” response and vice versa.
Workaround: After exporting a protocol containing an imported LOOK questionwhich has not been changed, edit it using a text editor such as Wordpad andexchange the next question number for the $Y and $N statements.
2. Exporting MCQ10 question
Bug: When an MCQ10 question is exported, the protocol contains MCQTEN which theSOPHIE engine does not recognise.
Workaround: After exporting a protocol containing an MCQ10 question, edit itusing a test editor such as Wordpad and change all instances of MCQTEN to MCQ10.
3. Answers on LOOK question
Bug: When you click on bulbs to indicate Read Code found or Read Code not foundon the LOOK question, it gives OnOpenConnector error which does not allowentering note to be added or advice to be given.
Workaround: Use FETCH question which is intended to replace LOOK question andhas much more functionality.
4. FETCH question needs variable
Bug: If you delete the “variable to hold value” in the FETCH question,then the protocol gives an error when it is executed.
Workaround: Select a variable even if the question is not going to retrieveany data.
5. Importing DATE question
Bug: Importing a DATE question transposes the date limits in the VAL and LIMsegments. Thus when you export it back, the VAL contains the date limits fromLIM and vice versa.
Workaround: After exporting a protocol containing an imported DATE questionwhich has not been changed, edit it using a text editor such as Wordpad andexchange the date limits for the $VAL and $LIM statements.
6. Incorrect tool tip for CALC question
Bug: For a beginner user, when the cursor/mouse pointer is held over the bluequestion mark of a CALC question, the tool tip says “all answersconnector” and when the cursor/mouse pointer is held over the blue diamondmark of a CALC question, the tool tip says “Confirm user decision”,both of which are wrong.
Workaround: None needed as it is just a display issue.
7. Copying questions using held answer
Bug: When you select the two questions connected by a ‘using held answer’connector (and possibly any other questions) and try to cut/copy them, then theeditor crashes.
Workaround: Make sure that the set of questions that you are trying tocut/copy do not contain questions connected by a ‘using held answer’ connector.
8. Validating CONFIRM question
Bug: When a protocol is validated, it does not check to see if the NO answer ofa CONFIRM question is connected to any other question or marks the end of theguideline.
Workaround: Manually ensure that all CONFIRM questions are connectedproperly.
9. Using exported protocols with System 5
Bug: The instructions in the online help for the steps to be carried out to usean exported guideline with System 5 are incorrect.
Workaround: Do not perform the last step “Type the command SOU and pressEnter. This will update the System 5 SOPHIE contents and the guideline shouldnow be available to be picked from System 5 SOPHIE.” as that undoes thechanges made in the previous steps.
10 Small bug in the EXEC function:
If you enter a command line such as: /usr/bin/progname p% the first / is notrecognised by Unix and the exec fails. Placing it in quotes i.e. “/usr/bin/prognamep%” solves the problem, except that soped does not send the quotes. Theyhave to be added to the $EXEC function afterwards.
A little niggle, but something that needs to be remembered if either the gdlor wse file is re-edited in Soped as the quotes are lost again.
There are three basic types of heading attachment inSOPHIE
- @1, @2, @3 etc – tags notes to header specified in $PROBLEMS
- @99 – generates notes as ‘unlinked’.
- No @ at all – tags notes to problem you were in before firing SOPHIE
Sophie looks for authorisations.