Hello Everyone,

It's the final week of GSoC 2013. And this week I was focused to scrub the code base, transfer repo's to OpenMRS github umbrella and improve documentation stuff for my project.

Here's the user documentation (User Guide) I have written for the patient narratives module.

Also I did a lil presentation about my project at this week's OpenMRS Developer Forum - Interns Final Presentation: http://notes.openmrs.org/Developers-Forum-2013-09-19

You can find more resources I used for that right here:

• Presentation Slides
• Video Demo
• User Guide

Code Repository: https://github.com/openmrs/openmrs-module-patientnarratives
Report Issues/Tickets: https://tickets.openmrs.org/browse/PNM

I would like to thank the OpenMRS community, especially my mentor Saptarshi Purkayastha, Daniel Kayiwa, Mark Goodrich, for the great help given at designing and developing the project.

And I must say it was an awesome learning experience, I gathered through this year's Google summer of Code. I had to learn various new technologies, namely: SpringAOP, DWR, WebRTC, Xuggler, HTML Form entry module, Xforms Module and lots of functions in OpenMRS framework (played with Concept dictionary, Observations, ComplexObs, Encounters, etc) 

One more point I wanna mention is, GSoC will be over from today, but its not the end of the development work for this module or contributing OpenMRS. I will be continuing my work and contribute OpenMRS even more next. Best is yet to come! :-)

Thank you very much Lord.Budhdha for always blessing me to get done this work properly! නමෝ බුද්ධාය.

~~~ GSoC 2013 is over ~~~

Hello Everyone,

Its the final week just before the firm pencils down date which will be starting from next Monday! I am really glad that I have been able to complete most of the essential end to end functionality of my project by today.

This week I was focusing on improving user experience (UX) and UI design.. So now the UI looks much simpler to follow and very responsive.

You can check out the latest DEMO (its a nice BETA release!) from below URL.
I have hosted it for you guys to check it out :-)

URL: http://54.235.163.128:8080/openmrs
Username: admin, password: Admin123

Starting from next week I will be focusing on improve documentation stuff for my project, and I will be presenting about my project at next Week's OpenMRS Developer Forum too!

Currently I am working on the WebRTC implementation to capture the video/audio media stream from the care seekers.
Thank you,
Harsha

Hi All,

I'm really glad to announce that, I have got completed the main end to end functionality as my mentor expected from me, before the mid term which gonna happen next week.

Features completed:

• HTML/X form entry submissions.
• Anonymous submissions.
• Care Provider Console (For Care providers: to review the received patient narratives--encounters)
• Module settings panel: (For admins: to switch X/HTML form as they wish and config the default patient used by the encounters and encounter type.)
• Captcha validation before form submissions.
• Initial WebRTC  integration.

And I have documented a brief user guide at wiki: https://wiki.openmrs.org/x/IAIzAw

And... Here are some screenshots :-)

Hi All,

The module work is going really well. I have finished embedding of the both Xforms and HTML forms into the module and now both allows to fill forms, gets saved properly and creates new encounters. Care seeker panel also have the basic functionality. In overall module works pretty well with Authenticated (logged in) users.

Currently I am focusing on the Anonymous submission stuff; Things seems like lil bit complicated than I expected since the other modules (X and HTML form entry modules) depends on some parameters which collects while authentication process. So currently I am trying to by-pass them using the Spring AOP advicer class (as daniel suggested) or if not using a deamon thread (as wyclif suggested)

I have hosted the current version of the Module at my EC2 server so you can check the progress of work:

URL: http://54.235.163.128:8080/openmrs
user name: admin
password: Admin123

Hi All,

Its the 4th week of GSoC, well just passed a big month of period after the GSoC coding start date! This week was a great week, So many improvements and development happened.

