Patient Dashboard uses "concepts" to retrieve information about whether a Diabetes Foot Risk Assessment and Retinal Screening has been done for a patient. So long as these concepts are mapped correctly, Patient Dashboard should correctly reflect the foot risk and retinal screening status of the patient, regardless of which forms are being used to record this.
Having said that, however screening is done. the result must be recorded within a screening term.
Common screening terms used are:
- DFRA (if using Procon's Foot Risk Assessment form)
- DS:FE - Foot Examination (if using bestPractice)
- DS:RET - Retinopathy (if using bestPractice)
- DRET (if using Procon's Retinal Screening form)
The Procon concepts that must be correctly mapped are as follows:
10.2.14.1 must be mapped to a field indicating the outcome of a diabetes foot risk screen. Patient Dashboard looks to see whether these outcomes are defined as "normal" or "abnormal", or "excluded".
10.2.14.2 must be mapped to the date that the foot risk screen was done. This can either be the "observation date" of the screening outcome mapped to 10.2.12.1 or it can be a date field within the screening term itself.
10.2.14.3 must be mapped to a field that describes the outcome of the foot risk screen. This can either be the "description lookup" of the outcome mapped to 10.2.12.1 or can be a text field in the screening term itself.
The same concept applies to retinal screening, but with differenet concepts:
10.2.12.1 mapped to the outcome of retinal screening
10.2.12.2 mapped to the date retinal screening ocurred
10.2.12.3 mapped to a text field describing the outcome of retinal screening.
Here is some example mapping where the Procon forms have been used to record foot risk and retinal screening (which will need to be different if something other than the Procon forms are being used):
Here is some example mapping where the bestPractice ds:ret screening terms has been used (and again, this mapping will need to be different if not using this screening term) - note that this screening term does not have outcomes, so we need to use fields within the screening term instead:
0 Comments