Patient module validation

Registered by Lars Helge Øverland on 2010-04-09

The patient module needs validation on three levels:

1) Dynamic validation of the meta-data, meaning that the database content needs to be validated. So far there is one relation that must be validated: Patient properties must meet certain criteria to be eligible to a Program. All the "fixed properties" of Patient (not including Patient Attributes) could be compared using a logical operator to a value in order to be eligible for a Program . Example 1: <age> <less than> <5> eg. "Patient age must be less than 5 to attend Vaccination program. Example 2: <gender> <equal to> <female> eg. "Patient gender must be equal to female to attend ANC program.

2) Fixed validation of the meta-data:

ProgramStageInstance dueDate >= ProgramInstance dateOfIncident
ProgramInstance enrollmentDate >= ProgramInstance dateOfIncident

3) Dynamic validation of patient data values. A combination of ProgramStage-DataElement could be compared using a logical operator with another combination of ProgramStage-DataElement. Example: <Vaccination 1st visit> <Height> <less than or equal to> <Vaccination 2nd visit> <Height>. Example: <Vaccination 1st dose> <Date given> <less than> <Vaccination 2nd dose> <Date given>.

Blueprint information

Status:
Complete
Approver:
Lars Helge Øverland
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
Thu Tran
Definition:
New
Series goal:
Accepted for trunk
Implementation:
Implemented
Milestone target:
milestone icon 2.0.5
Started by
Lars Helge Øverland on 2010-05-31
Completed by
Lars Helge Øverland on 2010-05-31

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.