1. Created a Xform (customized for the patient narratives' collection) Of course I have created required concepts to map the observations used at Form.

I wanna Thank bunch for Daniel Kayiwa for the great help and guidance given for me from the very beginning of Xform integration till the end of Xforms creation process.

Final look after the Xform integration

2. The care provider console improvements.





3. HTML form entry integration -- I wanna thank Mark Goodrich for the valuable guidance given for me to get done things related to HTML forms integration in my custom module UI.

After getting things done, I have created a small guide including my learning’s related to this case: How to Embed HTML Form (generated by HTML Form Entry module) in a custom module


Look after the HTML form integration.

Hi All,

Its the end of the third week of gsoc and it was a busy week for me.
So much research and development happened this week. Since i haven't work with Concept dictionary , Encounters and Observations before, I had to read lot about them. Actually now I understand why OpenMRS is a very unique software amoung all other healthcare related software products, Its because of the wonderful *Concept-Dictionary* it made of and the extensible framework it has.

Currently I am working on to build a basic Care provider console which will show up all the encounters filtered by a particular encounter type.

If all goes well it should look like this :-)

Introduction

At the heart of every OpenMRS implementation is a concept dictionary that defines the medical concepts (questions and answers) used as the building blocks for forms, orders, clinical summaries, reports and almost every aspect of the data.  Most OpenMRS implementations have an open concept dictionary - one that is considered incomplete and evolves over time. Therefore, as clinicians document conditions, the OpenMRS concept dictionary must be expandable to accommodate meaningful clinical data.
What follows is an introduction to the Concept Dictionary, OpenMRS's unique foundation, and how it provides flexibility for the implementation.

Definitions

Concept Dictionary

The concept dictionary represents a fundamental building block of OpenMRS. Similar to a dictionary defining the function, meaning, and relationships of the words, the concept dictionary defines the name, code, and appropriate attributes for any observations or data collected (including medical tests, drugs, results, symptoms and conditions). To even further simplify the concept dictionary, one could compare it to an infinitely large Excel spreadsheet, where patients are represented as rows and concepts are represented by columns.

Concept

The concept is the basic element of flexibility in OpenMRS. Concepts are the individual data points collected from a population of patients. Concepts include both questions and answers.
For example, blood type data is collected for a patient.  The question is "What is the blood type for the patient?", with a set of discrete answers of "A, B, AB or O".  To implement this in OpenMRS with concepts, the question is a concept ("blood type") and each response ("A", "B", "AB" and "O") is also a concept.  For this one question, a total of 5 concepts are required.
What about a question where the answer is not a discrete answer?  If the question is "What is the name of your first pet?", the answer would be expressed in a text box.  It would not be possible to provide a complete list of every possible name for your pet.  In this example, there would be one concept -- "name of first pet".
The bottom line is, if you need a medical word within your electronic records system, it needs to be defined within the concept dictionary.  More detail about all the possible concepts in a later section.

Encounter

A single, specific interaction between the patient and a provider. An encounter can be any interaction and includes doctor visits, laboratory tests, food distribution, home visits, counselor appointments, etc. Encounters are typically represented as a form (consisting of hundreds of observations), but could also be a touch-screen patient registration or a single lab test for CD4.  For example, a patient visits a health center or hospital.  For each electronic form completed for that patient, a new encounter is created.  Each will have a unique encounter_id and encounter_type.  Forms could be completed by different departments (ie.  drug pickup, visit with an HIV clinician, Diabetes visit, food package received), and will have an associated encounter_type (ie. ART Drug Regimen Pickup, Adult intake, food assistance, lab test, etc).  Each encounter has an encounter type, date/time, location and provider.

Observations

Anything actively measured or observed during an encounter. As an example, patients' weights, heights, blood pressures, and BMIs are observations, as well as qualitative facts including the number of years a patient smoked, the activities in which the patient experiences shortness of breath, and finding on an X-ray. Although typically an observable question, demographics are an exception, and are recorded as separate concepts. Each observation has a unique obs_id.
These are possible scenarios for encounters and observations:

• One visit with one encounter without observations – Touch screen patient registration in Haiti
• One visit with one encounter with one observation – Touch screen patient registration in Rwinkwavu, Rwanda with weight recorded
• One visit with one encounter and many observations – HIV followup form
• One visit with multiple encounters and many observations – HIV followup form along with ART drug regimen pickup.  This would show 2 encounters, where each encounter would have a different encounter id and encounter type.

