Hi Lara, Just a quick one. When the order results have been entered for a specific patient is this removed from the order list?
Thanks Erick On Mon, Sep 26, 2011 at 10:53 AM, Lara Kellett <[email protected]> wrote: > Hi Eric, > > For your first question, the Simple Lab entry module was designed around > the workflow of the lab technicians here, therefore there is only the > dashboard screens to enter orders and enter results and these are all based > on the dates the samples were taken. There isn't a way to view specific > patients lab results from the lab entry dash board as these can be viewed > from the individual Patients Dashboard. You should be able to see on the > encounters tab of the patient dashboard which results are the lab entries > and when they were taken from a patient. So we just use the graphing and > patient dashboard to track the result for individual patients. > > For the second question, this is the ID that is used by the lab (so I > believe it can be in any format that is used by the lab). Because of power > and network issues we can't guarantee 100% up time of our EMR system. > Therefore the lab still maintains a paper register of tests, which is then > entered into the EMR by a data entry clerk. So for us this is the id that is > recorded against the lab entry register, so this allows us to go back to the > paper records if there is any concern about data entry error for a > particular test. > > Hope that makes sense, > > Lara > ________________________________________ > From: Erick Mugoma [[email protected]] > Sent: Monday, September 26, 2011 9:23 AM > To: Lara Kellett > Subject: Re: [OPENMRS-DEV] Simple Lab Entry-How to set it up > > Hi Lara, > Thanks very much for your candid guidance, so far am having some positive > results and am about to start testing with some few test entries. I've some > few questions that I need further clarifications: > 1. How do I view a specific patient's Lab results from the lab entry dash > board without running the weekly report > 2. Is the lab ID supposed to be a sequential number or how should this > number generated? I suppose this number should be unique for each order. > > I'll still get back to you as more questions arise. > > Thanks > > Erick > > > On Sun, Sep 25, 2011 at 11:48 PM, Lara Kellett <[email protected]<mailto: > [email protected]>> wrote: > Hi Erick, > > Firstly my apologies, just realised I am getting confused with names and > thought you were one of the programmers working here in Rwanda, therefore on > a very similar system and more importantly on a concept dictionary based on > ours. > > So let me give you some more general information about the global > properties. > > 1. Patient Health center attribute type - we use health centers as a way to > identify locations for patients, the health center is saves as a patient > attribute against the patient, this global property is the id of the patient > attribute type used to determine the location of the patient > 2. Program to display - historically this module was developed for the > needs of the work partners in health was doing with HIV and has always been > based on program enrollment to track active patients being treated, so this > is the id of the program for the HIV program. > 3. Work flow to display - on the enter results screen their is a column > displaying group, we use this column to display the treatment group for a > patient as all our HIV patients are enrolled in treatment groups which are > controlled with program workflow states. This global property is the name of > the workflow that is used to hold the treatment group. > 4. supported tests - the lab entry module allows you to group test results > based on the tests being run. For example on our Rwanda system if a patient > is sent for Biochemistry Lab Panel, a series of 4 test will be run against > it. Therefore this global property contains the concept ids which relate to > the top level groups of tests. These concepts can be set up as labSets and > contain all the tests which should be entered against that lab panel, or as > individual tests. > 5. concepts In LabSets That Are Not Tests - this excludes concepts that may > be in the sets above but aren't tests. > 6. labOrderType - the simple lab entry module works by creating orders for > each lab test, the benefit of doing this is you can track when a test order > is created and also when it is completed (ie when the lab results are > entered). So this is the order type the lab order should be created against. > 7. labReportConcepts - these are all the lab tests that the lab module > should report about (generally this will be all the lab tests contained > within the sets for the supported tests global property) > > Unfortunately I can't see the print screen attached, I am viewing these > emails via Outlook Web Access and it has converted the image to Hex numbers. > I have just tried this out on my dev box though and can see the error thrown > if a program is not entered. I am not 100% familiar with the code for this > module, however I believe the only reason the Program is required is to show > the treatment group, so I wouldn't think it wouldn't take too much work to > remove this requirement. So what I would suggest is if you have a dev or > test environment available, create yourself a program (it just needs to be > a valid program within the system, there is no restriction about the > patients being enrolled in the program etc), the Workflow to display field > can't be left blank but can contain an invalid value (for example "test") > and see if the functionality of the rest of the module meets your > requirements, so you can make a judgement as to whether it is worth changing > the module to be a little more general. > > Thanks, > > Lara > ________________________________________ > From: Erick Mugoma [[email protected]<mailto:[email protected] > >] > Sent: Sunday, September 25, 2011 9:21 PM > To: Lara Kellett > Subject: Re: [OPENMRS-DEV] Simple Lab Entry-How to set it up > > Hi Lara, > Thanks very much for offering to bring me up to speed with Lab Entry > module. May be let me take time to let you know how we use openmrs so the > you can help me better. > > We use OpenMRS to keep the patient encounters only. our current instance of > openmrs has no specific programs or workflows that have been defined. > We have an infopath form that we use to capture the patient lab tests and > results (this method has its own shortcomings). > we want that all lab test orders and results are captured directly from the > lab and we can pull the reports directly from openmrs. Am trying to test if > the lab module will help us capture and pull reports directly from openmrs. > > Is there a way we can use the Lab module without having program or > workflows defined? > > Meanwhile I did try to follow ur guidelines on how to setup the global > properties but it is still not working. see the print screen > > [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAjgAAAFHCAIAAAAji6EoAAAgAElEQVR4nOzdd1wb9/0/8Ev6TfrtbtokbdNfmqZNmiZps79pZtssO068Nx6AsbEBsbfY0+w9JfaQQAux9957gwAJEENMgfa6k/T+/QGOwWkS24ljN7nn4/MHEncffe6ju3vd5wYggMPhcDjcPQy52w3A4XA4HO7L4EGFw+FwuHsaHlQ4HA6Hu6fhQYXD4XC4exoeVDgcDoe7p+FBhcPhcLh7Gh5UOBwOh7unffNBhalVq0KJSIF+4zV/lygUCrVafbdbcbNkMplWq73brfi6NBqNQqG42634DlKr1XjHfpvUarVSqbzbrfhW3WRQ6cf6exMz66pGVr9y0sFyxs/+bnowtvOLJ8F6u3oT8+qic6tDsipD0srCCwbWNF84tWhhJpFSy+pZvLmm/mcr0xNRaeUhWZUh6RVZHfO3OLe2v7snkdIysPSNbY3x8fHl5eXfVG13mru7+9TU1N1uxddVWVkZGxt7t1vxHVRWVpaQkHC3W/E9UlxcnJycfLdb8a26yaDSxXi7IQ8e/Ti0/Ssn7S3MRR43eO/LplS42rsivzrxwLv2T+wnPrHH/mnTXI5c/0VTLzSxkV8f+Ltn48019XO0aHFOzp/+YfrAW3ZP7Cc+/q8ryFOXnYt5t1RHiJsb8suLYZ2i22zD54SFhRUWFt7EhHrB8tqaAvvsNaqQ8ZZFtzG60arkvKUN9Au7+cvY2dlxOJzbmfPOE61vLG7c1NFlcXFxSEjInW7P1yFcX18Qq257drlcuiD+xobponXhTXYsm80ODw+/6Yp1i/z5vlkhdlur4rdPtCqobx1uH57tGJnhrX2jA0etZnxiund6/VbPPjGZzJiYmG+yJbdLp1HwBRsq3fZLuVg0tyq7E1/szQYVKTgA+a3RibjuHW+q2AUlJi4p5zzTLnhlhZVytta8vmIq8mejD4PLcnMKjZxTPLPbhTc2XOnn4Y38xjy4ZX3nuzP9XTaBlKSW8aK8EmPnFK/sXjmAZmXGwpKIPG/y8MGAc+7ZjNHNuf42m8C89Lax/BSacVwtlVlq6ZdH7V4GAACsnM6yCmRUTcs+q3ZjouupZw/f/8/gDsn2pyclZ/lQx9oaqgleuWktW6MrfX1hkZV/fhFHCqBrKqu95Eo+55563iOrcFwy0Vn38j5z5O/mL5tEnQsvn5QCAPQ0NVxwJZ1zSw8uHN9avonuNptAakrrGDObfYmYEVbFVcrl1GzaJWJqVOUEBrtERkYWFxfvfGdhrNc2pGhMcmNnBYQlJPQIP3sp53QcDWLsnkrf3dDsEpHnGlFA7RT85y8QQD83eMyfsvTFI9cv4ejoODExsfWzen0xMpHqEl3gGsMgJteMi7Abp1ZtFnRyPvfuF+pvbnQIo7lG0v0Zg8pbX8cLSFludK5yY5E9vPTlU5aWlu7Yn6po6QWpHVvDdEVGbmFE1cwtf/ZN0yo2UlNZruH5Dkn1XMkXHmbQsjIcim77gECdlUbLHJJ+9rqnqcExjO4aSQ9gDqluvWMZSZkerGnF+gJ7ePnLpywqKoqKirr2SlfFLrSJaxR84VIqiCbWyLks+X/63drUsGNYrmM0yzWO5RrBLh1b//w0qpUZ13BaGf/WVmXt6qxHZJ5LFNM5OMe3eEx7cx2CLo39336XCzFVTFrB7z+0tqBN3NKH/key+UmHcEbDCgBsHDe0+5sTW/iV8+xWUFAQFxe39fPMYH9G7fV1prOpg9bKae/gLCpu4StfGBuiNc7oAQA0LHZZSucyAIBaSGE0Dm982YzS2X4Tj1zOte+yt5hpGtX6RRPrNgVRZLprJN0psqSOJ7n55sHXCirdhvEF4lOnwg/Yxb/0sSXy+IWL2YMAMFiah/zV6MlzUeec4l/4iIA8fvKD0MbdOyCln4cP8rjpwcDijJL2jIImdu+8HqAlNxl59NAP9/obuSS88JEF8qixFWtKs8Y7Z2yH/O3iL/a4f3AlLq1vvTY1CvnNsceN487bRO4PraDnZCO/2PeEXaEKAEQTf3/5JPJGQKvw+n5ybaztyWdPIC9amyTV0Ss7mZ0zAAB6/UAlDfn5x7+6RN0EABX/3XfOIi96Na/JqZFx//u80TPnog7Yxu05Tnzbraa9seLZ902RF8yeOub7gRtjUo4Wp5F+8crlly7FHbjgiTxrciS2TQNQnRqDPHrkVyfCDZ3if/uqEfK61VFi7kWH6N+/chZ50T5tcNdo7HNBpUgMT3z2iF9gNX/7Da28rKqZRKv+1CJ8a961mQkyoyEkjPwv/+Kd+51mNv0DF1oLZ25waIzgEBfbsQI6zcT0wuDQKJndtagB+dI0mdEQFZ3+tgdjUwegV1VXN5DyWofX1ADAm10YHZ9KY7VOSjWCyQlyXh2Z2dY1J93Rtl1BJRxue9sorIK7yp1b5S5syFD99Oxca99YbkEtpW0OAObaql4yCvbLbmANLAPAWG83KbeuanQVANYEgnHeHKuksWx45Vrd2riQOCNy5+DEnIdbrHX+8NabrY0tJEpTx1YzVBssViOJ1kBtnUX16OjY9KJUBwCz/HnuhrIqK8+PPlZCz33ZLJnEau0QKAEVMVmNJHoDtXV25/hiV1DpNs0NLX9nQt3Ugmp29Nk3zr0R1g56TUN9Czm/PrtmUgUASmnX6HRDUweJ1jawrAIAAZeTwqgj57cPLm8NNXSdbZ0kWkNGcc/WaWHJ4gyZVpNRw5Ht+Fy9cs3ePdout3eQM1fELDruTuMpQbW5Ns6br6xupXXMA0BXWweJ1mBsF+ZcNg0A4gUeOb8mq5ajBNBKhGO8habmrsy6KRWo68tbSbT61Orxjd3H4dq1CZ/kWuH1eMAig2JN0roHJ/huxBh7+ujWVC0NzSRKU9e8DAD0CiGT1UiiNeS18VE9Ojo6LZDpAGBmdp63qSrPoAYwxwvzs182I5FYbV1LKtBsMpiNJHpDXtvszpTYHVRa4hUz5KWgvmtdL1leoLDqSczGzPIhgRIA1O6m9j++kNXQ1ZdK6xhY3DVGGa+gII9dcCwa586vcvmrq1LNxgKfXj/SN8bNKWwq7FzUAVaWSkKeOPUPIrtyan2Fx6W1TAyOjFNrhquau1ktM2oAvVxUXNXRNHt9V7jJ7X33A7NXHAp6JhZaK6s/sQyvXgIAbVNLFzmvjtI8qQEA0I31DRV0Tff2DqTTO/oWlYBKEwMDkBftHPMGpuYWsmmVJaNCAOCPD6czG8mFrXkVAxMbao1ohVHVOyLEQCUpq+1q50v1anF5fV/LGL+0trtjRtjX0UOiN6awWmrGNwBQekws8sSZ93zL6ycX66saSdXjGgDQbOaXNpPy6qq2shmVNzT11g7PNTa1ZxcOzst3HfjtDKpNbvchq9SBraMfbN3WOTGza6a6pn9eA6ARs0vqSIzOWQWg60u1Q4t6gBU+f3RJDoD1j/DmpNvVLvbWfmSWydcCKJeO7jd+2rNZB6Ca7PrYNmNKDaASFRTXkZhd01IdAOgka3nsGnJh3xIK6MLQJU/KrBb0m4uMtolqVpFTYvMIZ25cqAYA2dpiU9/CZ02XT3R+YJlUNTHfVlO9zzKtS6QDAKlgJoVWk149LgcA+WbHCK+2vpVE7+Rsr9/bg7WvM6LCBMuSNbl8TSjpKC742V+O/pzA0gOMlOUjfzq/N6oLAIDf+6d/nEXeDe/ZNRxU+nn4I09f+NE7Nr96z+5X/7jypk+FFqCHmYE8debd0A4AmGsq/dEf9v/JqVgPsNZRhjx15p2g7aAuJsUgTxufp187dydb+PTAJeRNv3Yp8GtZyBPHDyT172o7ps5NTH78zUvIoweQh/YjT118zSKtYloN6vWzpyyQl90rV/VrXRU/+NPRf0f2Amwc/ugi8nuj0wldqyLZ8tzy4JwIAOICApA/2cT2iABAzu/7698Mfn0ypUcgXZsfefdfRsjrwaMotOeRkT+fP5gyCgClqSTkoWPH0wYBoJoch/zp7InssZ2NuiGoFNO9hr7FPQNtp9xpy1oAvYISn3MlsZJS0nbUOjJ7QqmZHbFwS4stbU+Oz/] > Thanks > > Erick > > On Sun, Sep 25, 2011 at 12:18 PM, Lara Kellett <[email protected]<mailto: > [email protected]><mailto:[email protected]<mailto:[email protected]>>> > wrote: > Hi Eric, > > The Simple Lab Entry module is currently in use in Rwinkwavu, Kirehe and > Butaro so Peter, Dave and Myself will be able to give you any help you need > getting it set up an using the simple lab entry module. > > In relation to the global properties you are asking about > > 1. Patient Health center attribute type - this is the person attribute type > that is used to store the health center for a patient (probably 7 in your > system) > 2. Program to display - as this main use for this module originally was > recording CD4 counts we display the patient groups for each of the patient > rows. Currently in the IMB openmrs we store the treatment of a group using > program workflows so this global property is used to represent the Adult HIV > Program ID. > 3. Workflow to display - this is the workflow name that is used to store > the treatment group, so in our case we using TREATMENT GROUP, but given you > are not using workflows to record treatment groups you will need to supply > the name of one of the other workflows attached to the HIV program. > 4. supported tests - these are the different category of tests supported. > The system is set up so that the test results are grouped, for instance we > have a Biochemistry Panel, CD 4 Panel, Hematology Panel and Viral load > panel. So these are the top level concepts for the groups of results that > appear for each type of test, try 657,6168,6167,856 > 5. concepts In LabSets That Are Not Tests - these are any results that are > not strictly tests, like cd4% so try 730 > 6. labOrderType - this is the order type that lab orders should be recorded > against - in our system we use 4 which is a dedicated order type to > represent lab orders > 7. labReportConcepts - these are the concepts for the tests you are > recording results for in the module - given our concept dictionaries should > be somewhat in sync, try these values > 5497,730,653,654,790,1015,21,1017,678,3059,3060,952,1021,729,856 > > Let me know if you need any further clarification. > > Thanks, > > Lara > ________________________________________ > From: [email protected]<mailto:[email protected]><mailto:[email protected] > <mailto:[email protected]>> [[email protected]<mailto:[email protected]><mailto: > [email protected]<mailto:[email protected]>>] On Behalf Of Erick Mugoma [ > [email protected]<mailto:[email protected]><mailto: > [email protected]<mailto:[email protected]>>] > Sent: Sunday, September 25, 2011 9:22 AM > To: [email protected]<mailto: > [email protected]><mailto: > [email protected]<mailto: > [email protected]>> > Subject: Re: [OPENMRS-DEV] Simple Lab Entry-How to set it up > > Thanks Darius, > > Am referring to the following properties: > 1. Patient Health center attribute type > 2. Program to display > 3. Work flow to display > 4. supported tests > 5. concepts In LabSets That Are Not Tests > 6. labOrderType > 7. labReportConcepts > > - Erick > > On Sat, Sep 24, 2011 at 10:02 PM, Darius Jazayeri <[email protected] > <mailto:djazayeri%[email protected]><mailto:djazayeri%[email protected] > <mailto:djazayeri%[email protected]>><mailto:djazayeri%[email protected] > <mailto:djazayeri%[email protected]><mailto:djazayeri%[email protected] > <mailto:djazayeri%[email protected]>>>> wrote: > Hi Erick, > > Presumably you've seen this page<https://wiki.openmrs.org/x/JQO3> which > has very sparse documentation. > > Have you tried setting all the global properties mentioned there? I haven't > used the module, but if you ask for clarification on specific global > properties mentioned on that page, maybe I can help. > > -Darius > > On Sat, Sep 24, 2011 at 11:06 AM, Erick Mugoma <[email protected] > <mailto:[email protected]><mailto:[email protected]<mailto: > [email protected]>><mailto:[email protected]<mailto: > [email protected]><mailto:[email protected]<mailto: > [email protected]>>>> wrote: > Hi > Is there anyone using this module? I've downloaded this module and > successfully installed on my openMRS instance, unfortunately there are no > clear instructions on how to do configuration. I've also checked the wiki > pages and I can't get any clear instructions. > > Is there anyone using this module so that he bring me up to speed so that I > can set it up? > > Thanks > > Erick > ________________________________ > Click here to unsubscribe<mailto:[email protected]<mailto: > [email protected]><mailto:[email protected]<mailto: > [email protected]>>?body=SIGNOFF%20openmrs-devel-l> from OpenMRS > Developers' mailing list > > ________________________________ > Click here to unsubscribe<mailto:[email protected]<mailto: > [email protected]><mailto:[email protected]<mailto: > [email protected]>>?body=SIGNOFF%20openmrs-devel-l> from OpenMRS > Developers' mailing list > > ________________________________ > Click here to unsubscribe<mailto:[email protected]<mailto: > [email protected]><mailto:[email protected]<mailto: > [email protected]>>?body=SIGNOFF%20openmrs-devel-l> from OpenMRS > Developers' mailing list > > _________________________________________ > > To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to > [email protected]<mailto:[email protected]><mailto: > [email protected]<mailto:[email protected]>> with > "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. > > [mailto:[email protected]<mailto:[email protected] > ><mailto:[email protected]<mailto:[email protected] > >>?body=SIGNOFF%20openmrs-devel-l] > > _________________________________________ > > To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to > [email protected] with "SIGNOFF openmrs-devel-l" in the body > (not the subject) of your e-mail. > > [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l] > _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
