1



1501775292163500CRIS Release Notes 2.09.10t1 specificCopyright? Healthcare Software Solutions 2014Registered Office: 3rd Floor i2 Mansfield, Hamilton Court, Oakham Business Park, Mansfield, NG18 5FBThese materials are or comprise restricted and proprietary confidential information of Healthcare Software Solutions. Disclosure to or use by the recipient shall not convey any intellectual property rights in these materials. The right to use these materials by the recipient is subject to restrictions and limitations contained in the Provision of Integrated Care Record System and Associated Services Agreement and related agreements.ConfidentialityAll information in this document is provided in confidence for the sole purpose of adjudication of the document and shall not be used for any other purpose and shall not be published or disclosed wholly or in part to any other party without HSS prior permission in writing and shall be held in safe custody. These obligations shall not apply to information which is published or becomes known legitimately from some source other than HSS. Many of the product, service and company names referred to in this document are trademarks or registered trademarks. They are all hereby acknowledged.Document ControlTitleCRIS Release Notes 2.09.10t1 specificAuthorGary GloverDate Created25/08/2015File Ref. FILENAME CRIS Release Notes 2.09.10t1 specific D5.0.docxCRIS Version2.09.10t1Change HistoryIssueDateAuthor / EditorDetails of ChangeD1.021/08/2015Gary Glover2.09.10t1 initial draft.D2.025/08/2015Gary GloverRemoved references to development product names.D3.0Bazil CaygillD4.014/09/2015Gary GloverCorrected the new security setting outlined in issue CRIS-1013.D5.024/09/2015Gary GloverIssue CRIS-1163 completedReview DateContents TOC \o "1-2" \h \z \u 1.Introduction PAGEREF _Toc430863173 \h 51.1.Purpose PAGEREF _Toc430863174 \h 51.2.Audience PAGEREF _Toc430863175 \h 52.Authentication PAGEREF _Toc430863176 \h 62.1.New Functionality PAGEREF _Toc430863177 \h 63.Core PAGEREF _Toc430863178 \h 73.1.New Functionality PAGEREF _Toc430863179 \h 73.2.Enhancements PAGEREF _Toc430863180 \h 73.3.Resolved issues PAGEREF _Toc430863181 \h 84.Database PAGEREF _Toc430863182 \h 104.1.Resolved Issue PAGEREF _Toc430863183 \h 105.Date Formatting PAGEREF _Toc430863184 \h 115.1.Resolved Issues PAGEREF _Toc430863185 \h 116.Event Details PAGEREF _Toc430863186 \h 136.1.Resolved Issue PAGEREF _Toc430863187 \h 137.GUI PAGEREF _Toc430863188 \h 157.1.Resolved issue PAGEREF _Toc430863189 \h 158.Interfaces PAGEREF _Toc430863190 \h 168.1.New Functionality PAGEREF _Toc430863191 \h 168.2.Resolved Issues PAGEREF _Toc430863192 \h 189.Post Processing PAGEREF _Toc430863193 \h 209.1.New Functionality PAGEREF _Toc430863194 \h 2010.Printing PAGEREF _Toc430863195 \h 2110.1.Resolved Issue PAGEREF _Toc430863196 \h 2111.Reporting PAGEREF _Toc430863197 \h 2211.1.New Functionality PAGEREF _Toc430863198 \h 2211.2.Resolved Issue PAGEREF _Toc430863199 \h 2512.Sessions PAGEREF _Toc430863200 \h 2712.1.Resolved issue PAGEREF _Toc430863201 \h 2713.Setup Tables PAGEREF _Toc430863202 \h 2813.1.Resolved Issue PAGEREF _Toc430863203 \h 2814.Stats PAGEREF _Toc430863204 \h 2914.1.Enhancement PAGEREF _Toc430863205 \h 2914.2.Resolved Issue PAGEREF _Toc430863206 \h 2915.Vetting PAGEREF _Toc430863207 \h 3015.1.Resolved issues PAGEREF _Toc430863208 \h 3016.Worklists PAGEREF _Toc430863209 \h 3216.1.New Functionality PAGEREF _Toc430863210 \h 3216.2.Resolved Issues PAGEREF _Toc430863211 \h 33IntroductionPurposeThis document will outline the functional changes made to this release. It will detail any new features, enhancements to existing functionality and list changes made due to existing functionality not working as expected.AudienceThis document is primarily for the customer, so they have a clear understanding of what is included compared to previous releases. Internal stakeholders such as sales, product/client managers and Release Management personnel will also have visibility to this document and be involved in the review process.AuthenticationNew FunctionalityCRIS-1057 Single Sign On implementation with ADDescriptionWe need to provide the facility for automatic login using Single Sign On, which is validated against the Active Directory domain. Shared workstation facilities are also needed to be implemented.ResolutionSingle Sign On is now implemented as required.Fixed in2.09.10t1CoreNew FunctionalityCRIS-960API for AVDATA for external systemsDescriptionProvide an API for external systems to retrieve AVDATA documents on request so that these are available on request from external systems without relying on HL7 messagingResolutionIt is now possible to transfer AVData via HTTP instead of FTP. This is configured by the XR setting AVDATAMANAGER.useHTTP. In addition, the following XR settings should be configured to point to the new AVData system: AVDATAMANAGER.HTTP.URL, AVDATAMANAGER.HTTP.User and AVDATAMANAGER.HTTP.Password.Note that data migration is required before the HTTP solution can be implemented.Fixed in2.09.10t1 EnhancementsCRIS-1076Cannot close ‘role selection’ dialog box.DescriptionIf a user has a number of available roles, when the dialog appears so the required role can be chosen, there is no way the user can cancel the login process and shut down the application.ResolutionThe user can now *shut down CRIS* during the login process by closing the role selection dialog box.Fixed in2.09.10t1CRIS-845Reduce the numbers loaded upon loginDescriptionWhen CRIS has been deployed as part of a large consortium, the login process is taking too long. This is caused because it reads all of the users from the ‘staff’ table into memory as it starts up. ResolutionChanges have been made to reduce the time taken to complete the visible startup process, by processing old staff members in the background, whilst the current user maintains control of the application. Fixed in2.09.10t1CRIS-1059Printing delays in CRISDescriptionThe introduction of saving the printed reports has significantly increased the time between requesting one batch print and being able to change the filter to request the next one: CRIS is hanging at a point when users are expecting to be able to make changes.ResolutionAn additional thread was added to handle storing items in an analogous way to printing them that was already present. Essentially, each item is placed in a queue and control is immediately passed back to the rest of CRIS. The background thread then handles the processing of the queue. This avoids the hanging, and ought to allow for the "type-ahead behaviour" that had been possible previously.Fixed in2.09.10t1 Resolved issuesCRIS-1074Cannot select roles by using up and down arrow key in some cases.DescriptionDuring startup process, Role selection dialog box in CRIS, is not working as expected in some cases. (i.e. cannot select roles without pressing the TAB key)ResolutionThe ‘roles’ can now be selected using the ‘up’ and ‘down’ arrows as expected.Fixed in2.09.10t1CRIS-1075When a role is selected by using keyboard, incorrect activities are shown in Role selection dialog box.DescriptionWhere a user has multiple roles, selecting a specific role doesn’t display the associated activities of that role in the ‘Roles’ selection dialog box.ResolutionThe associated ‘activities’ are now displayed correctly when a user selects a particular role.Fixed in2.09.10t1CRIS-1077Patient event list datesDescriptionWhen undertaking the following sequence:create a new event as a request; appoint it; cancel it; reappoint with different date and time; and then reload the patient event listThe time (onscreen) is correctly updated to the new time, but the onscreen date is not.The underlying data in the database has been correctly updated.ResolutionThe correct date is now displayed onscreen alongside the correct time.Fixed in2.09.10t1CRIS-1116Nuclear Med - Syringe info not insertingDescriptionIt is not possible to attach syringe information against an event due to adatabase error.The issue is that the time format is ‘hh:mm’, which is 5 characters in length but the database field only hold 4 characters – ‘hhmm’. ResolutionThe GUI will always display the 5-character format. Before this is saved to the database, the ‘:’ is removed, so the time is saved without error.Fixed in2.09.10t1DatabaseResolved IssueCRIS-1010Error in ‘Batch verify’ due to time being stored incorrectlyDescriptionWhen adding a report to batch verify, the time is stored with a colon, e.g. 09:50. This leads to an error when loading the batch from the batch verify screen.ResolutionThe GUI will always display the 5-character format. Before this is saved to the database, the ‘:’ is removed, so the time is saved and retrieved without error.Fixed in2.09.10t1The GUI will always display the 5-character format. Before this is saved to the database, the ‘:’ is removed, so the time is saved without error.Date FormattingResolved IssuesCRIS-1005DOB field no longer accepts certain date formatsDescriptionSince the changes to the date field layout, it is no longer possible to enter certain formats into the DOB fields in CRIS.For example, entering any of the following into the DOB field on the main CRIS screen in order to search for a patient brings back 16-Apr-0076 instead of 16-Apr-1976: 160476, 16 04 76, 16 4 76, 16/4/76 or 16/04/76When entering into the DOB field on patient details the same date is calculated in the background and a warning message appear to say DOB cannot be more than 150 years in the past.Note that the above formats work as expected in other date fields.ResolutionDate of Birth / Date of death fields now calculate dates correctly and not from the year 0.Fixed in2.09.10t1CRIS-1006Certain date formats return an incorrect dateDescriptionRecent changes to the formatting of dates and times have been implemented. In particular, dates are now of the form dd-MMM-yyyy as opposed to dd/MM/yyyy. Since these changes, entering the following date formats no longer work as expected:(1) dd-M-yyyy(2) dd-M-yy(3) dd.M.yyyy(4) dd.M.yy, (5) dd.MM.yy(6) dd.MM.yyyy (date before 2000 only)ResolutionAll expected date format entries are now supported.Fixed in2.09.10t1CRIS-1009Validation no longer occurs in the date fields in CRISDescriptionBefore the recent date/time formatting changes, if an invalid date was entered into a date field then a warning message would be displayed to the user and the field would be blanked. This no longer occurs and an unexpected and often seemingly random date appears in the field instead. E.g. Entering 31/04/2015 would evaluate to 01-May-2015.ResolutionChanges have been made to better handle the entry of dates in the various formats now supported, and to ensure that error messages are more coherent.Fixed in2.09.10t1CRIS-1217Printed Letter arrival times different from DiaryDescriptionWhen an appointment letter is printed from a worklist, the resulting letter has prep time for the examination taken into account. When printing an appointment letter directly from the diary, the prep time is not taken into account.ResolutionThe ‘prep’ time is now being accounted for irrespective from where the letter is being printed.Fixed in2.09.10t1CRIS-1239Diary number format exception.DescriptionErrors are generated when resizing an event on the Diary. An error dialog is produced when resizing an event on the diary, and the 'booked' field for the room is not incremented correctly.ResolutionDragging and re-sizing events on the diary now work as expected.Fixed in2.09.10t1CRIS-1245Date range not saving in Diary.DescriptionWhen attempting to close a time range in a room in the diary, an error is thrown and the closure is not saved. If a user right-clicks on a room header in the diary and selects 'Close time range', saving this range throws an error to say the value is too long.This is caused by colons not being removed before saving. E.g. if the time range is from 10:00 until 11:00, it attempts to save 10:0011:00 into the database, when it should actually be saving 10001100. It errors as the database field is only 8 characters long.ResolutionA date range can now be saved in the diary without error.Fixed in2.09.10t1Event DetailsResolved IssueCRIS-1086Events showing an incorrect status after rollbackDescriptionWhen statuses are added in CRIS, the most recent status is normally set to be the current status. However, certain statuses should never be set to current and, when one of these is added, the previous status remains the current one.The statuses that should never be current are those with category V (vetted), P (printed), E (emailed) or D (document). So, for example, if a request is created and then vetted, the request status will remain the current status.An issue occurs when doing Undo Attend, Not Performed. After the Not Performed status is added, it should add back the most recent current status. However, the usual check to ensure the previous status can be current is not done and so it is possible for one of the above four statuses to be added back as a current status.Example: An event is requested, appointed, printed, attended, and then undo attend, not performed is selected.This results in the following status list:Status 1 = Request, not currentStatus 2 = Appointed, not currentStatus 3 = Printed, not currentStatus 4 = Attended, not currentStatus 5 = Not performed, not currentStatus 6 = Printed, currentThis is incorrect as, although 'Printed' is the last status before 'Attended', it should not be set to current. The last status added should instead be:Status 6 = Appointed, currentResolutionThe correct status is now inserted after Undo Attend, Not Performed has been selected. This prevents the vetted, printed, and emailed or document statuses from being incorrectly set as the current status.Fixed in2.09.10t1CRIS-1132Error message displayed when changing event from daylistDescriptionAn error message is displayed, ‘Request has been deleted’, when following Change workflow from Day list.ResolutionFixed issue when updating the time an attendance is booked for.Fixed in2.09.10t1GUIResolved issueCRIS-1115Author, License and notes information can be changed by userDescriptionText in ‘Acknowledgements’ tab in ‘About CRIS’ dialog box can be manually changed by user.ResolutionThe text in this tab is no longer editable, therefore cannot be changed by the user.Fixed in2.09.10t1InterfacesNew FunctionalityCRIS-980Create a DTI interface for the HSS DTI Hub application.DescriptionThere is a requirement to create an interface for the HSS DTI Hub application.ResolutionImplemented HSS DTI Hub endpoint in CRISFixed in2.09.10t1CRIS-1011Sending Reporting Groups as intended reporterDescriptionWhere sites use reporting groups it can be useful to include the reporting group as part of the outbound message for PACSResolutionIt is now possible to send out resource groups across the PACS interface in HL7 messages. These are sent only when the attribute SendAdditionalNTEInfo is set to true (default false). In addition, the EJBSERVER user must have GENERAL.ResourceManagementModuleAvailable = 'Yes'. The group information is sent out in NTE segments with the first repetition containing the code, the second repetition containing the description and NTE:4 containing 'RG' to identify this segment as a resource group.E.g.NTE|1||Resource group code 1~Group 1 description|RGNTE|2||Resource group code 2~Group 2 description|RGAs resource groups are stored at exam level, if an event contains multiple exams then the message for each individual exam will only contain groups assigned to that exam.Note that a change has been made to the IEP interface to send out a set of NTE segments per exam whenever SendAdditionalNTEInfo = true. This is to ensure groups against all exams are sent. If the attribute is set to false then it works as it currently does and only sends NTE segments in the first exam section.Fixed in2.09.10t1CRIS-1014Protocol field to be included in messaging to PACSDescriptionWhere vetting is done, it is useful to be able to message the protocol selected or created to the outbound interface, both with PACS driven reporting and external tele radiology services. This component should be a configurable part of outbound messages.ResolutionIt is now possible to send protocol information with any outbound OMG/ORU message to PACS or IEP. The information is sent in NTE segments, with the protocol text sent in NTE:3. This functionality is wrapped around the new attribute SendAdditionalNTEInfo. If this is set to 'false' then only clinical history is sent in NTE segments, which is how it worked before. If it is set to 'true' then it will send both clinical history and protocol information. In addition, if the attribute is set to true then NTE:4 is populated with 'CH' or 'PR' respectively, to show whether this text is clinical history or protocol info respectfully. The attribute is 'false' by default.Fixed in2.09.10t1CRIS-1034Event Comments required to pass to the PACS interfaceDescriptionInterface change required to ensure the event comments are sent, like the clinical history field, with note type (NTE:4} populated with RE for remark . Likely to require an attribute for backward compatibility.ResolutionEvent comments are now sent across the PACS interface whenever the attribute SendAdditionalNTEInfo is set to true (default false). The comments are sent in NTE:3 and NTE:4 is set to 'RE'.Fixed in2.09.10t1CRIS-1163Reason for exam and Clinical safety questions to be sent across interfaces in an NTE segmentDescriptionEMRAD requirementReason for exam and Clinical safety questions to be sent across interfaces in an NTE segment. This should be controlled by the attribute SendAdditionalNTEInfo.ResolutionClinical safety questions will now be sent to PACS in NTE segments whenever the attribute SendAdditionalNTEInfo is set to true. NTE:4 will be set to 'QN' for these segments.If the new attribute SendReasonForExam is set to true then OBR:31.2 will be populated with the Reason for exam. This field will be split into multiple repetitions whenever the text exceeds length 300, or whenever a line break appears in the text.Note that this change will also affect the IEP interface.Fixed in2.09.10t1CRIS-1164When a merge is done in CRIS it should create a trigger leading to an A08 message – EMRADDescriptionWhen a CRIS merge is performed, a MERGE interface trigger is create as expected. It should also be possible for an UPDATE trigger for the main patient to be created, leading to an A08 message. This should be switchable via an XR setting.ResolutionIt is now possible for an A08 message to be sent out following a patient merge in CRIS. The UPDATE trigger will be created as long as the new XR setting GENERAL.SendUpdateOnMerge is set to 'Yes' (default 'No'). The update message will be for the main patient.Fixed in2.09.10t1Resolved IssuesCRIS-998IEP Sends Wrong EventsDescriptionWhen sending events for reporting over the IEP interface, it is possible to configure the system to send prior events. These should be previous attendances for the same patient. This works as expected when sending events from the patient's 'Events' page. However, if sending from a worklist that includes attendances for other patients, it is possible for these attendances to be erroneously sent over the IEP interface.A change is required to ensure only priors for the selected event's patient are sent with the event that requires reporting.ResolutionThe IEP interface now sends the same priors for an event, regardless of whether the event was sent from the patient's event list or from a worklist.Fixed in2.09.10t1CRIS-1114Partial Clinical History signature sent over the interfacesDescriptionWhen sending messages to PACS, the Clinical History is sent across in NTE segments. The signature should be excluded from the message, i.e. the text that is automatically that displays the user, date and time. Example:Clinical History Line 1"(Entered By USER1 (Test User) on 22-Jun-2015 at 16:26)"This sends out:NTE|1||Clinical History Line 1NTE|2||on 22-Jun-2015 at 16:26)Only the first NTE segment should be sent.ResolutionThe signature is now fully removed from NTE segments as expected.Fixed in2.09.10t1CRIS-1167Adding a delay to an interface trigger no longer worksDescriptionIt is no longer possible to add a delay to an interface trigger in order to prevent it from being processed straight away. Any interface trigger will be processed on the hour of the time due. So, for example, if the current time is 9:25 and a two minute delay is added so that the time due is 9:27, the trigger will actually be picked up at any time after 9:00, meaning it will be picked up straight away rather than waiting the required two minutes.This will mean VERIFY triggers, which are delayed by two minutes as standard, will be sent out immediately. It also means that manual re-triggering, which should stagger the trigger processing to avoid too great a load, will no longer work, as the triggers will be processed in bulk on the hour.ResolutionAdding a delay to an interface trigger will now work as expected.Fixed in2.09.10t1Post ProcessingNew FunctionalityCRIS-959Allow Auto Reporting when Report Editor is restrictedDescriptionWhere restriction is enabled to stop the report editor being used, it must still be possible to allow a user to create auto reports in post processing - there should be a security setting for the user to indicate which users are allowed to auto report.Use the restrict report setting to implement the ability to auto report.ResolutionPermission to Auto Reporting feature now only depends on the System Setting, REPORT.AUTO_REPORT, regardless of other System Settings like GENERAL.CREATE_REPORT, GENERAL.CHANGE_REPORT and REPORT.PEER_REVIEW.(Note: if REPORT.AUTO_REPORT is not set, it is regarded as N (i.e. No))Fixed in2.09.10t1CRIS-961Post Processing to be read only once event is sent for external reportingDescriptionPost Processing should be locked so that changes can't be made once an event is being reported externally to stop changes to exams, etc being made.Two new settings are required.An XR setting that ‘locks down’ the exam once it has been processed.A security setting to allow only ‘super users’ to override the ‘lockdown’.Also need to add functionality for resending of post processing messageResolutionPost processed data can now be locked down with XR setting ‘POSTEXAM.LockdownPostProcessing’ set to ‘Yes’ but can be overridden if the user has the ‘GENERAL.OVER_PPROC_LOC’ security setting.Fixed in2.09.10t1PrintingResolved IssueCRIS-1097Printed Documents stored on the server results in NullPointer ErrorDescriptionIt is possible that if a user attempts to print a document a null pointer exception will be generated, this occurs when using HTTP not FTPResolutionWhen storing printed documents, a previously closed data transaction is trying to be closed again, leading to the error message seen. The error is no longer thrown and additional debug is added to inform the user when it is attempting to close an already closed transaction.Fixed in2.09.10t1ReportingNew FunctionalityCRIS-958Obstetrics reporting with external report interfaceDescriptionWhere the report editor is restricted to read only, it must be possible to configure at modality level which of the modalities this restriction applies to such that an event of modality 'O' is still reportable in CRIS.Possible solutions:Using the CRISMODL table to include extra field to enable an override of report, if report is set to read only.XR Setting If it's required to be site/trust specific then does it make more sense to add an XR setting? We could have it so that, for anything at all to be reported, the user must still have GENERAL.CREATE_REPORT/GENERAL.CHANGE_REPORT. But then, if they have an addition XR setting, e.g. Report.ModalitiesForReporting, set then only the modalities listed in this setting can be reported. E.g. Report.ModalitiesForReporting = O, M then only obs and MRI exams can be reported. If Report.ModalitiesForReporting is not set it could continue to work as it currently does. Would need to think about what to do for mixed modality events.ResolutionNew XR Settings: REPORT.ModalitiesForReporting.Other Affecting Settings: System Settings: GENERAL.CREATE_REPORT, GENERAL.CHANGE_REPORT, REPORT.AUTO_REPORT and REPORT.PEER_REVIEW.Any kind of modality including Obstetrics can be restricted.Reporting facility is allowed mainly based on the modalities provided through the XR Setting, REPORT.ModalitiesForReporting, and if the settings is empty, it implies all the modalities are allowed in reporting. Reports with no allowed modalities are not displayed unless there is a requirement for adding addendum, changing acknowledgement fields and/or changing double reporting.Main Areas where changes are mainly affected:XR Setting panel will pop up a multiple selection dialog box for modalities (Currently multiple selection dialog box is implemented for only modality even though underline API is also modified through this issue to compatible with other settings too. These enhancements will be addressed in future.)While creating a new event under Reporting mode, allowability for report creation is restricted mainly based on modalities and other relevant System Settings (these settings already are mentioned above).While creating a new event under sonographer mode, allowability for report creation is restricted based on modalities and other relevant System Settings.Reporting facility in Batch Verify List is restricted based on modalities and other relevant System Settings.Reporting facility in Day List is restricted based on modalities and other relevant System Settings.Reporting facility in Dictation List is restricted based on modalities and other relevant System Settings.Reporting facility in Event Details is restricted based on modalities and other relevant System Settings.Reporting facility in Event List is restricted based on modalities other relevant System Settings.Reporting facility in Post Processing is restricted based on modalities other relevant System Settings.Reporting facility in Report Info Lists is restricted based on modalities other relevant System Settings.Reporting facility in OverrideConsentReason is restricted based on modalities other relevant System Settings.CRIS Editor is restricted based on restricted based on modalities other relevant System Settings.Reporting facility in Session Management is restricted based on modalities other relevant System Settings.In a list, multiple selection of items may be enable or disable reporting button even though one event can only be reported.Event with at least one exam with allowed modality will enable reporting facility depending on other relevant System Settings too.Fixed in2.09.10t1CRIS-1013Restrict report editor to read onlyDescriptionWhere reporting is being done externally to CRIS, there needs to be a method for allowing users of CRIS access to the report editor to review reports, but not to create them unless specific criteria are met. Add a setting that restricts the report editor to view only, in that the report can be viewed and the finished page can be access such that double reporting/museum codes etc can be added as well as communicator type functionality still works.Ensure reporting can be restricted to view only without affecting other workflows around the report editorNew security setting , default No, that enables:- Acknowledgement status popup and panel- Double reporting fieldsChange Report =Y should override this settingPrint Report should also be allowedSetting to be called restricted reporting modeRestricted reporting mode to be able to be set independently of change report setting and still have the complete desired effect.ResolutionChanges made ensure that when GENERAL.CHANGE_REPORT and GENERAL.CREATE_REPORT (which are set in tandem) are set to "N" (No), then by setting REPORT.PEER_REVIEW to "Y" it is possible to edit both Acknowledgement and Double Reporting sections on the ‘FinishedPage’.Otherwise, behaviour is unaffected.GENERAL. CREATE_REPORT/ CHANGE_REPORTPEER REVIEWOUTCOMEYNIgnore restricted reporting setting, allowed to do anythingYYIgnore restricted reporting setting, allowed to do anythingNNWorks as it currently does, i.e. cannot do any kind of reportingNYCan change acknowledgement/double reporting sectionsFixed in2.09.10t1CRIS-1012RCR Reporting Guideline Changes - Visibility of name/grade etcDescriptionVisibility of name, professional status, grade, position and registration number is required when reporting. Identification of their name, professional status, grade, position and registration number is required when recording their interpretation of an imaging investigation. This can be achieved using a free text 'signature' field.Add four free text fields to the Clinicians table: Primary Signature, Primary Signature Description, Alternative Signature, and Alternative Signature Description. They can then be included in interface messages/printed reports, although they will not be displayed in the CRIS report editor itself or saved in the database as part of the report text.In terms of the interfaces, the signature should be included in an OBX segment following the report text. The signature used should relate to the clinician sent in OBX:16, which will be the person who reported, verified or addended the report. This should be the primary signature only and whether or not to send it should be switchable via a new attribute. This functionality should be added for all interfaces.It should be possible to display both the primary and the secondary signature in a printed report. ResolutionRadiologist 'signature' is now appended to reports. There is a new attribute which controls this - 'IncludeClinicianSignature'.Fixed in2.09.10t1Resolved IssueCRIS-962Editing report text after removing clarificationDescriptionIf a report has clarification markers, and a particular workflow is followedto remove the mark and edit text, it causes the exception error below:2013-06-14 12:47:31,652 [AWT-EventQueue-1] DEBUG hss.digitaldictation.dragonapi.DragonAPI caretUpdate 260 - Caret changed2013-06-14 12:47:35,085 [AWT-EventQueue-1] DEBUG hss.digitaldictation.dragonapi.DragonAPI caretUpdate 260 - Caret changedUncaught exception in event thread for java.awt.event.KeyEvent[KEY_PRESSED,keyCode=8,keyText=Backspace,keyChar=Backspace,keyLocation=KEY_LOCATION_STANDARD] on hss.radiology.reports.CrisEditor[,0,0,1215x474,layout=javax.swing.plaf.basic.BasicTextUI$UpdateHandler,alignmentX=0.0,alignmentY=0.0,border=javax.swing.plaf.basic.BasicBorders$MarginBorder@250cce,flags=360,maximumSize=,minimumSize=,preferredSize=,caretColor=sun.swing.PrintColorUIResource[r=51,g=51,b=51],disabledTextColor=javax.swing.plaf.ColorUIResource[r=184,g=207,b=229],editable=true,margin=javax.swing.plaf.InsetsUIResource[top=3,left=3,bottom=3,right=3],selectedTextColor=sun.swing.PrintColorUIResource[r=51,g=51,b=51],selectionColor=javax.swing.plaf.ColorUIResource[r=184,g=207,b=229],kit=hss.radiology.reports.ReportEditorKit@1fc719b,typeHandlers=]java.lang.ClassCastException: java.lang.Boolean??? at hss.radiology.reports.ReportDocument.remove(ReportDocument.java:604)??? at javax.swing.text.DefaultEditorKit$DeletePrevCharAction.actionPerformed(Unknown Source)??? at javax.swing.SwingUtilities.notifyAction(Unknown Source)??? at javax.swing.JComponent.processKeyBinding(Unknown Source)??? at javax.swing.JComponent.processKeyBindings(Unknown Source)??? at javax.swing.JComponent.processKeyEvent(Unknown Source)??? at java.ponent.processEvent(Unknown Source)??? at java.awt.Container.processEvent(Unknown Source)??? at java.ponent.dispatchEventImpl(Unknown Source)??? at java.awt.Container.dispatchEventImpl(Unknown Source)??? at java.ponent.dispatchEvent(Unknown Source)??? at java.awt.KeyboardFocusManager.redispatchEvent(Unknown Source)??? at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(Unknown Source)??? at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(Unknown Source)??? at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(Unknown Source)??? at java.awt.DefaultKeyboardFocusManager.dispatchEvent(Unknown Source)??? at java.ponent.dispatchEventImpl(Unknown Source)??? at java.awt.Container.dispatchEventImpl(Unknown Source)??? at java.awt.Window.dispatchEventImpl(Unknown Source)??? at java.ponent.dispatchEvent(Unknown Source)??? at java.awt.EventQueue.dispatchEvent(Unknown Source)??? at hss.app.WaitCursor.dispatchEvent(WaitCursor.java:47)??? at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)??? at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)??? at java.awt.EventDispatchThread.pumpEvents(Unknown Source)??? at java.awt.EventDispatchThread.pumpEvents(Unknown Source)??? at java.awt.EventDispatchThread.run(Unknown Source)ResolutionIf the ‘clarification’ markers are removed, the remaining text can be edited without error.Fixed in2.09.10t1SessionsResolved issueCRIS-1220Error message when saving comments in sessionsDescriptionAn error message is thrown when saving a comment to a session event.ResolutionThe error was being thrown by the database due to an underlying ‘date/time’ formatting error. The formatting has now been corrected and the session data can be saved as expected.Fixed in2.09.10t1Setup TablesResolved IssueCRIS-1058Intended Clinician cannot be applied via Protocol TemplatesDescriptionWhen attempting to add the 'Intended Clinician' to an existing protocol template the value is not saved. The problem also applies to new Protocols as well as existing protocols.ResolutionA change to the template is now correctly flagged when editing a protocol from the setup screen allowing ‘Intended Clinician’ field to be saved correctly.Fixed in2.09.10t1StatsEnhancementCRIS-1146Stat date csv output formattingDescriptionIt should be possible to configure whether stats outputs display dates in the new format (dd-Mon-yyyy) or continues to use the old format (dd/MM/yyyy). Using the new format may affect sites who require the output to be used in downstream systems.Add a new XR setting called STATS.UseCUIDateFormat. If set to 'Yes' it should use the new format and set to 'No' it should continue to use the old one. The default should be 'No'.ResolutionThe stats output can now display dates in either the new or the old format, depending on whether the XR setting STATS.UseCUIDateFormat is set to 'Yes' or 'No' respectively. By default the old format will be used.Fixed in2.09.10t1Resolved IssueCRIS-1107Unable To Run Stats Where Date Fields Are RequiredDescriptionWhen running a stat with a 'Calculated' date field, an error is displayed indicating that the month is invalid. This happens due to the formatting forced within CRIS conflicting with underlying code.There is also an issue when running stats with DATE.TODAY in the Stat Start/End Date field, as this will also throw a formatting error.ResolutionStats fields that return dates and are calculated from a Stats Method (e.g. Derived fields) were being run with the wrong date format. This caused the sql to error. The format has been updated to the new 'dd-MON-yyyy' format, which is compatible with both oracle and postgres, and so the error no longer occurs.Adding DATE.TODAY to the Stat Start/End Date fields also now uses the new 'dd-MON-yyyy' format and so no longer errors.In addition, existing stats with a date saved into Stat Start/End Date in the old format would also throw errors. A database script will be run on update to change all such dates to the new format.Fixed in2.09.10t1VettingResolved issuesCRIS-1085Radiologist widget Vetting list filtersDescriptionWhen using the Radiologist widget with the vetting list, the counts are incorrect when clicking through to the list from the generated numbers.The issue appears to be with the Justify box on the vetting list being populated with ‘Y’ when clicking through from the widget. Changing the ‘Y’ to Blank will then show the same counts as on the widget.A fix is required to ensure that the justify field is always defaulted to Blank when loading from the Radiologist Widget.ResolutionThe vetting list now sets the ‘Show Justified’ field to Blank whenever it is loaded from the Radiologist Widget.Fixed in2.09.10t1CRIS-1089‘Required within X number of days’ Protocol Template VettingDescriptionIt has been noticed that the 'Required By' field via the Protocol screen does not clear/update correctly.This occurs when a protocol template is selected with a ‘Required within X number of days’ defined via the Protocol Template. This populates the ‘Required By’ field in the event as expected. However, if the user then chooses a different Protocol Template which does not have a defined ‘Required within X number of days’ – i.e. a blank field via the template, then the date from the previous protocol is not updated.The ‘Required within X number of days’ needs to update based on the template when the previous template had a positive value and the subsequent template had a blank value.ResolutionSelecting a protocol that is configured with a blank required number of days will now blank out the 'Required By' field when vetting.Fixed in2.09.10t1CRIS-1227Waiting status vetting issueDescriptionWhen vetting and rejecting a Waiting status event in CRIS it doesn't display the thumbs down icon.?If the event is vetted and rejected a second time the thumbs down icon then displays.ResolutionChanges were made to the ‘Vetting Status’ update process to ensure that if a Vetting Rejected action is requested this is correctly stored against the current event.Fixed in2.09.10t1WorklistsNew FunctionalityCRIS-1154Vetting and Reporting Group development to enable use of the functionality.DescriptionThe new ‘Group’ fields in the [Vetting List] and [Report Info List] have two key limitations which means it is difficult to implement or use the new functionality.The Groups make use of the already existing ‘Resource Group’ and ‘Resources’ tables in CRIS which are associated with the Resource Module. However unless both the Vetting Module and Resource Module are fully implemented the only method of applying ‘Groups’ either for Vetting or Reporting is manual per individual event details via event details or by right-clicking the event from the events list or a worklist. Both methods require 4 key presses to initiate and complete a pop up screen which is laborious and is not in line with other existing functionality which enables customer to easily assign vetting and reporting worklists via practitioner and intended clinician.It is also impossible to multi assign ‘Groups’ to events which do not require vetting, or attendances as the only place this function is available is via the [Vetting List] screen and exams not marked as vetting required, and attendances do not appear here. This is a significant retrograde step for sites who are used to managing Reporting list using intended Clinician via the Post Processing and using ‘multi-select’ via the [Report Info List] and using right click ‘Intended Clinician’ functions.ResolutionAdded 'resource' group field to : Event lists (via right-click, multple can be selected) Post Processing Event Entry KNOWN ISSUE: When this new setting GENERAL.SingleResourceGroupPerEvent is set to 'Yes', an error is thrown when using batch verify with Order set to 'Batch'. This issue will be fixed in a patch against CRIS-1281.Fixed in2.09.10t1CRIS-1198Adding dates when report info list is loadedDescriptionDates must be displayed under date fields when report info list is loaded in the very first time (i.e. when no preferences for dates are available).ResolutionDates are displayed under date fields when report info list is loaded.Fixed in2.09.10t1Resolved IssuesCRIS-1052Date fields in report info listDescriptionIf date preferences for Report info list are deleted in the DB then the Start and End date fields in the report info list will become unusable.ResolutionWhen preferences are not available for start date and end date, the following default will be set: Start date = a week before End date = current date (i.e. today).Once this is changed, the changes will be stored to the user’s preferences.Calendar control is working and F4 keystrokes are working as expected in all cases.Fixed in2.09.10t1CRIS-1069Vetting List not working as expectedDescriptionWhen the Requested After field in Vetting List is not populated the list takes as its starting point today's date rather than having no lower bound on the date.ResolutionFunctionality has been introduced to ensure that empty date fields occurring in specific WorkLists pages were either returned as null values, or as today's date.Fixed in2.09.10t1 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download