Version: 2.1.14076
Web Service
with methods used for geting a use's access to services and units and to get
and list information about services and unit access.
All methods
require a correct and verified Authentication Block from AuthorizationWS to get
any information from the HIS.
The
AuthorizationWeb Service contains these methods:
The Web Service reference is: AuthorizationWS.asmx
Open in a
Web Browser for more detailed information about each method. The Web Service's WSDL, SOAP request and
response is described.
For more
detailed information as the Web Service's WSDL, SOAP request and response see:
https://linkws.service.tieto.com/PasLinkWS/AuthorizationWS/AuthorizationWS.asmx
Applicable
systems for method:
|
INFOMEDIX |
HIS90 |
CLASSIC |
|
|
|
|
Description:
The methods
returns the user's accesspermissions to a set if given services/functions in
the system. If no service/function names is specified the function return the
user's accesspermissions to all services/functions.
Syntax:
UserServiceAccesses
= GetUserServiceAccess(UserServiceAccessSearch)
|
Parameter
in |
Type |
Length
byte |
Description
– Data format – Valid data |
|
UserServiceAccessSearch |
Datastructure according to useraccess.xsd scheme |
N/A Dynamic |
Inparameter
is UserServiceAccessSearch[] is an collection of services. Either id or name of service must be given.
Id is internal id/code or function number in HIS. If one or more services is
sent in, the method will get the user's access permissions to these services.
Type is used for type of service. S is single services within the system, but
G is a group of several single services grouped together as a logical unit. If no services is specified as parameter into
the method, the method will get the user's access permissions to all services
available in the system. InfoMedix: Getting all services is not implemented. |
Definition
of the data structure UserServiceAccessSearch
for getting
information from
GetUserServiceAccess
|
Name |
Type |
Length Byte |
Description
– Comments |
|
Service
* xxx |
Service ; the structure below is
repeated xxx times. where xxx is valid from 0 to
endless/undetermined See useraccess.xsd scheme for structuredetails |
||
|
Id |
Number |
4 byte |
Id
is internal id/code or function number in HIS. Optinal
– either id or named has to be given. |
|
Type |
String |
N/A Dynamic |
Type
is used for type of service. S is single services within the system, but G is
a group of several single services grouped together as a logical unit. INFOMEDIX: Required. HIS90/CLASSIC/Other: Blank to list all |
|
Service |
String |
N/A Dynamic |
Name of service, either spesific
for HIS/PAS system or defined in mappingtable. Optinal
– either id or named has to be given. |
Schema for
UserServiceAccessSearch: UserAccess.xsd
Schema
documentation for UserServiceAccessSearch: UserAccess.html
Sample xml
file for UserServiceAccessSearch: UserServiceAccessSearch.xml
|
Returned
parameter |
Type |
Length
Byte |
Description
– Comments |
|
UserServiceAccesses
|
Datastructure according to useraccess.xsd scheme |
N/A Dynamic |
An array with a collection of
UserServiceAccess. The
return data is collection of which services and if the user has access to the
service. And if the system have several level of access this will also be returned.
If only true/false is given for the access level then 0 is returned as false
and any number greater than 0 is true. Eg. 9=True. The
data structure is dynamic and can return from 0 to undetermined number of
records with UserServiceAccess. |
Definition
of the data structure UserServiceAccesses
for getting
information from
GetUserServiceAccess
|
Name |
Type |
Length Byte |
Description
– Comments |
|
UserServiceAccesses
|
|
|
Collection
of UserServiceAccess type |
|
UserServiceAccess * xxx |
UserServiceAccess ; the structure
below is repeated xxx times. where xxx is valid from 0 to
endless/undetermined See useraccess.xsd
scheme |
||
|
Service |
|
|
A
service in the system |
|
-
Id |
Number |
4 byte |
Internal
id/number for service in the system. |
|
-
Type |
String |
N/A Dynamic |
Type of service. S=single service.
G= Group of many services |
|
-
Name |
String |
N/A Dynamic |
Name of service |
|
AccessLevel |
Number |
4 byte |
What access user have to the
service. Accesslevel: 0 is no access (False) and >0 is has access. (True
> 0). AccessLevel can have different values
above 0 to give the user different access to functionality. Infomedix: Only 0 (have not access) and 1 (have access) are used. HIS90/CLASSIC: Return a value between 0 and 9 where 0 is no access, and 1 is has
minimum access and graded to 9 for full access(super user access). |
Schema for
UserServiceAccesses : UserAccess.xsd
Schema
documentation for UserServiceAccesses : UserAccess.html
Sample xml
file for UserServiceAccesses : UserServiceAccesses.xml
Web Service Response and Request:
Related
methods or functions used:
GetUserLogin Used
to verify as user, and to get a valid authentication Block in return.
Other
references:
RequestHeader Information required calling a method, containing
authentication information.
ResponseHeader Information and messages returned from the method, e.g.
error codes/description,
system name or version.
Comments:
To use this
method the RequestHeader must contain
a valid Authentication Block and the system name is required. An error will be
raised if one of these is missing.
Valid
Authentication Block for RequestHeader
the can be retrieved by using the method GetUserLogin
in Authentication-Web Service.
In return
form the method there will always be a ResponseHeader,
which contains Error Information and System Information. Error Information
block must always be checked to determine if any error has occurred while
processing the methods.
Applicable
systems for method:
|
INFOMEDIX |
HIS90 |
CLASSIC |
|
|
|
|
Description:
The methods
returns all the units/departments that the user has access to in the organization.
The user is
identified by the security tocken. If access is related to units/roles
(possible restrictions) then access is resolved through the active/or logged on
unit/role stored in security tocken.
For some
systems the patient’s official id can be in input, the output from the method
will then show user’s access related to selected patient’s context. The
selection of units can then also be rescricted/enhanched by functional access.
Syntax:
UserUnitAccesses =
GetUserUnitAccess(OfficialId)
|
Parameter
in |
Type |
Length
byte |
Description
– Data format – Valid data |
|
OfficialId |
Number |
4 byte |
Patient’s
official id. Used for selecting units the logged on user have access to in a
patient context. HIS90:
Only implemented for HIS90 systems yet. Formatt:
DDMMYYNNNNN. For
HIS90 the selcetion of unit is also related to a functional accesslevel that
says what unit the logged on user have access to in a patient context, see HIS90 details |
|
Returned
parameter |
Type |
Length
Byte |
Description
– Comments |
|
UserUnitAccesses |
Datastructure according to useraccess.xsd scheme |
N/A Dynamic |
An array with a collection of UserUnitAccess. The
return data is collection of a user's accesses to units and the level of
access. If only true/false
is given for the access level then 0 is returned as false and any number
greater than 0 is true. Eg. 9=True. The data structure is dynamic and can return
from 0 to undetermined number of records with UserUnitAccess. |
Definition
of the data structure UserUnitAccesses for getting information from GetUserUnitAccess
|
Name |
Type |
Length Byte |
Description
– Comments |
|
UserUnitAccesses |
|
|
Collection
of UserUnitAccess,
MedicalUnits and Institution |
|
UserUnitAccess* xxx |
UserUnitAccess
; the structure below
is repeated xxx times. where xxx is valid from 0 to
endless/undetermined See useraccess.xsd
scheme |
||
|
Unit |
|
|
Unit
or department the user has access to. |
|
-
Id |
Number |
4 byte |
Internal
id/number for the unit in the system. |
|
-
TypeOfId |
String |
N/A Dynamic |
Internal id for the organizationunit. Valid values for TypeOfId are: HIS90: LIN = Local institution id LAV = Local medical unit /department id LEN = Local care unit id Infomedix: LIN = Local institution id LCL = Local MedicalClinicRegistration and
MedicalList LAV = Local MedicalSpecialityRegistration and LEN = Local CareRegistration and CareList unit
id LVA = Virtual MedicalList unit id LVE = Virtual CareList unit id LV =
Vrtual MiedicalList and CareList unit id LGA = Grouping MedicalList unit id LGE = Grouping CareList unit id LG =
Grouping MedicalList and CareList unit id For filtering of
units to be used in Infomedix listboxes, a typical TypeOfId filter
could be like this (used in RoS): For a registration
listbox: Medical units (sections) : LAV, LCLAV Care units (departments): LEN For a list group/report listbox: Medical
responsibility : LAV, LCLAV, LG, LGA, Care
responsibility : LEN, LG, LGE,
LIN, |
|
-
ShortNameId |
String |
N/A Dynamic |
Short name or code for the unit |
|
-
Name |
String |
N/A Dynamic |
Name of the unit in the HIS/PAS |
|
-
OfficialId |
String |
N/A Dynamic |
The official id of the unit. E.g.
HER id |
|
AccessLevel |
Number |
4 byte |
What access user have to the unit.
Accesslevel: 0 is no access (False) and >0 is has access. (True > 0) AccessLevel can have different
values above 0 to give the user different access to unit. Infomedix: Return a value between 0 and 8 where 0 is no access, and 1 is has
minimum access and graded to 8 for full access HIS90/CLASSIC: Return a value between 0 and 9 where 0 is no access, and 1 is has
minimum access and graded to 9 for full access(super user access). |
|
ParentUnidId |
Number |
4 byte |
This unit's parentid. Used for
hierarchial reference of units. Omitted if no reference to parent is needed.
If blank then top level or root unit. |
|
ParentUnitOfficialId |
String |
N/A Dynamic |
The official id of the unit. E.g.
HER id HIS90 systems only. |
|
|
|
|
|
|
AllUnits |
Boolean |
N/A |
Set to true if loggen on user has
access to all unit – whole organization structure. Super user. HIS90 systems only. |
|
MedicalUnits |
|
|
Collection of MedicalUnit, HIS90
systems only. |
|
MedicalUnit * xxx |
MedicalUnit;
the structure below is repeated xxx times. where xxx is valid from 0 to
endless/undetermined See useraccess.xsd scheme |
||
|
-
Id |
Number |
4 byte |
Internal
id/number for the unit in the system. |
|
-
ShortNameId |
String |
N/A Dynamic |
Short name or code for the unit |
|
-
Name |
String |
N/A Dynamic |
Name of the unit in the HIS/PAS |
|
-
OfficialId |
String |
N/A Dynamic |
The official id of the unit. E.g.
HER id |
|
|
|
|
|
|
Institution |
|
|
Organization/Institution
user has belongs to to. |
|
-
Id |
Number |
4 byte |
Internal
id/number for the Organization/Institution in the system. |
|
-
ShortNameId |
String |
N/A Dynamic |
Short name or code for the Organization/Institution |
|
-
Name |
String |
N/A Dynamic |
Name of the Organization/Institution in the HIS/PAS |
|
-
OfficialId |
String |
N/A Dynamic |
The official id of the Organization/Institution. E.g. HER id |
Schema for UserUnitAccesses : UserAccess.xsd
Schema
documentation for UserUnitAccesses :
UserAccess.html
Sample xml
file for UserUnitAccesses : UserUnitAccesses.xml
Web Service Response and Request:
See https://linkws.service.tieto.com/PasLinkWS/AuthorizationWS/AuthorizationWS.asmx?op=GetUserUnitAccess
Related
methods or functions used:
GetUserLogin Used
to verify as user, and to get a valid authentication Block in return.
Other
references:
RequestHeader Information required calling a method, containing
authentication information.
ResponseHeader Information and messages returned from the method, e.g.
error codes/description,
system name or version.
Comments:
To use this
method the RequestHeader must contain
a valid Authentication Block and the system name is required. An error will be
raised if one of these is missing.
Valid
Authentication Block for RequestHeader
the can be retrieved by using the method GetUserLogin
in Authentication-Web Service.
In return
form the method there will always be a ResponseHeader,
which contains Error Information and System Information. Error Information
block must always be checked to determine if any error has occurred while
processing the methods.
HIS90 GetUserUnitAccess
details and access control
For HIS90
the selection of units the user have access to in a patient context(the
patient’s official id is goven in request) is controlled by the access level
set in the functional access(Bilde) QPAS. (Use method GetUserServiceAccess to get/check this)
The rules
for GetUserUnitAccess and QPAS access level in HIS90 are:
|
QPAS access
level |
Description |
|
0 |
No unit
will be listed, user have no access. |
|
1,2,5 or
9 |
If
patient is admitted all units at the logged on user medical unit/department
will be listed. If
patient is NOT admitted the user will get no access to any units, the logged
on user has no access to the patient (or units in patient context) if the
patient is not admitted. |
|
3 or 4 |
All units
the user is authorized within EASY(security system) for will be listed |
|
6 |
If
patient is admitted or has an active waiting list at the logged on users
medical unit/department then all units within PAS will be listed. If
patient is NOT admitted and NOT have an active waiting list at the logged on
users medical unit/department then all units the user is authorized within
EASY(security system) for will be listed |
|
7 |
All units
at the logged on user medical unit/department will be listed. |
|
8 |
All units
within PAS will be listed. |
Infomedix GetUserUnitAccess details and access control
For
Infomedix the selection of units the user have access to is controlled by the
accesstemplate of the calling user. The accesstemplate describes which units
the user have access to and with which accesslevel.
Applicable
systems for method:
|
HIS90 |
|
|
|
|
|
|
Description:
The method
is used for getting users functional rights.
HIS90: For HIS-90 this means only users private
functional rights that are in addition to functional rights that are given by
role/group authorization.
Syntax:
GetUserServiceAccessesResponse
=
GetUserServiceAccesses(GetUserServiceAccessesRequest)
|
Parameter
in |
Type |
Length
byte |
Description
– Data format – Valid data |
|
GetUserServiceAccessesRequest |
|
N/A Dynamic |
GetUserServiceAccessesRequest class according to XML schema Authorization.xsd. .
|
|
Returned
parameter |
Type |
Length
Byte |
Description
– Comments |
|
GetUserServiceAccessesResponse |
|
N/A Dynamic |
GetUserServiceAccessesResponse class according to XML schema Authorization.xsd. |
Schema for
GetUserServiceAccessesRequest: Authorization.xsd
Schema
documentation for GetUserServiceAccessesRequest: GetUserServiceAccessesRequest.html
XML
sample file for GetUserServiceAccessesRequest: GetUserServiceAccessesRequest.xml
Schema for
GetUserServiceAccessesResponse: Authorization.xsd
Schema
documentation for GetUserServiceAccessesResponse: GetUserServiceAccessesResponse.html
XML
sample file for GetUserServiceAccessesResponse: GetUserServiceAccessesResponse.xml
Web Service Response and Request:
Other
references:
RequestHeader Information required calling a method, containing
authentication information.
ResponseHeader Information and messages returned from the method, e.g.
error codes/description,
system name or version.
Comments:
To use this
method the RequestHeader
must contain a valid Authentication Block and the system name is required. An
error will be raised if one of these is missing.
Valid
Authentication Block for RequestHeader
the can be retrieved by using the method GetUserLogin
in Authentication-Web Service.
In return
from the method there will always be a ResponseHeader,
which contains Error Information and System Information. Error Information
block must always be checked to determine if any error has occurred while
processing the methods.
HIS90 Specified information.
Server ACO11 is used for retrieving
user’s individual accesses and authorization that are in addition to user’s
category/role. The server gets users information from Easy-file ACDENBI (EN persons autorisasjon til BIlder).
In case of user service accesses
found the server issues following message: GetUser
ServiceAccesses – ok. If noting is found the message ENBI-post finnes ikke is issued.
For using the GetUserServiceAccesses method the user must have PWS1 level larger than 4. This restriction is
implemented in the WebService and not in the server.
Applicable
systems for method:
|
HIS90 |
|
|
|
|
|
|
Description:
The
method is used for saving/modifying users functional rights.
HIS90: For HIS-90 this means users private functional
rights that are in addition to functional rights given by role/group
authorization.
Syntax:
SaveUserServiceAccessesResponse
=
SaveUserServiceAccesses(SaveUserServiceAccessesRequest)
|
Parameter
in |
Type |
Length
byte |
Description
– Data format – Valid data |
|
SaveUserServiceAccessesRequest |
|
N/A Dynamic |
SaveUserServiceAccessesRequest class according to XML schema Authorization.xsd. .
|
|
Returned
parameter |
Type |
Length
Byte |
Description
– Comments |
|
SaveUserServiceAccessesResponse |
|
N/A Dynamic |
SaveUserServiceAccessesResponse class according to XML schema Authorization.xsd. |
Schema for
SaveUserServiceAccessesRequest: AuthorizationWS.xsd
Schema
documentation for SaveUserServiceAccessesRequest: SaveUserServiceAccessesRequest.html
XML
sample file for SaveUserServiceAccessesRequest: SaveUserServiceAccessesRequest.xml
Schema for
SaveUserServiceAccessesResponse: AuthorizationWS.xsd
Schema
documentation for SaveUserServiceAccessesResponse: SaveUserServiceAccessesResponse.html
XML
sample file for SaveUserServiceAccessesResponse: SaveUserServiceAccessesResponse.xml
Web Service Response and Request:
Related
methods or functions used:
GetUserServiceAccesses Method GetUserServiceAccesses
is to be used in conjunction with SaveUserServiceAcceses. When creating or
modifying user functional rights metod GetUserServiceAccesses is first to be
used and the result with new or modified right’s piped to
SaveUserServiceAccesses.
Other
references:
RequestHeader Information required calling a method, containing
authentication information.
ResponseHeader Information and messages returned from the method, e.g.
error codes/description,
system name or version.
Comments:
To use this
method the RequestHeader
must contain a valid Authentication Block and the system name is required. An
error will be raised if one of these is missing.
Valid
Authentication Block for RequestHeader
the can be retrieved by using the method GetUserLogin
in Authentication-Web Service.
In return
from the method there will always be a ResponseHeader,
which contains Error Information and System Information. Error Information
block must always be checked to determine if any error has occurred while
processing the methods.
HIS90 Specified information.
Server
ACO11S is used for creating/modifying
users individual accesses and authorizations that are in addition to the
users authorization accourding to role/category. The Easy-file
ACDENBI (EN persons autorisasjon til
BIlder) is uppdated by the server.
This is done by saving a number 1-9 (access-level) for each of 200 bilder that
are actual for the induvidual authorization.
Follwing message is issued when the
server runs without an error: SaveUser
ServiceAccesses – ok. In case of error follwing error message can be in
output: Oppgitt avdeling finnes ikke.
For using the SaveUserServiceAccesses method the user must have PWS1 level larger than 6. This restriction is
implemented in the WebService and not in the server.
Applicable
systems for method:
|
HIS90 |
|
|
|
|
|
|
Description:
The method
is used for getting users authorizations access rights (accourding to
role/group).
Syntax:
GetUserAuthorizationResponse
=
GetUserAuthorizations(GetUserAuthorizationRequest)
|
Parameter
in |
Type |
Length
byte |
Description
– Data format – Valid data |
|
GetUserAuthorizationRequest |
|
N/A Dynamic |
GetUserAuthorizationRequest class according to XML schema Authorization.xsd. .
|
|
Returned
parameter |
Type |
Length
Byte |
Description
– Comments |
|
GetUserAuthorizationResponse |
|
N/A Dynamic |
GetUserAuthorizationResponse class according to XML schema Authorization.xsd. |
Schema for
GetUserAuthorizationRequest: AuthorizationWS.xsd
Schema
documentation for GetUserAuthorizationRequest: GetUserAuthorizationRequest.html
XML
sample file for GetUserAuthorizationsRequest: GetUserAuthorizationRequest.xml
Schema for
GetUserAuthorizationsResponse: AuthorizationWS.xsd
Schema
documentation for GetUserAuthorizationResponse: GetUserAuthorizationResponse.html
XML
sample file for GetUserAuthorizationResponse: GetUserAuthorizationResponse.xml
Web Service Response and Request:
Related
methods or functions used:
SaveUserAuthorizations Method
GetUserAuthorizations is used by SaveUserAuthorizations when users
authorizations and accesses are to be modified
Other
references:
RequestHeader Information required calling a method, containing
authentication information.
ResponseHeader Information and messages returned from the method, e.g.
error codes/description,
system name or version.
Comments:
To use this
method the RequestHeader
must contain a valid Authentication Block and the system name is required. An
error will be raised if one of these is missing.
Valid
Authentication Block for RequestHeader
the can be retrieved by using the method GetUserLogin
in Authentication-Web Service.
In return
from the method there will always be a ResponseHeader,
which contains Error Information and System Information. Error Information
block must always be checked to determine if any error has occurred while
processing the methods.
HIS90 Specified information.
Server
ACO10 is used for getting user accesses and authorization. The Server gets it
sinformation from the Easy-file ACDENPE (EN persons PErsonlige
autorisasjon).
For using the GetUserAuthorization
method the user must have PWS1 level larger than 4. This restriction is
implemented in the WebService and not in the server.
Applicable
systems for method:
|
HIS90 |
|
|
|
|
|
|
Description:
The method
is used for saving/modifying authorizations and accesses (acourding to
role/group).
Syntax:
SaveUserAuthorizationResponse
=
SaveUserAuthorizations(SaveUserAuthorizationRequest)
|
Parameter
in |
Type |
Length
byte |
Description
– Data format – Valid data |
|
SavetUserAuthorizationRequest |
|
N/A Dynamic |
SavetUserAuthorizationRequest class according to XML schema Authorization.xsd. .
|
|
Returned
parameter |
Type |
Length
Byte |
Description
– Comments |
|
SavetUserAuthorizationResponse |
|
N/A Dynamic |
SavetUserAuthorizationResponse class according to XML schema Authorization.xsd. |
Schema for
SavetUserAuthorizationRequest: AuthorizationWS.xsd
Schema
documentation for SaveUserAuthorizationRequest: SaveUserAuthorizationRequest.html
XML
sample file for SavetUserAuthorizationRequest: SaveUserAuthorizationRequest.xml
Schema for
SavetUserAuthorizationResponse: AuthorizationWS.xsd
Schema
documentation for SaveUserAuthorizationResponse: SaveUserAuthorizationResponse.html
XML
sample file for SaveUserAuthorizationResponse: SaveUserAuthorizationResponse.xml
Web Service Response and Request:
Related
methods or functions used:
GetUserAuthorizations The method is used by SaveUserAuthorizations to
validate if users
authorizations/accesses are to be modified or created.
Other
references:
RequestHeader Information required calling a method, containing
authentication information.
ResponseHeader Information and messages returned from the method, e.g.
error codes/description,
system name or version.
Comments:
To use this
method the RequestHeader
must contain a valid Authentication Block and the system name is required. An
error will be raised if one of these is missing.
Valid
Authentication Block for RequestHeader
the can be retrieved by using the method GetUserLogin
in Authentication-Web Service.
In return
from the method there will always be a ResponseHeader,
which contains Error Information and System Information. Error Information
block must always be checked to determine if any error has occurred while
processing the methods.
HIS90 Specified information.
Server
ACO10S is used for modifying user accesses and authorization. The Server
creates/modifies information in
Easy-file ACDENPE (EN persons PErsonlige
autorisasjon).
In case of successfully run following
message is issued: SaveUser Authorization
Ok
Else following error messages can be
in output.
|
Message |
Comment |
|
Angi
signatur |
Signature
missing |
|
Ikke
godkjent signatur |
Signature
not valid |
|
Ikke
'X' i signaturen |
Not
’X’ in signature |
|
Oppgi
FROM-Dato |
From date missing |
|
Oppgi
TOM-Dato |
To
date missing |
|
TOM-Dato må være større
enn FOM-Dato |
To
date must be larger than to date |
|
Ukjent
kategori |
Unknown
category |
|
Du har feil aut.nivå for å
legge inn denne kategorien |
User
trying to saving/modifying authorization has not a valid authorization level. |
|
Avdeling
må oppgis! |
Medical
unit missing |
|
Rapp.skriver kan ha maks. 4
tegn |
Report
writer has more than 4 char |
|
Brev.skriver kan ha maks. 4
tegn |
Letter
writer ahs more than 4 char |
|
Giro.skriver kan ha maks. 4 tegn |
Giro
writer has more than 4 char |
|
Kassekode kan ha maks. 2
tegn |
Cash
code can have max 2 char |
|
Etik.skriver kan ha maks. 4 tegn |
Etikett
writer has more than 4 char |
|
Avdeling
mangler! |
Medical
unit missing |
|
Feil ved kontroll av
avdeling! |
Error
when controlling medical unit |
|
Enhet
mangler |
Care
Unit missing |
|
Feil ved kontroll av enhet |
Error
when controlling Care Unit |
|
Skriver
mangler! |
Writer
missing |
|
Feil ved kontroll av
brevskriver! |
Error
when controlling letter writer |
|
Feil ved kontroll av
giroskriver! |
Error
when controlling giro writer |
|
Feil
kassekode! |
Wrong
cash code |
|
Feil ved kontroll av
etikettskriver! |
Error
when controlling etikett writer |
|
Feil ved kontroll av
gruppe! |
Error
when controlling group |
|
Feil
autorisasjonsgruppe! |
Wrong
authorization group/access template. |
|
Du har ikke tilgang til
alle enheter! |
Operator
has not authorization to give user access to all units requested. |
|
|
|
All messages starting with ’Feil’ are
usually general sql errors and can be slowed by compiling the server.
For using the SaveUserAuthorization
method the user must have PWS1 level larger than 6. This restriction is
implemented in the WebService and not in the server.
Which roles
can be given/set by the logged on user
The logged on user can only apply
roles(categories) dependent on the authority of the user himself.
The rules for which roles the user
can apply are:
Applicable
systems for method:
|
HIS90 |
|
|
|
|
|
|
Description:
The method
is used for listing all service accesses that are accessible for a system.
Syntax:
ListServiceAccessesResponse
= ListServiceAccesses(ListServiceAccessesRequest)
|
Parameter
in |
Type |
Length
byte |
Description
– Data format – Valid data |
|
ListServiceAccessesRequest |
|
N/A Dynamic |
ListServiceAccessesRequest class according to XML schema Authorization.xsd. .
|
|
Returned
parameter |
Type |
Length
Byte |
Description
– Comments |
|
ListServiceAccessesResponse |
|
N/A Dynamic |
ListServiceAccessesResponse
class according to XML schema Authorization.xsd. |
Schema for
ListServiceAccessesRequest: AuthorizationWS.xsd
Schema
documentation for ListServiceAccessesRequest: ListServiceAccessesRequest.html
XML
sample file for ListServiceAccessesRequest: ListServiceAccessesRequest.xml
Schema for
ListServiceAccessesResponse: AuthorizationWS.xsd
Schema
documentation for ListServiceAccessesResponse: ListServiceAccessesResponse.html
XML
sample file for ListServiceAccessesResponse: ListServiceAccessesResponse.xml
Web Service Response and Request:
Related
methods or functions used:
Other
references:
RequestHeader Information required calling a method, containing
authentication information.
ResponseHeader Information and messages returned from the method, e.g.
error codes/description,
system name or version.
Comments:
To use this
method the RequestHeader
must contain a valid Authentication Block and the system name is required. An
error will be raised if one of these is missing.
Valid
Authentication Block for RequestHeader
the can be retrieved by using the method GetUserLogin
in Authentication-Web Service.
In return
from the method there will always be a ResponseHeader,
which contains Error Information and System Information. Error Information
block must always be checked to determine if any error has occurred while
processing the methods.
HIS90 Specified information.
The server
PWLA02 – service PWS0940 is used for listing all bilder (number and names) for
a given system.
The service
reads from sql-table PAQFUNC (PAS), Klinsik-lab tabel
KKQFUNC and Mikrolab-tabellen =MLQFUNC, depending on system in input (PA, KK,
ML).
Applicable
systems for method:
|
HIS90 |
|
|
|
|
|
|
Description:
The method
is used for listing all categories (roles) found in a system.
HIS90: Se HIS90 spesific information about scope for
this method.
Syntax:
ListRolesResponse
= ListRoles(ListRolesRequest)
|
Parameter
in |
Type |
Length
byte |
Description
– Data format – Valid data |
|
ListRolesRequest |
|
N/A Dynamic |
ListRolesRequest class according to XML schema Authorization.xsd. .
|
|
Returned
parameter |
Type |
Length
Byte |
Description
– Comments |
|
ListRolesResponse |
|
N/A Dynamic |
ListRolesResponse
class according to XML schema Authorization.xsd. |
Schema for
ListRolesRequest: AuthorizationWS.xsd
Schema
documentation for ListRolesRequest: ListRolesRequest.html
XML
sample file for ListRolesRequest: ListRolesRequest.xml
Schema for
ListRolesResponse: AuthorizationWS.xsd
Schema
documentation for ListRolesResponse: ListRolesResponse.html
XML
sample file for ListRolesResponse: ListRolesResponse.xml
Web Service Response and Request:
See https://linkws.service.tieto.com/PasLinkWS/AuthorizationWS/AuthorizationWS.asmx?op=ListRoles
Related
methods or functions used:
Other
references:
RequestHeader Information required calling a method, containing
authentication information.
ResponseHeader Information and messages returned from the method, e.g.
error codes/description,
system name or version.
Comments:
To use this
method the RequestHeader
must contain a valid Authentication Block and the system name is required. An
error will be raised if one of these is missing.
Valid
Authentication Block for RequestHeader
the can be retrieved by using the method GetUserLogin
in Authentication-Web Service.
In return
from the method there will always be a ResponseHeader,
which contains Error Information and System Information. Error Information
block must always be checked to determine if any error has occurred while
processing the methods.
HIS90 Specified information.
Server
ACO07 is used by the service for getting Role/Category information from Easy. The server lists information from Easy-file
ACDKABI ((KAtergori
BIldekobling) and for each record serviceaccessname(bildenavn)
from Easy-file ACDBILD is listed.
Listing all roles(categories) including all serviceacessess(bilder) for the role put 9999
into the RoleId in request. If RoleId=9999 the all roles are listed else only
the selected role(category) is retrieved.
Following message is given when no
error has occurred: ListCategories ok, else
the error message is Kategori finnes ikke.
ListRoles for HIS-90 will not list
all roles found in selected system, but roles dependent on the authority of the
user himself.
The rules for which roles are
listed:
Applicable
systems for method:
|
HIS90 |
|
|
|
|
|
|
Description:
The method
is used for listing all authorizationsgroups in a system that eventually are
linked to selected department/medical speciality.
Syntax:
ListAccessTemplatesResponse
= ListAccessTemplates(ListAccessTemplatesRequest)
|
Parameter
in |
Type |
Length
byte |
Description
– Data format – Valid data |
|
ListAccessTemplatesRequest |
|
N/A Dynamic |
ListAccessTemplatesRequest class according to XML
schema Authorization.xsd. .
|
|
Returned
parameter |
Type |
Length
Byte |
Description
– Comments |
|
ListAccessTemplatesResponse |
|
N/A Dynamic |
ListAccessTemplatesResponse class according to XML schema Authorization.xsd. |
Schema
for ListAccessTemplatesRequest: AuthorizationWS.xsd
Schema
documentation for ListAccessTemplatesRequest : ListAccessTemplatesRequest.html
XML
sample file for ListAccessTemplatesRequest : ListAccessTemplatesRequest.xml
Schema for
ListAccessTemplatesResponse: AuthorizationWS.xsd
Schema
documentation for ListAccessTemplatesResponse: ListAccessTemplatesResponse.html
XML
sample file for ListAccessTemplatesResponse: ListAccessTemplatesResponse.xml
Web Service Response and Request:
Related
methods or functions used:
Other
references:
RequestHeader Information required calling a method, containing
authentication information.
ResponseHeader Information and messages returned from the method, e.g.
error codes/description,
system name or version.
Comments:
To use this
method the RequestHeader
must contain a valid Authentication Block and the system name is required. An
error will be raised if one of these is missing.
Valid
Authentication Block for RequestHeader
the can be retrieved by using the method GetUserLogin
in Authentication-Web Service.
In return
from the method there will always be a ResponseHeader,
which contains Error Information and System Information. Error Information
block must always be checked to determine if any error has occurred while
processing the methods.
HIS90 Specified information.
Server
PWLA03 – service PWS0950 is used to list access templates. The service lists
all authorization groups that are associated to selected Medical Units and Care
Units. If Medical Unit is in input all groups with associated Care Units that
are part of Medical Unit will be listed, else all Medical Units, groups and
Care Units are listed. Authorization groups are found in table ACQUSAC. The same Care Unit can be part of more thane one authorization
group. The same group can be part of
more than one Medical Unit.
In following example group SYK is
defined both for Medical Unit BARN and Medical Unit KIR. Care Unit KIRS01 is
part of group SYK and group SYK2.