Demographics

Demographics are any descriptive characteristic of a person. This includes: name, address, date of birth, age, and any other social construct involvement.

So Glad to heard that I have been selected for "Google summer of code 2013" as a Student this year again, yeap for the second time! :-) This year it was very amazing and much more competitive than last year. To mention a lil wow fact: I have been selected for *two* open source organizations this time!! In-fact those are two great organizations:"Raxa" and "OpenMRS" both are related to Healthcare informatics. (Sometimes we need to take some crucial decisions in our life.) So finally I chose OpenMRS as my organization, because of my love towards this awesome open source community which I have been with over year now,
And ripen, I love this concept by now, "Write codes, Save lives!" I dont think we (as coders) can do much better work than this to serve the global healthcare informatics force. Saving human lives is a priority among all other alms-giving stuff. 

Lastly I wanna thank Lord Budhdha who were always blessed me to get through this big achievement! නමෝ බුද්ධාය.

Congratz everyone! Looking forward for a great summer with OpenMRS!

If you are interested, My Project details can be found here:
I will be developing a "User-driven healthcare" system by integrating OpenMRS-core as the base.

1) https://google-melange.appspot.com/gsoc/project/google/gsoc2013/durapix/118001
2) https://wiki.openmrs.org/display/projects/Patient+Narratives+Upload+-+Project+Proposal



Few Links:
OpenMRS GSoC 2013 students list: https://wiki.openmrs.org/display/RES/Summer+Of+Code+2013#SummerOfCode2013-Interns,Mentors,andProjects

GSoC 2013 Accept students at Google Melange web: https://google-melange.appspot.com/gsoc/projects/list/google/gsoc2013

OpenMRS Feedback Module - User guide Presentation: Targeting implementers usage Done by me @OpenMRS University Forum :)

Notes

• User friendly, Wizard driven Feedback Form
• Automated Screenshot Capture/Edit process within Web Browser.
• User-to-User Communication within Feedback System. (Comment System)

GSoC Project Progress Presentation

21th June 2012 @ OpenMRS Dev Forum

Reference links used in the Presentation - Feedback Module

Project Contents 

Demo of the work done so far (Hosted OpenMRS)

Username:  admin
Password:  Admin123

User Documentation

Waiting for changelog lock....
Waiting for changelog lock....
Waiting for changelog lock....
Waiting for changelog lock....
ERROR - Listener.contextInitialized(124) |2009-05-26 12:07:49,197| Got exception while starting up: 
javax.servlet.ServletException: java.lang.RuntimeException: error getting unrun updates on the database
 at org.openmrs.web.Listener.setupNeeded(Listener.java:144)

Solution.


REF : http://openmrs-mailing-list-archives.1560443.n2.nabble.com/Waiting-for-changelog-lock-td5166981.html

http://dev.openmrs.org/ticket/1524

OpenMRS has been designed to have a tiered architecture. The real strength of OpenMRS is in its robust and flexible data model. However, not all users want to have to know this data model inside and out. The ?API layer allows a developer to only have to know Java objects and read/save to them. This layer can be used in a standalone application or, as most people use it, in a J2EE web application.

Context

