veNOM codes
Given the planned implementation of the veNOM codes for Diagnosis and Presenting complaints.
Is there a benefit to expanding our current archetypes to accept the veNOM codes for:
species
Species
The species listing within the code is a generic listing that links together breeds in the hierarchy system. The 46 listed species are simplified names to include large groups of species within a colloquial name (eg Hamster or Mouse). More common single species groups have their synonym colloquial names and their scientific names linked within the codes (eg Sheep and Ovine).
breeds
The breed codes currently consist of canine and feline breeds that are recognised by kennel clubs and cat fancying associations across the world. Where possible all synonyms of the same breed have been linked in the codes to each other, and are independent of their colour coding unless it is specific to that breed. Similar breeds have been grouped together using standard categories (eg Retrievers or Spaniels). The list is very inclusive to ensure all types of dog breeds are covered, and first generation pedigree crosses (such as Labradoodle or Puggle) are also included to assist with data capture. Non-standard cross breed dogs are recorded as synonyms of 'Crossbreed'. The cat terms are more uniform across the world and results in a simpler list, only certain breed descriptors are included as extra to the breed (eg Point). This list is frequently being updated as new breeds are introduced across the world.
Currently, equine and farm animal breed lists are being generated along with small furries and exotics.
product.services -
Procedures
The veterinary procedures performed at both first opinion and referral practice can be coded for within 718 different procedure codes. These codes catalogue all the procedures that are performed in small animal clinics. Equine and Farm animal procedures are currently under development.
product.medications
Therapeutics
The therapeutic codes are currently under development. The VeNom Coding Group are very grateful for the help of The BSAVA Formulary in developing the therapeutic terms within the VeNom list.
If Openvpms Pty Ltd has signed a endUser agreement with veNOM, I would be happy to work on xml's to load these as part of the base installation(making them optional)
Re: veNOM codes
See the VeNom Coding project for background. The Diagnosis and Presenting Complaint codes are related to:
These codes don't have any equivalent in OpenVPMS 1.7 or below, so there is no issue in loading them.
The other codes provided by VeNom:
We can support the Species, and Breed by:
The Reason for Visit correponds to the lookup.appointmentReason lookup. This would be supported by:
(Alternatively, rename lookup.appointmentReason to lookup.reasonForVisit - marginally shorter).
The lookup.speciesVeNom and lookup.breedVeNom codes would be part of the setup installation data, not the base data. Practices migrating from other systems will already have their own species and breeds.
Reports would need to be updated to allow for the archetype changes (e.g. use "like lookup.species%" instead of "=lookup.species").
The Procedure and Diagnostic test codes may be useful if you want to submit data to VetCompass.
Re: veNOM codes
Forgot to mention that the scripts to generate the diagnosis and presenting complaint codes are in openvpms-etl/scripts/VeNom. There's a readme.txt describing the requirements.