/
NEUTRAL POINT SERVICE

NEUTRAL POINT SERVICE

Introduction

  • The Linkcare Neutral Point (LC-NP) is a Linkcare service to allow mobile and web service clients to be able to log in to multiple Linkcare Servers. 
  • This feature makes possible to use a single App provider (i.e. google play) and avoid patients to be required to customise the system
  • When a Linkcare client is started, the LC-NP returns a DNS-like list of all the available LC Servers were the patient is registered
  • The Linkcare Neutral Point can also be installed as a Corporate Service, but in this case the health service provider must create a "white label" app, and patients will only be able to access the specific Health Care Service Provider with this "customised" app.

In this moment, the Linkcare Neutral Point Service is in https://mobile.linkcare.es/ws  and/or https://patient.mobile.linkcare.es/ws

The most important function in the Linkcare Neutral Point Service is:

SESSION_DISCOVER WS FUNCTION

Returns, if logged in properly, the token and the user id (both needed to call protected methods), an endpoint and other user info.

Discussion

Remember that the endpoint you get from the output parameters can be totally different to the one used to call this function, and you should use the retrieved one for every new calls associated to that user.

If you still don't have a specific endpoint or you don't know to which endpoint your user is associated, you may use this method to login correctly. Otherwise simply use session_init

This method has the same input and output structure of session_init

Input Parameters

userThe username
passwordThe password of the user
IPIP of the caller (the one who invokes this web service). If IP="", the system will try to determine automatically the remote connection IP
hostThe chosen identifier for the application (with its version)
languageThe language code in ISO format used by the device
current_dateThe actual date with hour and minutes in the local device  in american format YYYY-mm-dd HH:mm:ss
calendarThe type of calendar used by the device
deviceAn unique and immutable ID for the device
extraField with extra data (app version, OS version ej. {"app_version": 3.0.10, "android_version": 4.0.3})

Output Parameters

token

The session ID, needed to call protected method
userThe user ID (different from username), needed to call protected method
WSThe URL web service endpoint
languageDefault language for the user
nameThe name of the user
ErrorMsgany fault in the call, either in the validation of input parameters, errors in the connection to the database or any other error, this parameter returns the error message produced

Example

Request

sample:

session_discover ( “user”, “password”, "127.0.0.1",);

Response

sample:

<token xsi:type="xsd:string">LC**************.********</token>
<user xsi:type="xsd:string">0</user>
<WS xsi:type="xsd:string">http://dev.linkcare.es/ws/ServerWSDL.php</WS>
<language xsi:type="xsd:string">EN</language>
<name xsi:type="xsd:string">Demo</name>
<ErrorMsg xsi:type="xsd:string" />

Notes:


 

Related content