The backbone of OpenMRS is the core ?API. This API has methods for all of the basic functions like adding/updating a patient, adding/updating a concept, etc. These methods are provided in services. There are classes named PatientService, ConceptService, EncounterService, ObsService, etc. The Data Model groups the database tables into "domains." Each domain is a separate colored box. The breakdown of domains/tables is essentially a visual representation of the service separation.
The Context is a static class to allow the application to save on memory. Only one PatientService object, one ConceptService object, etc (and of course the associated DAO's) are instantiated. The Context's services are split into two categories: methods for the Services and for Users. The services are kept in the aptly named ServiceContext class. This is instantiated only once and is stored statically in the Context. The getter methods for the services simply pass through Context to the ServiceContext. The StaticContext properties are set via our Spring application Context and Dependency Injection. The UserContext contains methods for acting on users: authentication and authorization, logging in, logging out, etc. A different UserContext is instantiated for every user accessing the system. The "current" UserContext is stored on the current thread. When that user is done, the UserContext is taken off of the thread and put into the user's session variable (in the case of the webapp). When the user accesses the system again, the UserContext is taken off of the user's session and placed onto the thread again. In the webapp, this manipulation is done by the OpenmrsFilter class that wraps around every call to the server. Similar to the services, the methods on the Context class pass through to the current UserContext on the current thread.
Every access to the system must be defined within a "unit of work". This unit is bordered by calls to Context.openSession() and Context.closeSession(). In the webapp, these calls are done in OpenmrsFilter and most developers don't have to worry about making those calls. However, any developer of an external application or a thread spinoff (like Hl7InQueueProcessor and FormEntryProcessor) will need to be sure to include open/closeSession calls or risk leaking database connections.
Read more about the API

Spring DI and AOP

[PatientService], [ConceptService], etc are interfaces. [PatientServiceImpl], [ConceptServiceImpl], etc are the current default implementations of those interfaces. Which implementation Context serves up is determined by Spring's dependency injection. Each *Impl contains a reference to its DAO ([PatientDAO], [ConceptDAO], etc). The DAOs are also interfaces. The current default implementation of them are for Hibernate ([HibernatePatientDAO], [HibernateConceptDAO], etc). Which DAO implementation is used at runtime is also determined by Spring's DI.
All of these implementations are described in the Spring [applicationContext-services.xml] file. This file also controls the transaction and authorization AOP annotations (See next section).
Each *Service (not *DAO) is considered to be an AOP advice point. Because we instantiate and serve only one *Service class out of the Context, this is easy. When Spring starts, each service that has advice points around it gets wrapped with a Spring AOP class. If there are five modules/methods that wrap around a certain class, there will be five different wrappers. Any one of those could exit method execution early (if it's an "around" advice). Most AOP linking will be done by modules.
Also see OpenMRS AOP.

Authorization and Authentication

OpenMRS has a very granulated permissions system. Every action is associated with a [Privilege]. An action would be "Add Patient", "Update Patient", "Delete Patient", "Add Concept", "Update Concept", etc. A [Role] contains a collection of Privileges. A Role can also point to a list of inherited roles. The role inherits all privileges from that inherited role. In this way, hierarchies of roles are possible. A User contains only a collection of Roles, not Privileges.
AOP annotations are used to require a privilege for a service method.
The annotation is placed in the interface of the service. If the current user does not possess that privilege an APIAuthenticationException is thrown. (The webapp catches this exception and redirects to the login form). Each page in the webapp is able to require a certain privilege for the page with the openmrs:require taglib. The openmrs:hasPrivilege taglib provides support for restricting only certain sections of a page.
While using the API, you may come to a point where you need to temporarily grant the current user a certain privilege in order to make an API call. This is accomplished using the Context.addProxyPrivilege(String priv) and removeProxyPrivilege(String priv) methods. Multiple priv objects defining the same string can be proxied. Subsequent calls to removePrivilege will only pop the first one off the stack. Best practice says that you should put your API method calls in a try/catch block and put the removeProxyPrivilege call in a finally block.

Hibernate

Hibernate is an excellent Object Relational Mapper. Using just xml files, we are able to describe the relationship between all of our tables and our domain (POJO) objects (like Patient.java, Concept.java, etc). Looking at the concept domain in the datamodel, we see that it consists of tables named concept, concept_answer, concept_set, concept_name. It would be very difficult to keep up with where to store each part of the concept object and the relations between them. Using Hibernate, we only need to concern ourselves with the Concept object, not the tables behind the object. The concept.hbm.xml mapping file does the hard work of knowing that the Concept object contains a collection of ConceptSet objects, a collection of ConceptName objects, etc. To add a new name to a concept:
Hibernate knows what has changed and what needs to be saved into the database. (The long and short of it is that Hibernate wraps the Concept object in its own object and keeps track of what has been added, removed, etc).
Hibernate will not load all associated objects until they are needed – this is called lazy loading. The concept object above never dove into the concept_answer table to get the list of answers for concept 1234. If we had called concept.getConceptAnswers() Hibernate at that point would have made a call to the database to retrieve the answers for us. For this reason, you must either fetch/save/manipulate your object in the same session (between one open/closeSession) or you must hydrate all object collections in the object by calling the getters (getConceptAnswers, getConceptNames, getSynonyms, etc).

OpenMRS Source code

OpenMRS lives in a subversion repository.  See the ?Code Repository wiki page for more info.

Building OpenMRS

OpenMRS uses ?Maven to manage the libraries and build system.  See that wiki page for more info.

Modules

See the Module documentation for developers.  Modules are allowed to interact with OpenMRS on every level.  They can provide new entries into the Spring Application Context, new database tables, new web pages, and even modify current service layer methods.

Webapp

The OpenMRS organization creates and ships a webapp (openmrs.war) for people to use.  This webapp is a consumer of the API.  We expect there to be (and there are already) several different consumers of the API by different parties.

Spring MVC

OpenMRS strongly subscribes to the Model-View-Controller pattern. We won't go into the depths of MVC, or even the basics of it. Mediawiki has a complete writeup about everything you may have wanted to know about the MVC programming pattern. Spring has also written a fair amount on how and why to use MVC. OpenMRS, for the most part, uses the domain objects as the model. Most controllers will be SimpleFormControllers and be placed in the [org.openmrs.web.controller] package.  There are some controllers that have been rewritten to use Spring 2.5+ annotations.  We recommend using those. The model is set up in the controller's formBackingObject, and processed/saved in the processFormSubmission and onSubmit methods. The jsp views are placed in [/web/WEB-INF/view].
Not all files served by the webapp are run through Spring. The [/web/WEB-INF/web.xml] file maps certain web page extensions to the [SpringController]. All *.form, *.htm, and *.list pages are mapped. The SpringController then uses the mappings in the [openmrs-servlet.xml] file to know which pages are mapping to which Controller.
There are no .jsp pages that are accessed directly. If a pages url is /admin/patients/index.htm, the jsp will actually reside in [/web/WEB-INF/view/admin/patients/index.jsp]. This is necessary so that we can do the redirect with the SpringController. Because the file being accessed ends with .htm, the SpringController is invoked by the web server. When the SpringController sees the url, it simply replaces .htm with .jsp and looks for the file in /web/WEB-INF/view/ according to the jspViewResolver bean in openmrs-servlet.xml. If the page being accessed was patient.form, the mapping in the urlMapping bean would have told spring to use the PatientFormController and the patientForm.jsp file.
That spring descriptor file also contains settings for the max form upload size, locale changing, message names, fieldGen handlers, and name/address templates (to be removed: TRUNK-368 ).

DWR

Direct Web Remoting is a framework that allows us to translate java objects and methods to javascript objects and methods. Together with jquery/DOJO, DWR forms the basis of the AJAX in OpenMRS. The dwr.xml descriptor file describes which classes and methods are translated and made available to javascript calls. Most base DWR-able classes are placed into the org.openmrs.web.dwr package.  Modules can add dwr methods/objects and those will go into the already-registered-with-dwr dwr-modules.xml file.

Javascript

jQuery is the recommended JS framework. The included jquery package will be kept up to date with openmrs releases.  Import the one you need with
(but its already done in the header for you as of version 1.7) DOJO is a javascript library and packaging system. All dojo packages are stored in /webapp/src/main/webapp/WEB-INF/view/scripts/dojo. The custom OpenMRS javascript "classes" are stored in /webapp/src/main/webapp/WEB-INF/view/scripts/dojo/src/widget/openmrs.

________________________
Ref: https://wiki.openmrs.org/display/docs/Technical+Overview 

Thanks for Reading my Gsoc-Story this far! :)

Regards,
harshadura

______________________
Other related Links.

1. GSoc 2012 - Accepted Students From Sri Lanka
2. OpenMRS - GSoC 2012 Landing Page
3. List of all projects accepted into GSoC 2012
4. Project Proposal - Better Error Submission Process for FDBK Module

I created  Facebook group called "OpenMRS සිංහලෙන් ලියමු!" (Lets convert OpenMRS in Sinhalese together!) Most of the people who contributed to this translation program was my University friends. I really respect there humble contribution towards this innocent approach of mine. :) And there were some good people that I really dont know personally but they understood the value of this global healthcare system and contributed really really fine. I am thankful for all of them as well.

