...
- Project design
- Infrastructure requirements
- Machines for entering, storing, and accessing data
- Organizational requirements
- Infrastructure requirements: power, connectivity, security
- System requirements
- Implementations
- The OpenMRS Implementation Survey describes several organizations' implementations
- A few Point of Care examples
- Case study: Rolling out OpenMRS in Rwanda
- More examples and information on the Projects page
Initial Setup - From Beginning to Launch
- Implementation process overview
- Installing OpenMRS
- Initial configuration is created by the Installation Wizard
- Constructing forms: An iterative and non-trivial process
- Customizing look and feel
- change the default theme to a different color palette
- use the custom branding module to add your own logo
- add your own CSS files and login, registration, and dashboard JSPs by overriding the default runtime properties
- Using OpenMRS modules
- Finding and selecting modules is covered in detail in Getting Started with OpenMRS
- The module repository contains descriptions, downloads, and documentation links for each module .
- Installing modules
- If you encounter a problem after installing a module, the first step is to stop and restart it from the Administration > Manage Modules page. It will show an error message if there was a trouble during startup. If the problem persists, stop the module and recheck the symptoms. This will confirm that the problem comes from that module. See the module's documentation for troubleshooting suggestions. You can receive further help from the Implementers mailing list.
- Role and User development
- OpenMRS uses roles to manage permissions. Typical roles include:
- system administrator - configures OpenMRS, installs and updates modules, manage user accounts
- registrars - adds new patients to OpenMRS at check-in; adds patients to programs
- data entry clerk - creates and updates encounters after a visit
- care providers - views patient records at point of care; creates or updates orders or encounters; assigns regimens
- content editors - creates or updates the forms that collect encounter data; adds or changes concepts in the concept dictionary; adds or updates programs
- Users, roles, and permissions are managed through the administrator control panel at Administration > Users.
- OpenMRS uses roles to manage permissions. Typical roles include:
- Patients
- Identifiers
- Overview: administering identifiers
- the ID Generation and Registration modules generate identifiers.
- The Registration module supports biometric ID through fingerprints.
- best practices
- Deciding what information to collect
- patient attributes
- caretakers
- Registration
- modules
- best practices
- Identifiers
- Concept development
- How to translate an idea to a concept - read /wiki/spaces/RES/pages/26290270, lecture 4, "Concepts, Observations, and Encounters"
- Best practices
- Jump start with the OpenMRS Concept Collaborative (OCC)
- Mapping - why and how to map concepts
- Concept mapping changes
- Form development
- Implementation options - XForms, InfoPath, HTMLForms - /wiki/spaces/RES/pages/26312479
- Administering forms
- Best Practices for Translating Paper Forms - /wiki/spaces/RES/pages/26312479 - slides 22-24, "Guidelines for Managing Forms"
- Examples at the Form Bank
- Some best practices for implementations
- Data migration
- Receiving information from external applications into OpenMRS
...