| | 1 | [[i2b2 - UHL clinical informatics system integration|back]] |
| | 2 | |
| | 3 | == Source |
| | 4 | |
| | 5 | * The information is stored in the DWEPMA database on the data warehouse server. |
| | 6 | * The formulary is based on the First Databank standard. |
| | 7 | * The version in use is not the latest version. |
| | 8 | * The latest version is in test, but there have been problems. |
| | 9 | * It contains the same drugs multiple times for different manufacturers. |
| | 10 | * The prescription data does not always contain all the information (dosage, route, frequency, duration) as this may be added by the person who administers the drug. |
| | 11 | * Once created, prescriptions are never altered. |
| | 12 | * Incorrect prescriptions are stopped and a new prescription is issued. |
| | 13 | |
| | 14 | == Mapping |
| | 15 | |
| | 16 | * Depending on how closely the formulary sticks to the First Databank standard, it may be possible to use the [http://www.nlm.nih.gov/research/umls/rxnorm/ RxNorm] standard as an ontology or as a way to map the codes to SNOMEDCT. |
| | 17 | * Dosage, route, frequency, duration can be stored in i2b2 as modifiers. This would require i2b2 to updated version 1.6. |
| | 18 | |
