--- title: FDB to VS Conversion Process slug: portal-sub/fdb-to-vs-conversion-process docTags: createdAt: 2026-03-04T12:03:22.803Z --- # First DataBank (FDB) to Vigilance Santé (VS) Conversion To support practices moving to the Vigilance Santé (VS) formulary system, Intrahealth has released an FDB to VS Cross Reference based upon the mapping table provided by Vigilance Santé. The cross references provide automatic links for around 80% of the FDB branded and generic drugs.  This document will guide you on how to convert the FDB data to VS. # Frequently Asked Questions ### What will change when converting FDB to VS? All instruction templates and adverse reactions that reference First DataBank drugs will be updated to reference Vigilance Sante drugs. Cross references will automatically update most FDB prior and usual scripts to the VS equivalent when prescribing. ### How long does the conversion process take? The length of the conversion process varies depending on the size of the databank, but we recommend the bulk conversion is run at a quiet time of day as it may slow down performance for some time. ### What will happen to a patient's old prescription history? Prescription history will not be affected by the change, as the FDB medications can be cross referenced to the equivalent in VS. ### How are the medications matched? The medications are matched using their DIN codes. If there are no DIN matches, it is possible to create a cross reference on matching NTP codes. ### What happens if there is no match between the FDB medication and VS? The FDB drug will not be converted. However, the next time the drug is prescribed, the system will allow you to create a manual cross-reference. See the [FDB to VS Prescribing Information](docId\:SgzUP_voI9TiL2o8xJ3df) document for more information. ### What happens to previous ad-hoc prescriptions? Ad-Hoc prescriptions are not linked to any formulary and therefore no cross references will be available. ### How do regular updates happen? At the start of each month, Intrahealth will update the formulary and package this in a jaffa file. # Conversion Requirements - Profile 8.8.10 - The VS Drug Database and the cross references have been imported by Intrahealth. - The Default Rx System has been switched to Vigilance Santé by Intrahealth. - The role action **Organization\Control Centre\Manage\Bulk Updating** must be granted. # How to begin Bulk Conversion As usual medications, and prior prescriptions can be matched through cross-references, the bulk conversion process does not need to be done for these. However, instruction templates and adverse reactions are linked to the FDB database and thus require extra steps to convert. 1. Go to **Control Centre/Manage/Bulk Updating **and select** Instruction Templates (FDB to VS) **and** Adverse Reactions (FDB to VS)** in the** Items to bulk update **panel. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/jrjeFec2pffJyiDkyRYCt_mqzv0tpf0v0exltpzdedhtiluv9htseraw.png" size="100" isUploading="false" initialPath="assets/MqZV0tpf0v0EXltpzdEdhtilUv9htseRAw.png" githubPath="en/Technical Resources/Data Transfer/assets/MqZV0tpf0v0EXltpzdEdhtilUv9htseRAw.png" position="flex-start" showCaption="false" indent="2"} :::Paragraph{indent="1"} This view will display all the FDB items which have been used in patient records.**Instruction Templates (FDB to VS) **and** Adverse Reactions (FDB to VS) **can be selected and converted individually. ::: 2. Press ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/ecGogUnM3YP0zcCeE64aK_xm1uxd1wnvlhcdgkddbthfejmk7wekaffa.png" size="17" isUploading="false" initialPath="assets/xm1uXd1wnvLhcdgkddbTHFejMK7WekafFA.png" githubPath="en/Technical Resources/Data Transfer/assets/xm1uXd1wnvLhcdgkddbTHFejMK7WekafFA.png" position="flex-start" showCaption="false" indent="2"} :::Paragraph{indent="1"} in the **Bulk Updating** toolbar to start the conversion process.  A confirmation dialog box will appear. ::: ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/L0mbJT8-0IRPHsFHKDfoX_eiludyzgdi8gbghr5lp-rl6kvvqacyrw.png" size="100" isUploading="false" initialPath="assets/eiLuDyZgdI8GbGHR5Lp-rl6KVvqa_CyR_w.png" githubPath="en/Technical Resources/Data Transfer/assets/eiLuDyZgdI8GbGHR5Lp-rl6KVvqa_CyR_w.png" position="flex-start" showCaption="false" indent="2"} :::Paragraph{indent="1"} Individual templates or reactions can be selected separately and the ::: :::Paragraph{indent="2"} ::: ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/uNEGcG2b9FaQf1YLD092z_qtf78dmxombcwnzbqr1jtp2khukw7hirq.png" size="10" isUploading="false" initialPath="assets/qTF78dmXomBCWnzBQR1JTp2_khuKw7HIRQ.png" githubPath="en/Technical Resources/Data Transfer/assets/qTF78dmXomBCWnzBQR1JTp2_khuKw7HIRQ.png" position="flex-start" showCaption="false" indent="2"} :::Paragraph{indent="1"} icon can be clicked in the **Bulk Updating** toolbar to only convert the selected items. ::: 3. Press **Yes** to confirm the conversion. A processing window will appear, displaying a specific progress bar and a total progress bar. This process may take some time, depending on the size of the database. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/6vbd1t60scMSCNlXTchg0_esblw5irf0jzs2cpfpnoczvdeigx1dokwg.png" size="47" isUploading="false" initialPath="assets/eSblW5irf0jzs2cPFpNOcZvdEiGX1dOkWg.png" githubPath="en/Technical Resources/Data Transfer/assets/eSblW5irf0jzs2cPFpNOcZvdEiGX1dOkWg.png" position="flex-start" showCaption="false" indent="2"} 4. When the process is finished, press **OK** in the dialog box. ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/X3scM_R7F6Pmyt17Rz6We_hqayr6idsqzkkgb5q94oahko7ap7rc0q.png" size="96" isUploading="false" initialPath="assets/hqayr6Id_sQzkKgb5Q94OahkO7A_p7RC0Q.png" githubPath="en/Technical Resources/Data Transfer/assets/hqayr6Id_sQzkKgb5Q94OahkO7A_p7RC0Q.png" position="flex-start" showCaption="false"} After the conversion is done, click ::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/1zWD_rauB52KbIx6T678s_5ch22wlzrp4k-gv7q51zrcf0khxhtymslq.png" size="10" isUploading="false" initialPath="assets/5cH22wLZRP4k-GV7Q51zrcF0KhxHtymslQ.png" githubPath="en/Technical Resources/Data Transfer/assets/5cH22wLZRP4k-GV7Q51zrcF0KhxHtymslQ.png" position="flex-start" showCaption="false"} in the **Bulk Updating** toolbar and the converted items will disappear. :::hint{type="info"} Adverse Effects in Formulary is not related to **Adverse Reactions** in the Bulk Update process. Only Adverse Reactions recorded for patients are involved in conversion. ::: :::hint{type="info"} Descriptions for **Adverse Reactions **will not be updated. However, after converting from FDB to VS, Profile can still check **Adverse Reactions **for allergy warnings. ::: ## Prescribing Unmapped Medications When the cross references are imported into Profile by Intrahealth, the process will automatically convert medications from FDB into their equivalents in VS based on its DIN code. Around 80% of all medications in FDB have a match in VS and cross-references will be created. However, some medications will not be cross-referenced through this process. For those medications, a manual cross-reference can be created at the time of prescribing so that all the future prescriptions are automatically created within the new formulary. For information on how to create manual cross-references, see the [FDB to VS Prescribing Information](docId\:SgzUP_voI9TiL2o8xJ3df) document.