VPMS Web Application

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3
• Fix Version/s: 1.3
• Component/s: Patient
• Labels:

  None

This is a need to allow individual practices to add additional patient fields to store date, text , lookup and numeric information. The current archetyping system allows the site to modify the fields generally for a party.patientpet archetype but cannot support fields that are specific to the value of another node in the archetype, such as the species node.

To overcome this we suggest the following :

1. In the current party.patientpet archetype add a custom node that contains 0:1 collection of entityRelationship.customPatientFields to entity.customPatient* archetypes. The entity.customPatient* archetypes represent site specific archetype definitions for the additional fields required and can be species specific. The system implementor will be responsible for providing these archetypes and maintaining them during upgrades on the site.

2. The lookup.species archetype will be modified to include a customFields node which will nominate the entity.customPatient* archetype name to use when managing a party.patientpet with this species selected.

3. During editing of the party.patientpet archetype if the patient species changes or is selected utilise the lookup.species customFields node to ascertain if a new entity.customPatient* archetype needs to be created or modified and linked to the party.patientpet.

• If none create new one.
• If an existing one with the same archetype name exists leave alone.
• If one with different archetype name delete and create new.

• Assignee:

  Tony De Keizer

  Reporter:

  Tony De Keizer

• Due:

  05/Sep/08

  Created:

  28/Aug/08 1:41 PM

  Updated:

  08/Mar/10 11:22 PM

  Resolved:

  15/Oct/08 8:54 AM