ProcCode

A ProcCode instance is a custom data object of high importance to the openmolar application.

this is the object sent to the application when user selects a code from the procedure code widget.

ProcCodes are ALWAYS initiated at application startup when the ProcedureCodes object is created.

Their properties are obtained by decoding the file resources/proc_codes/om_codes.txt

(which is actually stored as a QResources, so editing the file will only take effect once QResources are refreshed)

Note

it is my intention that openmolar codes remain unique. If a practice needs additional codes, then this should NOT be done by modifying the file mentioned above.

methods and attributes

class lib_openmolar.common.datatypes.proc_code.ProcCode(element, category)

Bases: object

__init__(element, category)

BRIDGE = 6

CROWN = 5

FILL = 4

OTHER = 8

PROSTHETICS = 7

ROOT = 3

SIMPLE = 0

TEETH = 2

TOOTH = 1

allowed_pontics

a list of teeth which can be replaced with this procedure (eg upper teeth only for a P/-)

category = None

code

comment_required

some items require an extra description from the user when converting to a TreatmentItem eg. “other treatment” code needs embellishing

crown_type

the code expected by a ToothData object so that an item of this type can be drawn correctly

description

element = None

A pointer to the minidom element which holds the info about this code

further_info_needed

is_bridge

is_chartable

can this procedure be displayed on a dental chart?

Note

this needs more work!

is_crown

is_fill

is_prosthetics

is_root

is_tooth

material

multi_tooth

no_pontics

no_surfaces

pontics_required

range_from_node(node)

returns a list of ints which have been specified in the xml in this way <tooth_range>18..33</tooth_range>

surfaces_required

tooth_required

this is a property indicating that to become a treatment item a tooth is required. this is, for example, the case with an MOD filling, but not needed for an examination

total_span

returns the span of a bridge this is a string, so as to allow values like “3+”

treatment_item_requirements

the xml config sheet can speculate what is needed to create a valid TreatmentItem from this code

tx_type

type