Skip to content

8.0 Incubator Objectives

Dave Lasley edited this page Nov 12, 2015 · 9 revisions

8.0 Incubator Objectives

1. Introduction

The objective is to retrieve a stable situation in harmony with Odoo 8.0 and OCA standard. This wiki targets a proper way to port addons/models from __unported__ to stable 8.0 version.

2. Concerned Modules:

2.1 General changes:

  • Try to split packed modules into smallers based on functional added values
  • Upgrade source code to be compliant with https://github.com/OCA/maintainer-tools/blob/master/CONTRIBUTING.md
  • Standardize views(search/form/tree/actions):
  • remove group_by on "unique datas/Text field"
  • only strict necessary actions (instead of an action per type of views)
  • use tags into form views in order to see label on the interface
  • unify xml_id of views
  • Use the correct nomenclature for relational fields
  • Remove useless model used to define a m2m with two o2m and replace them with real Odoo m2m

2.2 Medical EMR

Medical EMR is currently not good enough in terms of modularity concept (more than 20 python files with majority of them including a new functional concept ) as far as technical than functional. Also it has a lot of inconsistency.

Functional Improvements:

Medication And Medication Template

Major issue is that the start-end date is defined on medication and not on medication template. So this forces to create as much template as patient

Data model should be review with inclusion of an abstract concept. (to discuss)

Medicament:

Current implemented version introduce a ambigous relation between 'medical.medicament' and 'product.product' which may possibly beeing a source of additional complexity into the invoicing process of Odoo as product is the core of its billing process This notion has to be reviewed with two possible solution

  • remove medical.medicament and add complementary fields into product.product just as membership (is_membership) or expend (can_be_expend) (side effects: product table become too big and user see useless things (more complex views management)) or
  • use a real inherits to 'product.product' and keep additionals fields introduced by medical.medicament (possible problems: there already is a inherits from product.product to product.template)

Technical Improvements:

Integral review of all files to be consistency with https://github.com/OCA/maintainer-tools/blob/master/CONTRIBUTING.md

Dependencies:

                 medical
       |----------|----------------|
       |                           |
medical_disease              medical_medicament
       |                           |
       |                           |
       ----------------------------|
                            medical_medication
                                   |
                                   |
                                   |
                           medical_prescription
                                   |
                                   |
                                   |
                            medical_pharmacy

          __unported__/medical_emr

Pharmacy

Pharmacy module will provide workflows and KanBan queues to allow for standard pharmacy operations such as:

  • Receiving/Verifying Prescription Orders
  • Matching Prescription Orders to Sale Orders
  • Matching Sale Orders to Prescription Orders
  • PV1-2/DUR
    • These are verification stages performed by RPH's (prescription verification 1&2 + drug utilization review)

Web.pharmacy

Extension to the ECommerce & pharmacy modules providing customer ordering and other functionalities.

Others:

  • HIPAA Compliance
  • Update all ReadMe's
  • Add Adjudication
  • Unify Dependents & Family in medical.patient (Dependents are currently child_ids)