Facebook Group URL : https://www.facebook.com/groups/348002341879342/

I used a Collaborative etherpad tool Meeting words to Translate OpenMRS but I got to know after some time there were good online tools available specially for localization stuff and hopefully I think this method is also not bad. Other than the Server limitations of meetingwords.com it worked really fine.

Meeting Words : http://meetingwords.com/ep/pad/view/gCr6VIz0GT/latest




Here's the List of Contributors who helped this OpenMRS Sinhalese Localization Campaign in many ways.

1. Navodth Bhanuka
2. Mahen Samaranayake
3. Kulitha de Silva
4. Janani Jayathilake
5. Yashodha de Silva
6. Dehan Wijesekara
7. Udesh Settinayake
8. Geethika Perera
9. Hiyal Chathura
10. Roshana Muthuwan
11. Isuru Kodi
12. Manorama Perera
13. Sahan Maldeniya
14. Sumudu Abesuriya
15. Madushan Sameera
16. Nuwani Nishadhi
17. Jeewan Nandasena
18. Chamil Sanjeewa
19. Uthpala Dilhari
20. Angel Kodithuwakku
21. Dewmal Nilanka (EC2 hosting for the public release)

Note : Please note that, me (with these contributors) have translated as much as possible (only 50% out of full translated upto now, rest of others remains to be translated later on) I have opened a JIRA ticket at OpenMRS regarding this new feature. Then one of the senior developers of OpenMRS reviewed the translation and committed it to trunk repository.

