Site and Location table: Difference between revisions

Line 110:

#Cardiology Service Patients that are '''physically located''' in the '''STB MICU''' but are looked after by the Cardiology Service physician will collected and entered into the database with a Site_location as: STB_MICU.

#Cardiology Service Patients that are "physically located" in the '''STB_CICU''' but are looked after the Cardiology Service physician will collected and entered into the database with a Site_location as: STB_CICU.

#*[[Registry Patient Type]] for the above two scenerios will be coded as '''C''' to indicate the patient is under ~~Cardiac~~ Physician Service Care.

#*[[Registry Patient Type]] for the above two scenerios will be coded as '''C''' to indicate the patient is under Cardiology Physician Service Care.

#If MICU attending physician '''takes over''' their '''care''', a new profile will be started

#Site_Location for the new profile will be STB_MICU

@@ Line 110: / Line 110: @@
 #Cardiology Service Patients that are '''physically located''' in the '''STB MICU''' but are looked after by the Cardiology Service physician will collected and entered into the database with a Site_location as: STB_MICU.
 #Cardiology Service Patients that are "physically located" in the '''STB_CICU''' but are looked after the Cardiology Service physician will collected and entered into the database with a Site_location as: STB_CICU.
-#*[[Registry Patient Type]] for the above two scenerios will be coded as '''C''' to indicate the patient is under Cardiac Physician Service Care.
+#*[[Registry Patient Type]] for the above two scenerios will be coded as '''C''' to indicate the patient is under Cardiology Physician Service Care.
 #If MICU attending physician '''takes over''' their '''care''', a new profile will be started
 #Site_Location for the new profile will be STB_MICU