Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi i have below code :
SurgSup:
LOAD Distinct
SurgCardItemKey,
HAR,
UnknownPanelMarker,
Surgeon ,
OrProcedure,
all_proc_as_ordered,
ItemMfg,
ItemType,
SurgeryDate,
AmtUsed,
AmtWasted,
CostPerUnit,
AmtUsed * CostPerUnit as TotCost,
SurgLocation,
SurgFacility,
SurgInRoomDT,
SurgOutRoomDT,
Date#(Interval((SurgOutRoomDT) - (SurgInRoomDT),'m')) as ProcLength,
Interval((SurgOutRoomDT) - (SurgInRoomDT),'m') as zzzProcInterval,
SurgicalService
resident surgload;
drop tables surgload, surgtransform;
i am looking to hide the surgeon names from each other , surgeons should not be able to see the other surgeons name while they login into the system .
How can we achieve
that ,not sure how section access can be applied here
Different options here I guess. One is HidePrefix to hide fields from field lists for users in frontend.
However, if you want to apply section access I would use surgeon as the field to do data reduction on. As each surgeon should only be able to see its own data. Furthermore, you could also use in SA table the OMIT statement to make fields unvisible in the frontend for users.
Hope this helps.
Hi , i am using below code
LIB CONNECT TO 'ClaritySQL';
UserMapping:
LOAD "USER_ID" as SurgLogOPID,
NAME,
"PROV_ID",
"EPIC_EMP_ID",
;
SQL SELECT "USER_ID",
NAME,
"PROV_ID",
"EPIC_EMP_ID"
FROM clarity.dbo."CLARITY_EMP"
;
SurgSup:
LOAD Distinct
SurgCardItemKey,
HAR,
UnknownPanelMarker,
Surgeon,
SurgLogOPID,
SurgeonID, //prov_id
OrProcedure,
all_proc_as_ordered,
ItemMfg,
ItemType,
SurgeryDate,
AmtUsed,
AmtWasted,
CostPerUnit,
AmtUsed * CostPerUnit as TotCost,
SurgLocation,
SurgFacility,
SurgInRoomDT,
SurgOutRoomDT,
Date#(Interval((SurgOutRoomDT) - (SurgInRoomDT),'m')) as ProcLength,
Interval((SurgOutRoomDT) - (SurgInRoomDT),'m') as zzzProcInterval,
SurgicalService
resident surgload;
//where ApplyMap('UserAccessMap' ,SurgLogOPID,0);
drop tables surgload, surgtransform;
Section_Access:
load
'USER' as Access ,
'DS\'&SurgLogOPID as USERID,
Surgeon as OMIT
Resident SurgSup;
Section_Application;
still i could see Surgeon data at front end