JIRA Issue : https://tickets.openmrs.org/browse/TRUNK-3040

[This post describes Contributors who were interested in Localizing OpenMRS into Sinahala version, how they can contribute for this Camp. I have used Meeting Words one of Collaborative Etherpad tool for people to gather and translate the Values.]

(The below post is written in Sinhalese Unicode font which is the native Language of Srilanka)

හරි අපි මේ මහා පුණයකර්මය ආරම්භ කරන්නයි යන්නෙ..වැඩේ ගැන ඔයා තවම හරියට දැනුවත් නැත්තම් මේක මුලින් කියවල එන්න.

මම දැන් කියන්නම් මේ වැඩේ අපි කරං යන විදිය ගැන..
අපි දැන් මේ සෙට් කරල තීන විදියට වෙබ් බේස්ඩ් Document එකක් තීන්නෙ..
ඒ නිසා ඕනි වෙලාවක ඕනිම කෙනෙක්ට සැරෙන් සැරේට උනත් ඇවිත් වචන කීපයක් ලියල දායක වෙන්න පුලුවන්

[01] Document එක ගැන..
-----------------------------
මේක Programming languages වල නිතර වෙනස් වෙන Values දාලා තියෙන Document එකක්.. ඒකට සාමානයෙන් කියන්නෙ Property File 1ක් කියලයි.
ඔය කියන Property Files වල තීන්නෙ කොටස් 2යි. එකක් Key එක, අනික Value එක ඒ දෙක වෙන් වෙන්නෙ සමාන ලකුණකින්. key එක තමයි කෝඩ් එකෙ Variables ව්ලදි පාවිච්චි කරන්නෙ.. ඒ නිසා ආයි පස්සෙ කාලෙකදි ලේබල් එකෙ නම වෙනස් කරනවනම් Value එකෙ වෙනස් කරාම හරිනෙ. ඔන්න ඕකයි Property file එහෙක තියෙන වාසිය.

උදා:
key=value
user.code=User Name
pass.code=Password

මෙන්න මේ වගේ ගොඩාරියක් එකතු වෙලා තමයි Property file 1ක් හැදෙන්නෙ.

