v 10.0 Third Party 6079
Download for v 10.0 Deploy on Odoo.sh
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Community Apps Dependencies
Technical Name medical
LicenseGPL-3
Websitehttps://odoo-community.org/
Versions 10.0
You bought this module and need support? Click here!

Odoo Medical

This module extends Odoo with the base functionality of medical patients.

Installation

This module depends on modules located in the following repos: * https://github.com/OCA/partner-contact

Check the __manifest__.py for the specific dependencies.

Usage

Patients

Patients are available in the Medical App, in the Patients submenu.

Medical Abstract Entity

The Medical Abstract Entity (medical.abstract.entity) is an AbstractModel that provides for a central base that all medical entities should inherit from.

A Medical Entity is any partner that also requires a medical context. Examples:

  • MedicalCenter
  • MedicalPatient
  • MedicalPhysician
  • MedicalPharmacy

Some base views are also provided in order to make it easy to create new medical entities & maintain uniformity between them:

  • Kanban - medical_asbsract_entity_view_kanban
  • Tree - medical_asbsract_entity_view_tree
  • Form - medical_asbsract_entity_view_form
  • Search - medical_asbsract_entity_view_search

When inheriting these views, you must define the inheritance mode as primary, such as in the following example:

<record id="medical_patient_view_tree" model="ir.ui.view">
    <field name="name">medical.patient.tree</field>
    <field name="model">medical.patient</field>
    <field name="inherit_id" ref="medical_abstract_entity_view_tree" />
    <field name="mode">primary</field>
    <field name="arch" type="xml">
        <xpath expr="//tree" position="attributes">
            <attribute name="string">Patients</attribute>
        </xpath>
        <xpath expr="//field[@name='email']" position="after">
            <field name="identification_code" />
            <field name="age" />
            <field name="gender" />
        </xpath>
    </field>
</record>

Take a look at medical/views/medical_patient.xml, or any of the other medical entity views for more examples.

Try me on Runbot

Known issues / Roadmap

  • There is a singleton issue with the ID numbers pass-thru & crossing could occur.
  • v11 - Move Marital status into a new module in OCA/partner-contact

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smash it by providing detailed and welcomed feedback.

Credits

Images

  • Odoo Community Association: Icon.
  • DevCom: Patient Avatar.

Contributors

The current project as it is today represents an evolution of the original work started by Luis Falcon. See https://sourceforge.net/projects/medical/files/Oldfiles/1.0.1, that later became GNU Health (see http://health.gnu.org/). The original code was licensed under GPL.

On Nov 27, 2012 derivative code was published in https://github.com/OCA/vertical-medical, by Tech-Receptives Solutions Pvt. Ltd., licensed under AGPL. The license change was unauthorized by the original author. See https://github.com/OCA/vertical-medical/commit/f0a664749edaea36f6749c34bfb04f1fc4cc9ea4

On Feb 17, 2017 the branch 9.0 of the project was relicensed to LGPL. https://github.com/OCA/vertical-medical/pull/166. Various prior contributors approved the relicense, but not all.

On Jan 25, 2018, GNU Health claimed that the original code and attribution should be respected, and after further investigation the Odoo Community Association Board agreed to switch the license back to GPL v3 to respect the rights of the original author.

Although no trace of relationship was found between the code at the date and the original code from 2012, through the commit history of the project one can see that the current status of the project is the end result of an evolutionary process. The Odoo Community Association Board concluded that the original license should be respected for ethical reasons.

More information can be read here - https://odoo-community.org/blog/our-blog-1/post/vertical-medical-75.

Maintainer

Odoo Community Association

This module is maintained by the OCA.

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

To contribute to this module, please visit http://odoo-community.org.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author, please use the developer contact information. They can usually be found in the description.
Please choose a rating from 1 to 5 for this module.
Error create new patient in Medical Odoo module v.10
by
Gita Azizah Putri
on 11/15/17, 8:03 PM

I can open in Odoo 10 , and I just installed Medical app , and when i try to creat a new patient, but it displayed error : Error: NameError: name 'supplier' is not defined http://192.168.1.100:8069/web/content/4093-8cb3364/web.assets_backend.js:1326 Retraçage : Error: NameError: name 'supplier' is not defined at PY_ensurepy (http://192.168.1.100:8069/web/content/4093-8cb3364/web.assets_backend.js:1326:65) at Object.py.evaluate (http://192.168.1.100:8069/web/content/4093-8cb3364/web.assets_backend.js:1441:8) at Object.py.evaluate (http://192.168.1.100:8069/web/content/4093-8cb3364/web.assets_backend.js:1450:194) at Object.py.eval (http://192.168.1.100:8069/web/content/4093-8cb3364/web.assets_backend.js:1454:284) at http://192.168.1.100:8069/web/content/4093-8cb3364/web.assets_backend.js:1593:110 at iterator (http://192.168.1.100:8069/web/content/3207-a962549/web.assets_common.js:14:183) at Function. (http://192.168.1.100:8069/web/content/3207-a962549/web.assets_common.js:17:8) at _.(anonymous function) [as reduce] (http://192.168.1.100:8069/web/content/3207-a962549/web.assets_common.js:69:526) at eval_contexts (http://192.168.1.100:8069/web/content/4093-8cb3364/web.assets_backend.js:1591:136) at http://192.168.1.100:8069/web/content/4093-8cb3364/web.assets_backend.js:1593:253.. how to solve this problem?


Error set up medical odoo 10 with odoo 10
by
dinhha
on 2/28/20, 3:38 AM

Hello. i just installed medical app but i have problem "You try to install module 'medical' that depends on module 'base_locale_uom_default'. But the latter module is not available in your system." I try to find module base_locale_uom_default in odoo but no result. I need your help? thank you so much


Error when creat new patient of Medical Odoo 10
by
Boutaina AS
on 9/20/17, 6:32 AM

I just installed Medical app , and when i try to creat a new patient, it displayed error like bellow : Uncaught Error: NameError: name 'supplier' is not defined


Error when creat a new patient
by
Boutaina AS
on 7/21/17, 4:49 AM

I work with Odoo 10 , I just installed Medical app , and when i try to creat a new patient, it displayed error like bellow : Uncaught Error: NameError: name 'supplier' is not defined http://192.168.1.100:8069/web/content/4093-8cb3364/web.assets_backend.js:1326 Retraçage : Error: NameError: name 'supplier' is not defined at PY_ensurepy (http://192.168.1.100:8069/web/content/4093-8cb3364/web.assets_backend.js:1326:65) at Object.py.evaluate (http://192.168.1.100:8069/web/content/4093-8cb3364/web.assets_backend.js:1441:8) at Object.py.evaluate (http://192.168.1.100:8069/web/content/4093-8cb3364/web.assets_backend.js:1450:194) at Object.py.eval (http://192.168.1.100:8069/web/content/4093-8cb3364/web.assets_backend.js:1454:284) at http://192.168.1.100:8069/web/content/4093-8cb3364/web.assets_backend.js:1593:110 at iterator (http://192.168.1.100:8069/web/content/3207-a962549/web.assets_common.js:14:183) at Function. (http://192.168.1.100:8069/web/content/3207-a962549/web.assets_common.js:17:8) at _.(anonymous function) [as reduce] (http://192.168.1.100:8069/web/content/3207-a962549/web.assets_common.js:69:526) at eval_contexts (http://192.168.1.100:8069/web/content/4093-8cb3364/web.assets_backend.js:1591:136) at http://192.168.1.100:8069/web/content/4093-8cb3364/web.assets_backend.js:1593:253