7a81.  Third Party Congruence2. Pharmacists in Retail 3.a) Normalize Third Party information to make for efeciifnt use of Pharmacist's time when attempting to bill for a prescription or service. This could be in the form of using standardized codes for different retains. You will have to option to look Third Party insurance up by state of origin. Condor Codes currently used by CVS/Walgreens will be present on every profile of a third party entity. The user may set several search options or filtering parameters when looking for Third Parties. For Example: a patient has just presented you with a Blue Cross Blue Shield of North Dakota card. Since this is not something you see often, you approach the application and input to a State of Origin Field: ND, secondly you input into a BIN filed the BIN # on the front of the card. Lastly you use the PCN identifier in the PCN field. The app returns to you that this is actually a Medco Plan. You double check this by seeing there is a Medco logo on the rear of the card. You take the Condor Code provided by the app and bill the Third Party successfully. You have eliminated the  guess and try  method that is too common in Retail pharmacy.b) The main challenge to creating a database such as this, is that there is vast array of third party providers out there. Allocating all of the information for each and every one would become expensive. Secondly, Third Party companies are changing constantly. Medicare Part D patients receive a new plan or card or ID number nearly every year. The use of the application may also be hard when you are unsure if the plan you found in search was truly the plan you are supposed to bill. Medco has several plans that use the same PCN # and you may receive multiple plans that may or may not all work. The pharmacist may not have enough information to narrow the field down to a usable amount of search returns either.27
 Inomaortifn is power and now I'm a !@#$ing dictator.

リロード   新規 編集 差分 添付 複製 改名   トップ 一覧 検索 最終更新 バックアップ   ヘルプ   最終更新のRSS