හරි දැන් මට කියන්න ඕනි මේකයි.
අපි Java Code එකක් ගහනකොට තිතයි කොමාව, බ්‍රැකට් මේන්ටේන් කරන්න ඕනිනෙ හරියට. නැත්තම් පස්සෙ ලෙඩ දෙනවානෙ.. ඒවගේම තමයි මේකෙත්. Property File එකක් තීන්න ඕනි විදියට තිබ්බෙ නැත්තම් ආයි ලෙඩ දෙනව. ඒක නිසා අපි පුලුවන් තරම් හරිම ක්‍රමේට කරන්න බැලුවොත් ලේසිවෙයි ලෙඩ අඩුකරගන්න.

Property files වලදි Single Line comment කරන්න පුලුවන් # ලකුණින්.
ඒ කියන්නෙ
උදා:
Navigation.home = නිවස
#Navigation.home = Home

මේකෙ Home කියන එක කොමෙන්ට් එකක්.

හරි ක්‍රමේ.
Navigation.home = නිවස
#Navigation.home = Home

වැරදි ක්‍රමේ.
Navigation.home = නිවස #Navigation.home = Home

උඩ තීන විදිය වැරදිය. මොකො Propert file එහෙක සමාන ලකුණ එහා පැත්තෙන් තීන ඔක්කොම ඌ Value එකට ගන්නව. තව ඔය පෙරලි කොමා උදා: ["ටෙස්ට්"], තනි කොමා උදා: ['ටෙස්ට්'] දැමීමෙනුත් වැඩේ කෙලවෙනව..
ඒව දාන්නෙ නැතුව වැඩේ කරන්න මහන්සි ගන්න.

[2] Comment දැමීම අනිවාර්යයි.
-----------------------------------

මම් කලින් කිව්ව නේද Property Files වල Comment දාන විදිය ගැන. ඔව් # එක ඊලට පේලියෙ තියල තමයි. මේ වැඩේ කරන්න ඕනි මොකද පස්සෙ Recheck කරද්දි මට බලාගන්න පුලුවන්නෙ මේ ලියල තීන සිංහල පරිවර්තනය කලින් තිබිච්ච ඉංග්‍රීසි වචනෙත් එක්කහරියට පරිවර්තනය වීමක් සිදු වෙලාද කියල. ඒක නිසා පරිවර්තනය කරන්න කලින් අර තිබිච්ච එක කොමෙන්ට් කරල යටට දාන්න.

මෙන්න මේ වගෙ..

කලින් තියෙන්නෙ මේ වගෙ
forgotPassword.title=OpenMRS - Forgot Password

පරිවර්තනයෙන් පසුව
forgotPassword.title=OpenMRS - මුරපදය අමතක වුනා
#forgotPassword.title=OpenMRS - Forgot Password

කොමෙන්ට් කරපු ඉංග්‍රීසි වචනෙ තීන පේලියයි, පරිවර්තනය කරපු පේලියයි වෙන් කරන්න හොදට ඉඩ කඩ තියන්න Enter එකෙන් ඔබල මෙන්න මේ වගෙ. එතකොට පැහැදිලිනෙ හුගක්.

#index.title=OpenMRS - Home
index.title=OpenMRS -නිවස

#login.title=OpenMRS - Login
login.title=OpenMRS - ඇතුලුවීම

#forgotPassword.title=OpenMRS - Forgot Passwordක්
forgotPassword.title=OpenMRS - මුරපදය අමතක වුනා

[3] Parameters සමග එකගොඩේ ලිවීමේදි උපදෙස්
---------------------------------------------------
general.displayingXtoYofZ=Displaying {0} to {1} of {2}
මෙවැනි වචනයක් පරිවර්තනය කරද්දි ගොඩක් ප්‍රවේසම් වෙන්න ඕනි.
මොකද ඔය {} දාල තීන්නෙ Parameters වගයක් Code එකෙන් පාස් කරන.
Java වල Command line arguments වගෙ සීන් එකක්.. ඒ නිසා ඕව කපන්නෙ නැතුව ගැලපෙන තැන් වලට සෙට් කර කර හදන්න.

මෙන්න මේ වගෙ
#general.displayingXtoYofZ=Displaying {0} to {1} of {2}
general.displayingXtoYofZ=දැන් පෙන්වන්නේ {0} සිට {1} දක්වා {2} මෙයයි

