{5} Assigned, Active Tickets by Owner (Full Description) (56 matches)
List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.
akollegger
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #290 | Database to database merge/sync | OpenMRS Code Base | task | 01/30/07 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The merge/sync operation would provide the ability to replicate patient data from one server to another. Scenarios to consider:
Unclear whether current plans to develop collaborative system (concept sharing and patient sharing) will replace this requirement. May be able to simply set sequence numbers at each site to allow for appending of patient information tables. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #291 | Bulk Concept Import | OpenMRS Code Base | task | 01/30/07 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Ability to import into Concept table and into Concept Name table. PurposeTo complement the concept export routines, it is necessary to have a concept import routine. This would help the transfer of concepts between servers, and also the importing of concepts mapped to external dictionaries like SNOMED and ICD. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
bmckown
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #167 | Cleaning Out Test Data | OpenMRS Code Base | OpenMRS 1.3 | enhancement | 08/02/06 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
We could use a button to delete patients/obs/concepts/forms. Implementors requested this in order to clean out test data. Done. There needs to be ample warning before the db is cleared. Done. Separate buttons should be used for each section. Done. TODO: Still working to resolve resetting auto_increment to value 1 for patients (persons). |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #805 | Regex validation on input fields. | OpenMRS Code Base | OpenMRS 1.3 | enhancement | 06/06/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
A general openmrs field validator could take in a regular expression and an input string to validate any input field. An administration section could allow the administrator to add a field type, a regular expression, and an example format for as many input fields as desired. The openmrs validator could take in a string and the regex in order to validate the field. It might also be able to parse the regex so that when the user enters a value, what is entered is actually what gets filtered from the parser. For person address, I am including a quick-fix patch that allows a regex and example format to be defined in the addressTemplate of openmrs-servlet.xml for any person address field. If the input does not match when editing a patient on the patient dashboard then the field(s) is/are highlighted, an error message is shown, and the page will not submit until the user enters the correct value. The patch directly applies to latitude and longitude values for the Kenya address template. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #689 | Enable Search by Identifier or Name when adding relationships | OpenMRS Code Base | OpenMRS 1.3 | task | 04/15/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
When adding a relationship for a patient at the dashboard, it yields no results when searching by patient identifier. This used to work, but quit working on a recent update. It is important to be able to find the person using either identifier or person name when adding a relationship. Also see... Implementers Mailing List Post |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
bwolfe
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #714 | PersonAttributeType with a format of java.Util.Date | OpenMRS Code Base | OpenMRS 1.4 | defect | 04/30/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
In order to store a date as a Person Attribute, you need to choose the format of java.util.Date. When doing this, a javascript calendar picker appears for the user to choose a date and save to the person. When viewing this patient again, no input box and no date appears as options. (as reported by James: https://listserv.iupui.edu/cgi-bin/wa-iupui.exe?A2=ind0804&L=openmrs-implement-l&D=1&T=0&O=D&P=11865 ) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #40 | PatientService.createPatient() should fail (or create temporary identifier) if identifier is missing | OpenMRS Code Base | OpenMRS 1.3 | defect | 03/23/06 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
We should not allow patients to be created without an identifier. Until we have created a means to auto-generate a guaranteed-to-be-unique temporary identifier on-the-fly, the PatientService.createPatient() method should throw an exception if the patient being created has a null or empty PatientIdentifier list. "temporary identifier" would be in the form Xnnnnn-c -- that is, start with a capital "X", then one or more numbers followed by a hyphen and check digit (calculated on "X" plus the string of numbers). Such temporary numbers are useful when no identifier (medical record number) has been assigned, yet the patient must be put into the system (e.g., emergency rooms often face this dilemna). Once a "real" medical record number can be assigned to the patient, the temporary number would simply become an alias. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #634 | Unlabeled symptom durations in Encounter view | OpenMRS Code Base | OpenMRS 1.3 | defect | 02/26/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
In the TB Screening section (it’s really similar to the adult DDB) the symptom concepts and duration of symptoms aren’t matching up with the system present findings. You can see that in the attached screen shot—Symptom present is below the big chart, but and there are unlabeled duration of symptom in days observations in the big chart. To make the form I just duplicated the schema for the Adult RV. The symptoms and their durations are showing up correctly when I test the Adult RV, so I’m not sure why this isn’t working. The form is saved as PROGRAMME PEDI VIH –RENDEZ-VOUS- Rwanda (v.1.0) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #140 | Dojoify the Openmrs Search Scripts | OpenMRS Code Base | OpenMRS 1.3 | enhancement | 08/01/06 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The search scripts should be merged into a widget in dojo. This will allow us to easily use them multiple times on a page in portlets. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #315 | Expand Capabilities of Person Object | OpenMRS Code Base | OpenMRS 1.3 | enhancement | 02/09/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The Patient and User objects need to extend Person:
Persons need to be able to have extendable attributes:
Model changes very similar to the 1.1pre data model image: http://openmrs.org/wiki/Image:Openmrs_data_model_1.10pre.png Related to the Relationship table restructuring - #316 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #24 | Various Form Hierarchy GUI Changes | OpenMRS Code Base | OpenMRS 1.3 | task | 03/17/06 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I'll fill this as I begin to play with it. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #209 | trac registration needs to be moderated | Trac | OpenMRS Someday | task | 08/25/06 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Users should not be able to register to the trac site without approval of a trac admin. I want to make it as easy and open as possible, but I also don't want our trac site to fall prey to spammers / hackers. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #225 | Download XSN broken by accent marks and special characters | FormEntry Module | FormEntry 2.7 | task | 09/14/06 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I tried downloading an XSN while my locale was set to French, and I get this error when I try to design the downloaded xsn in Infopath: An invalid character was found in text content. Line 467, Position 86 Here's the line from FormEntry.xsd that causes the problem:
When I extract the XSN and open FormEntry.xsd in emacs, it tells me that the coding system is "raw-text-unix". I changed that to "utf-8" which seems to solve the accent problem, but I hit problem #2. Concept names with special characters (like '<') need to be xml-escaped.
I manually fixed this in FormEntry.xsd, but now I just get the error "The parameter is incorrect" when I try to design from the xsf file. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #258 | Support Obs Groups in user interface | OpenMRS Code Base | OpenMRS Someday | task | 12/11/06 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The view encounter screen needs to be fixed to display groups correctly The encounter edit screen needs to display obs groups in some way The obs editing screen needs to be able to handle obs groups |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #611 | Remove xforms module dependency on formentry module | OpenMRS Code Base | OpenMRS 1.3 | task | 02/06/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The current xforms module uses several components of the formentry module. These components need to be either copied to the xforms module or moved to core openmrs. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #683 | Flowsheet module 1.2 errors with OpenMRS 1.2.02.3888 | OpenMRS Code Base | task | 04/11/08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I clicked on FLOWSHEET link from Encounters tab with version 1.2 and OpenMRS 1.2.02 and received the following error: An Internal Error has Occured org.openmrs.api.APIException I don't know what to do here because I don'tknow what the parent is of the group I'm being put into. This method is deprecated and should not be used. org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:285) org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:202) org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:418) org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:71) org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:124) org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:448) org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:169) org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:317) org.apache.velocity.app.Velocity.evaluate(Velocity.java:322) org.apache.velocity.app.Velocity.evaluate(Velocity.java:195) org.openmrs.module.clinicalsummary.web.GenerateSummariesServlet.doGet(GenerateSummariesServlet.java:138) javax.servlet.http.HttpServlet.service(HttpServlet.java:690) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.openmrs.module.web.ModuleServlet.service(Unknown Source) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) org.openmrs.web.OpenmrsFilter.doFilter(Unknown Source) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:198) org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:75) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) java.lang.Thread.run(Unknown Source) Version: 1.2.02 Build 3888 Database Version: 1.2.02 Cookies: dashboardTab-1=[patientEncountersTab] JSESSIONID=[970EBB00CAB184FFB3B981118A5B7A12] openmrs_language=[en_US] |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #330 | Degrade gracefully for search fields on non-AJAX capable browsers | OpenMRS Code Base | OpenMRS 1.3 | enhancement | 02/16/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Our web interface should take advantage of AJAX, but not be completely dependent on it. The first step in this process would be to adjust the generic search widgets so that, when JavaScript is not available, they submit the current page to itself with the search string within the URL and the same widget would render the results for any search in the URL as a default. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #251 | Change patient merge so patient data is voided instead of simply switched | OpenMRS Code Base | OpenMRS 1.3 | task | 11/15/06 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
When merging patients, instead of switching patient_id within encounters, obs, etc, we should probably void these records and create copies with the "winning" patient_id so we have an audit trail of the merge. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #594 | Strange characters in a concept description can break the design schema | OpenMRS Code Base | task | 01/31/08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The symptom was that a form worked fine -- concepts added, schema built, infopath form created, and the form could be used for data entry. The problem seemed to be that the design schema would not appear -- it would say "Loading", but it would never load. Firebug did not catch any problems, and the forms appeared fine. It turns out that one of the concepts used on that form had a description with a line feed (showing as \r\\n). By editing this weird character, the schema design works fine now for that form. fieldName: \"SPUTUM SPECIMEN\", description: \"Was a sputum specimen collected?\r\\nMatter coughed up and usually ejected from the mouth, including.....etc. I am working in Peru, and perhaps it's that the Spanish keyboard puts in different characters. Darius mentioned that he can help with this. Our friends in Lima would like to include all the "normal" Spanish keystrokes, and that should be possible, right? |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #813 | Garbled OpenMRS Website Displayed in Internet Explorer (IE) | Wiki | task | 06/17/08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
In Microsoft Internet Explorer (IE) the OpenMRS website appears garbled, missing part of the first characters on the left side, among other display formating errors. See the attached image. The website appears fine in Mozilla Firefox. As a first impression of OpenMRS, the www.openmrs.org should work with all popular web browsers. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
callen
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #328 | Can't create a PatientFilter from reportObject.form | OpenMRS Code Base | task | 02/14/07 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
When I go to this page to create a new patient filter, the "choose an element type" list is empty. admin/reports/reportObject.form I'm marking this a trivial because the cohort builder will probably save people from having to create filters in this way. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
catullus
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #778 | Audit Patient Identifiers function should be more flexible and ask for confirmation | OpenMRS Code Base | defect | 05/25/08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The 'audit patient identifiers' tool should not actually make changes without asking you for confirmation. In addition it should be more flexible and let you pick what type of identifier you are auditing, and which type you want to change it to if it fails validation. Brian, Ada, does AMPATH ever use this feature? Or is it a blast from the past? |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ddejager
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #231 | Create Custom Izpack Panel to Install Tomcat and Mysql | Installer | Installer 2.0 | enhancement | 09/22/06 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #232 | Add linux support | Installer | Installer 2.0 | enhancement | 09/22/06 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #233 | Add Mac support | Installer | Installer 2.0 | enhancement | 09/22/06 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
djazayeri
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #332 | Cannot void patients from Patient Form | OpenMRS Code Base | defect | 02/20/07 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
When trying to void a patient in Patient Form, receive ConstraintViolationException. Stack trace: An Internal Error has Occured org.springframework.dao.DataIntegrityViolationException Could not execute JDBC batch update; nested exception is org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update Consult the help document. Contact your friendly neighborhood administrator if it cannot be resolved. Hide stack trace org.springframework.dao.DataIntegrityViolationException: Could not execute JDBC batch update; nested exception is org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update Caused by: org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:71) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:249) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:235) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:144) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106) at org.springframework.orm.hibernate3.HibernateTransactionManager.doCommit(HibernateTransactionManager.java:558) at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:540) at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:510) at org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:310) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:117) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:209) at $Proxy44.deletePatient(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:318) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:198) at $Proxy42.deletePatient(Unknown Source) at org.openmrs.web.controller.patient.PatientFormController.onSubmit(PatientFormController.java:347) at org.springframework.web.servlet.mvc.SimpleFormController.processFormSubmission(SimpleFormController.java:258) at org.openmrs.web.controller.patient.PatientFormController.processFormSubmission(PatientFormController.java:323) at org.springframework.web.servlet.mvc.AbstractFormController.handleRequestInternal(AbstractFormController.java:250) at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153) at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:45) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:806) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:736) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:396) at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:360) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.openmrs.web.OpenmrsFilter.doFilter(OpenmrsFilter.java:70) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:174) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:77) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) Caused by: java.sql.BatchUpdateException: Cannot delete or update a parent row: a foreign key constraint fails (openmrs/encounter, CONSTRAINT encounter_patient FOREIGN KEY (patient_id) REFERENCES patient (patient_id)) at com.mysql.jdbc.ServerPreparedStatement.executeBatch(ServerPreparedStatement.java:642) at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723) at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:48) at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:242) ... 55 more Version: 1.0.52 Build 1457 Database Version: 1.0.52 Cookies: dashboardTab-1128=[patientDemographicsTab] JSESSIONID=[EFDEBDD8A4FD75DE88A31F6BD54CEE42] |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #719 | Encounter Obs don't match in Edit and View screens | OpenMRS Code Base | OpenMRS 1.3 | defect | 05/01/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
After a form is entered and submitted successfully, the encounter obs in edit screen are different from what are shown in the view screen. E.g. When the field is a multi, the multiple obs are shown correctly in the Edit screen but the last ob is shown in the View screen. Opposite problem is happened for other concepts which are multi (i.e. all multiple obs are shown correctly in the View screen but the last ob is shown in the Edit screen). Please see attachment for details. Thanks! --Ada |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #286 | Allow for update/delete of observations through HL7 | HL7 | OpenMRS 1.3 | enhancement | 01/25/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Add support for OBR-25 (HL7 2.5 manual: 7.4.1.25) and OBX-11 (HL7 2.5 manual: 7.4.2.11) in ORU-R01 messages to change (status = "C") or void (status = "D" or "W") existing observations. Ideally, we would support/consider filler + filler order number and/or accession numbers. As a first pass, the HL7 handler for ORU-R01 messages should check the order status on OBR and OBX components. If an OBR is flagged as changed, each OBX within that OBR should be checked and changed if it already exists. If an OBX is flagged as changed, then only that OBX needs to be checked. If an observation status is "changed" but an existing (matching) observation is not found in the database, then the observation should be added as a new observation. Requests to void observations that are not found in the database should be silently ignored. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #311 | Allow sorting/filtering of patients by Patient Address component | Reporting API | enhancement | 02/07/07 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Need to be able to select/display/report on a cohort of patients that have been selected based on a subcomponent of their address. For example: if you want to see data about all patients from a certain village, or district, or province. Darius, I'm giving this to you since you are working on cohort builder. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #651 | Patient dashboard and Graphs should modify layout for multiple measurements | OpenMRS Code Base | task | 03/14/08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
For a patient with lots of weights and CD4 tests (dependent on fonts, screen size, and number of measurements), the Graphs tab on the patient dashboard cannot fit the all the measurements without adding a scrollbar. The graphs are centered on the page, but with the addition of the measurements and scrollbar, the graphs no longer appear centered on the page. For an example, see this patient: http://demo.pih-emr.org:8080/openmrs/patientDashboard.form?patientId=14128 PS - Happy to provide a login to this machine if the "assignee" wants access. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #977 | Remove nealreporting from core | OpenMRS Code Base | OpenMRS 1.4 | task | 08/15/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Now that module support is well established, nealreporting should be removed from the core code. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #529 | form inport/export auto-rebuild xsn enhancement | OpenMRS Code Base | enhancement | 01/03/08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
It'd be really great if the form import tool could automatically rebuild the form that it imports so that the user does not have to remember to do this (as it's a non-intuitive step). Alternatively, as a temporary fix, just a reminder to do this with the import confirmation would be good enough. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
eray
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #499 | Make Calendar Popup Format Dates with Letters | OpenMRS Code Base | OpenMRS Someday | task | 12/20/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The calendar should be able to handle dates with the format dd-MMM-yyyy. See the email thread: https://listserv.iupui.edu/cgi-bin/wa-iupui.exe?A2=ind0712&L=openmrs-devel-l&T=0&O=D&P=11081 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
jegg
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #973 | Patient matching module not up-to-date | Patient Matching Module | OpenMRS 1.4 | task | 08/12/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The Patient Matching Module V1.1.3 has a problem installing on the latest OpenMRS (1.4.0). Since the OpenMRS repository module hasn't been updated since December 2007, perhaps it doesn't work with the API refactoring code? Is there a newer version of the module? Could you please fix? |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
jmiranda
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #916 | Report generation not handling date columns correctly (possible parsing error) | BIRT Report Module | defect | 07/17/08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Email from Jeremy Keeton (jkeeton@pih.org) @ 7/16/2008 3:02 AM EDT ===== BEGIN email snippet I think I’ve figured out what’s going on here. I did the following: 1. I generated the first PDF called “bobete_emr.pdf” directly from the emr 2. I downloaded the report design and the dataset directly from the server and opened them up in the BIRT RCP designer 3. I setup the dataset without editing the datatypes under “Select the file and columns for the dataset” and generated “bobete_wo_datatypes.pdf” 4. Lastly I setup the dataset and edited the datatypes (only the ones that were dates) and generated “bobete_w_datatypes.pdf” –THIS generated the correct report with the correct numbers. So it looks like somehow BIRT in OpenMRS doesn’t know that the following report params are dates: Any of the report params with the word date, obs_datetime and the column Earliest ARV start So when it does a comparison against these dates (i.e. “DateTimeSpan.years(dataSetRowBirthdate?,paramsReport End Date? )>14”) it sees “Birthdate” as a string and counts ‘0’ patients. One other note, there was a warning in the catalina.log file for every patient that says “There exists an error in toDate method” Unparsable date: “2007-08-16”. I’ve attached a sample, I couldn’t attach the whole log file because for some reason it was 760MB after running this, so I'm guessing this means there was a very long error for every patient. ===== END email snippet |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #432 | Upgrade BIRT Report Module to the latest version of the OpenMRS API | BIRT Report Module | enhancement | 08/11/07 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The OpenMRS Report API was recently updated to fix the "identifier of an instance of 'class' was altered from X to Y". The BIRT Report Module requires this API upgrade in order to prevent this error from occurring during the Create Report use case. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #917 | BIRT throws "Cross-table query is not supported" error during report generation | BIRT Report Module | defect | 07/17/08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Email from Seid Hussein (seid_hussein@YAHOO.COM) @ 6/6/2008 2:24 AM EDT ===== BEGIN email snippet I was generating a report using BIRT module. Though I have checked there is nothing wrong in the data export, which works fine while I used it to design the report in BIRT, when I import it to the BIRT Reporting Module in OpenMRS, it is giving me error while I generate the report. I can create the report and link it with the Data Export. The problem is when I generate the report. It gives me the error:
What does it mean. And if I made a mistake in any step of designing the report, please tell me. I have attached the whole error below. I am using the build on Apr 24 2008 02:31 AM Version: 1.2.04 Build 4010 Database Version: 1.2.04 Failed to prepare the following query for the data set type org.eclipse.datatools.connectivity.oda.flatfile.dataSet. [select "Skin rash this month", "Neuropathy side effect this month", "Anemia side effect this month", "Pancreatitis this month", "Lipodystrophy this month", "TB this month", "Candidiasis this month", "Diarrhea this month", "Cryptococcal meningitis", "PCP this month", "Herpes zoster this month", "Genital herpes this month", "Toxoplasmosis this month", "Recurrent respiratory infection this month", "MAC this month" from Monthly_report_--_NGO_and_PLHA_involvement,_Staffing_Details,_Side_Effects_and_Opportunistic_Infections_en_us-2008-06-06-124358+0530.csv] Cross-table query is not supported. ===== END email snipper |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #356 | Move passwords from global properties into runtime properties file | Scheduler | Scheduler 1.0 | enhancement | 04/03/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
We need to figure out a way to handle encryption/decryption of passwords in the global properties table. The scheduler component (org.openmrs.scheduler) requires a username/password, so that its scheduled tasks can make calls to the service layer. Originally, the username and password for the scheduler component was declared in a constants file (SchedulerConstants). For security reasons, we decided to remove the password from the source code and move it into the global properties table in the database. The password is still in cleartext (in the database) and therefore poses a security risk. We would like to figure out a general scheme for encrypting passwords like these in the database. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #469 | Create tool to be able to export data by form | Form Data Export Module | enhancement | 10/10/07 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Create a module that allows administrators to export data based on a given form. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #470 | Allow user to select patients for form data export tool | Form Data Export Module | enhancement | 10/10/07 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Add support to the form data export tool to allow users to select a pre-defined cohort. The cohort will be used to restrict the rows in the export -- only patients in the cohort will have rows in the export. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #551 | Add better error handling to BIRT Report Module | BIRT Report Module | enhancement | 01/11/08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Currently the BIRT report module displays a blank PDF (or HTML/Excel file) when an error occurs. The BIRT report task interface exposes an getErrors() method that will allow us to get any errors that have occurred during the processing of the task. In addition, we can set the BIRT Report Engine to either Continue or Stop on errors. I'm going to test these approaches and figure out which one makes more sense. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #554 | Improve parameter support in BIRT Report Module | BIRT Report Module | enhancement | 01/11/08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The BIRT Report Module now handles simple parameters (string, int, date, datetime) as well as complex parameter (select lists). However, the more complex parameter types have not been tested thoroughly. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #556 | Upgrade BIRT Report Module to BIRT Report Engine 2.2.2 | BIRT Report Module | enhancement | 01/11/08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This enhancement includes the following tasks:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #581 | Allow BIRT Module to be deployed as two separate modules | BIRT Report Module | enhancement | 01/15/08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The BIRT Report Module is rather large, weighing in at around 10MB. The majority of that comes in the form of JARs required by the BIRT Report Engine. These JARs should be deployed as a separate module (i.e. birt-engine-2_2_0.omod) so that the BIRT integration code can be deployed more easily as another module (birt-report-2_2_0.omod). This is important for implementation in remote locations like Rwanda and Malawi. This will require changes to the BIRT Report Module build.xml to create multiple omods from the same code base. In addition, this may also require a change to the module code to allow modules to specify which module version they depend on. Right now, I believe, you can only specify which module dependency, not fine-grained module version dependencies. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #401 | Add user-defined support to data export utiltiy | Reporting API | task | 06/05/07 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The current version of the data export utility only supports tab-delimited exports. I added a method to the utility to allow users to specify their preferred separator (i.e comma, pipe, tab, etc). This feature needs to be propagated to the web interface so that the user can specify the preferred delimiter used for exports. It is currently only used internally by the BIRT report module to export CSV data files. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #490 | Convert between String and LogicCriteria | OpenMRS Code Base | Core Reporting Framework 1.0 | task | 12/06/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Build the functionality that will allow us to convert between String and LogicCriteria, based on a very limited vocabulary. Also encapsulate this within org.openmrs.propertyeditor.LogicCriteriaEditor. The minimal vocabulary should be able to handle something like this: [CD4 COUNT] @LAST @LT(350) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #423 | ClassNotFoundException (org.openmrs.module.birt.BirtReport) on session loading during Tomcat startup | Module Engine | defect | 07/10/07 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
When Tomcat is started, it tries to load objects that were persisted during the last Tomcat shutdown. Objects that were stored in the session during runtime are persisted to the file system when Tomcat stops executing. Objects created by OpenMRS modules are sometimes stored in the session, which means they need to be available when OpenMRS classes are loaded into the classloader (i.e. during Tomcat startup). However, these module classes are not loaded into the classloader until after the OpenMRS starts up. Therefore, Tomcat cannot load these module objects into the session during startup. Possible solutions: 1. Disable Tomcat's default session persistence / loading mechanism by override the OpenMRS webapp's context.xml 2. Figure out a way to load all classes (from code API, web, modules) at once ERROR - StandardManager.doLoad(400) |2007-04-17 16:51:34,539| ClassNotFoundException while loading persisted sessions: java.lang.ClassNotFoundException: org.openmrs.module.birt.BirtReport java.lang.ClassNotFoundException: org.openmrs.module.birt.BirtReport
ERROR - StandardManager.start(638) |2007-04-17 16:51:34,569| Exception loading sessions from persistent storage java.lang.ClassNotFoundException: org.openmrs.module.birt.BirtReport
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #516 | Patient search needs 3 characters | OpenMRS Code Base | defect | 01/02/08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Patient search says it requires two characters to search but doesn't find my patient with 2 characters... It can only find the patient when I enter 3 characters. Probably should find it when enter 2 characters. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #358 | Add extension point to Scheduler interface | Scheduler | enhancement | 04/05/07 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Add an extension point to the Scheduler interface to allow custom scheduler modules to override functionality of the TimerSchedulerService. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #359 | Implement module that interfaces with the Quartz scheduler | Scheduler | enhancement | 04/05/07 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Given that our current scheduling framework (and the JDK Timer) does not support advanced scheduling features (like cron), we need a more powerful tool. I've evaluated Quartz in the past and would like to create a module that interfaces with the Quartz scheduler. See http://www.opensymphony.com/quartz/ for details about the scheduling features provided by Quartz. Let me know if there are scheduling features that you think should be supported within OpenMRS or within a module outside of OpenMRS. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #467 | Add page specific titles to all JSPs | Customization | enhancement | 10/03/07 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Currently, we use openmrs.title from message.properties for all pages in the application. We should add a mechanism for specifying a page title for any page. The page title should be pulled from message.properties. If a page title does not exist for a given page, we should default to openmrs.title. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #869 | Adding task with no details of task allows you to save and get an exception | Scheduler | OpenMRS 1.4 | defect | 06/23/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Under Manager Scheduler, when adding a task and you click the save button without entering any detail should not throw a "ConstraintViolationException" exception. It should rather tell the user to enter mandatory fields before clicking the "save" button. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
pbiondich
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #78 | drug.drug_id auto_increment | Data Model | Data Model 1.1 | defect | 04/11/06 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
drug.drug_id needs to be set to auto_increment. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
pboucher
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #519 | Dead in the future? | OpenMRS Lite | OpenMRS Lite Release Candidate | defect | 01/02/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
ART Encounter Form Basic 002 I was able to enter a date of death and lost to follow-up dates in the future... Both dates on same form at the same time... should be one or the other only. There is also a title for Transferred out but not possible to enter a date here. Why have the title when no entry possible? Should have some error checking here. Also, the three ? buttons to the right of these fields do not do anything. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #521 | ART Encounter Basic 00002 bottom section | OpenMRS Lite | OpenMRS Lite Release Candidate | defect | 01/02/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
ART Encounter (Basic) Form 0002 - Bottom section Patient is male... should hide the Pregnant due date title. What are units for weight and height? '?' Buttons on right don't do anything. I was able to enter both a substitution and a switch on same patient... should be one or the other. Also, only enter something here if a change... Form should display current regimen as default and hide switch and change fields. Only show them if make a change. CD4 Count and/or percent? Both? Encounter date shouldn't be allowed to be in the future. (Should default to today's date). Form submitted successfully. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
r0bby
| Ticket | Summary | Component | Milestone | Type | Created | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #930 | CLI/GUI front-end to deploy omods | Module Engine | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||