[4] HTML Tags තියෙ නම් එහෙමම තියන්න. කලින් අර Parameters සීන් එක විදියටම ක්‍රියාත්මක වන්න.

උදා :
#general.notYetImplemented=<font color='red'>Not Yet Implemented</font>

general.notYetImplemented=<font color='red'>මෙය තාම යොදාගෙන නැහැ</font>

---------------------------------------

දැනට නම් මට මෙච්චරයි විශේෂයෙන් සදහන් කරන්න දේවල් තීන්නෙ.. මොනා හරි අවුල් තැනක් තිබ්බොත් මට කියන්න. නැත්තම් මැසේජ් එකක් දාන්න..

සිංහලෙන් කොටන්න දන්නෙ නැති අයට
--------------------------------------------

RSinglish තමයි මං යූස් කරන Tool එකෙ නම. තව ඒව ගොඩක් තීනව.
මොනා හරි කමක් නෑ සිංහල යුනිකෝඩ් වලින් ටයිප් වෙන්නයි ඕනි.

Rsinglish වෙබ් අඩවිය :  [http://www.madurax86.com/rsinglish]
මේක නම් හෙන ලේසි පාවිච්චි කරන්න.
මේකෙන් අපි ලියනවත් එක්කම සිංහලෙන් කොටන්න පුලුවන්.
Scroll Lock එකෙන් තමයි සිංහල/ඉංග්‍රීසි switch වෙන්නෙ..

මුලින් මේක Download කරගෙන Install කරගන්න.


ඊට පස්සෙ Scroll eka එක ඔබල මොනා හරි කොටන්න. ඔයාට පෙනේවි සිංහල අකුරු.
ආයි ඉංග්‍රීසියට මාරු වෙන්න ආයි Scroll lock එක ඔබන්න. වැඩේ හෙන ලෙසි.

ඔයාට "අම්මා" කියල ටයිප් කරන්න ඕනි නම් Keyboard එකෙ "amma" කියල ටයිප් කරාම හරි.

Notes.
බිංදුව එන්නෙ q එකෙන්. තව Shift එකෙන් දීර්ග ඇලපිලි ආදිය පුලුවන්.
ටයිප් කරන ආකාර ගැන වැඩි විස්තර සදහා  [http://www.madurax86.com/rsinglish] බලන්න.

----------------------------

සිංහලයට පරිවර්තනය කරද්දි පුලුවන් තරම් ලංකාවෙ තොරතුරු තාක්ෂණයට නඹුරු වෙච්ච වචන භාවිත කරන්න උත්සුක වෙනවානම් වටිනව.

පලමු අදියර විදියට මම වචන 500 List එකක් Web Based Document එහෙක දාල තීනව. මේක Web based Collaborative Writing Tool එකක්.. ඒ නිසා Online කීප දෙනෙක්ට එක සැරේ උනත් මේ Document එක Edit කරන්න පුලුවනි.
ටිකක් ඈතින් ඈතින් ඔයා ටයිප් කරගෙන යන්න.. කොහොමත් අනික් කෙනා ටයිප් කරන දේ පෙනෙන නිසා ලොකු ගැටුලුවක් මතු වෙයි කියල මම හිතන්නෙ නැහැ.

හරි එහෙනම් අපි වැඩේ පටන් ගමු!
Document එකෙ කැමති තැනකින් පරිවර්තන කටයුතු පටන් ගන්න ඔයාට අවස්ථාව තීනව.
 
මං හිතනව කවුරුත් මේ පුණයකර්ම වැඩේට අනවශය විහිළු නොකරයි කියල. මේ ලියන දේට කුණුහරුප ලියලවත්, ලියන දේවල් මකල වත් පව් පුරවා නොගනී කියල.
කලින් Save කරන ලද Revisions තියෙන නිසා කොහොමත් එච්චර ලොකු අවුලක් වෙන්නෙ නැහැ.


මෙන්න එහෙනම් අපි වැඩ පටන් ගමු.
http://open-mrs-sinhalen.tk/