You are viewing an old version of this content. View the current version.
Compare with Current
View Version History
« Previous
Version 63
Next »
Function prototype | case_get_contact ( session , case, [subscription] , [admission], [mode]) |
---|
API Version | ALL |
---|
Supported interfaces | SOAP |
---|
Returns personal data of a CASE
The case reference can be any of the references obtained from a case_get(). Be aware that passing two different references from the same source will return the same values (is only an alternate identifier). If the parameter case is null, the function returns an empty XML template.
The data included in the response is determined by one of the CASE FORMAT SETTINGS (FORMAT.CASE or FORMAT.CASE.NEW)
Required permissions: The active user must have role XXXX. Otherwise an INSUFFICIENT_PRIVILEGES error will be returned.
Input parameters: | session: is the token obtained in the session_init call case: Reference of the case. It is possible to indicate a reference of the patient in an external system if the format of the reference meets the rules defined in External user references subscription: specify the subscription to obtain only the CONTACT fields defined in the FORMAT SETTINGS of the subscription admission*: specify the admission in which the case is part of. This field will be deprecated in the future. It was provided as an indirect way to obtain the subscription mode (optional, default = 'edit'): Indicate which FORMAT SETTINGS should be used to determine the contact data that must be included in the response. Introduced in API Version 2.7.29 Possible values:
|
Output parameters: | result: an XML with personal data stored at the @source system ref: CASE reference username editable: (true/false) Indicates if the contact data of the CASE is editable by the active USER pictures: identifiers/identifier: list of IDENTIFIER OBJECT of the CASE description: Description of the IDENTIFIER in the active SESSION language label: label of the IDENTIFER (e.g. NAT_ES) value: value assigned to the IDENTIFIER image_ref: Reference of the image associated to the IDENTIFIER. This reference can be used in the function image_get () to retrieve the image bytes. auto_generated: (true/false) Indicates if the value of the IDENTIFIER has been generated automatically by the API. Auto-generated IDENTIFIERS cannot be modified. Introduced in API version 2.7.21 validation_id: String that represent this IDENTIFIER used for validation purposes. This field is generally equal to the label value except when the IDENTIFIER is a SUBSCRIPTION IDENTIFIER because it is necessary to distinguish the same IDENTIFIER across different SUBSCRIPTIONs. When the function case_validate () is invoked it returns a list of error in a structure of type CONTACT DATA VALIDATION, where each field with errors ir referenced by an ID that matches the validation_id, what allows to locate unequivocally the problematic field. Introduced in API version 2.7.18 group: Name of the group to which the IDENTIFIER belongs. This value is generated only when there exist a FORMAT SETTINGS that specify a list of IDENTIFIERS that belong to the same logical group. All IDENTIFIERS belonging to the same group will have the same group name. Introduced in API version 2.7.21 admission_status: Only returned in SUBSCRIPTION IDENTIFIERS. Indicates the status of the most recent ADMISSION to which this IDENTIFIER is bound. When an ADMISSION is finished (DISCHARGED or REJECTED), it is not possible to modify the value of the IDENTIFIER. program: (only in IDENTIFIER OBJECT that are associated to a SUBSCRIPTION). Introduced in API version 2.7.18 team: (only in IDENTIFIER OBJECT that are associated to a SUBSCRIPTION). Introduced in API version 2.7.18 ref: TEAM reference code: TEAM Code. name: TEAM name
editable: (true/false) Indicates whether the information about this IDENTIFIER is editable by the active user. Introduced in API Version 2.7.24 source: Indicates whether the information has been imported from an external source. If null, the data has been created directly in Linkcare platform. Otherwise the source will be an ID indicating the HIS from which the information was imported. Introduced in API Version 2.7.24
full_name: Concatenation of the name and surnames of the contact. If the name or surname contain Chinese characters, then the full name is the concatenation of the surname and name informal_name: Normally consists on name of the contact. If the name or surname contain Chinese characters, then the full name is the concatenation of the surname and name. Introduced in API Version 2.7.24 data: additional data bdate: information about the birthdate or age of the contact. Modified in API Version 2.7.25 (in previous versions it was a scalar value) bdate: Date of birth in format yyyy-mm-dd age: Age in years editable: (true/false) Indicates whether the information about Birthdate (or age) is editable by the active user. source: Indicates whether the information has been imported from an external source. If null, the data has been created directly in Linkcare platform.
gender: Information about the gender of the contact. Modified in API Version 2.7.25 (in previous versions it was a scalar value) gender: Male (M) or Female (F) editable: (true/false) Indicates whether the information about Gender is editable by the active user. source: Indicates whether the information has been imported from an external source. If null, the data has been created directly in Linkcare platform.
nationality: Information about the nationality of the contact. Modified in API Version 2.7.25 (in previous versions it was a scalar value) ref: A valid 2 letter ISO 3166 country code. name: name of the nationality country in the active session language. editable: (true/false) Indicates whether the information about Nationality is editable by the active user. source: Indicates whether the information has been imported from an external source. If null, the data has been created directly in Linkcare platform.
name: Detailed information about the name of the CASE given_name middle_name: removed from API version 2.7.18
family_name family_name2: removed from API version 2.7.18
complete_name: Complete name specifically provided. Normally in occidental countries this name can be generated from the concatenation of the Given name and Family name, but some cultures prefer to provide a complete name instead of Given name and Surname. Introduced in API Version 2.7.24 editable: (true/false) Indicates whether the information about name is editable by the active user. Introduced in API Version 2.7.24 source: Indicates whether the information has been imported from an external source. If null, the data has been created directly in Linkcare platform. Otherwise the source will be an ID indicating the HIS from which the information was imported. Introduced in API Version 2.7.24
addresses: Detailed information about the addresses of the CASE can_add: (true/false) Indicates whether the active user can add or remove exiting addresses. Introduced in API Version 2.7.24 address: Information about each individual address of the contact. Introduced in API Version 2.7.24 editable: (true/false) Indicates whether the information about this address is editable by the active user. Introduced in API Version 2.7.24 source: Indicates whether the information has been imported from an external source. If null, the data has been created directly in Linkcare platform. Otherwise the source will be an ID indicating the HIS from which the information was imported. Introduced in API Version 2.7.24
channels: communication channels associated to the CASE
source: a case data source. By default is Linkcare internal System. If the source have data, the object “tag” cannot be edited by the front-end ErrorMsg: any 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 ErrorCode: If any error occurs, then this value contains any of the standard ERROR CODES
|
case_get_contact( “LCAAAAAAAAAAAA”, 10261)
<contact>
<ref>10261</ref>
<username>alex4234</username>
<editable>true</editable>
<pictures>
<insignia>
<ref>1</ref>
</insignia>
</pictures>
<identifiers>
<identifier>
<description>Participant Reference</description>
<label>PARTICIPANT_REF</label>
<value>0001</value>
<validation_id>PARTICIPANT_REF#243#1</validation_id>
<program>
<ref>243</ref>
<code>SPIRO</code>
<name>Spirometry study</name>
</program>
<team>
<ref>1</ref>
<code>LINKCARE</code>
<name>Linkcare</name>
</team>
<editable>true</editable>
<source/>
</identifier>
<identifier>
<description>NIF</description>
<label>NAT_ES</label>
<value>ALEXEY</value>
<validation_id>NAT_ES</validation_id>
<image_ref>3626</image_ref>
<editable>true</editable>
<source/>
</identifier>
<identifier>
<description>PASSPORT</description>
<label>PASS</label>
<value />
<validation_id>PASS</validation_id>
<editable>true</editable>
<source/>
</identifier>
</identifiers>
<full_name>Maria Rosa Gosa Imbern</full_name>
<data>
<bdate>
<bdate>1998-03-20</bdate>
<age>17</age>
<editable>true</editable>
<source/>
</bdate>
<gender>
<gender>F</gender>
<editable>true</editable>
<source/>
</gender>
<nationality>
<name>Spain</name>
<ref>ES</ref>
<editable>true</editable>
<source/>
</nationality>
</data>
<name>
<given_name>Maria Rosa</given_name>
<family_name>Gosa Imbern</family_name>
<complete_name></complete_name>
<editable>true</editable>
<source/>
</name>
<addresses>
<address>
<kind>Main Address</kind>
<street>Roger de LLuria</street>
<number>50</number>
<floor>SAT</floor>
<suite>A</suite>
<district />
<city>Barcelona</city>
<postcode>08009</postcode>
<state />
<country>España</country>
<comment />
<gps_map_url>http://maps.google.com/maps?q=Roger+de+Lluria%2C+50%2C+Barcelona%2C+%2C+08009%2C+Spain</gps_map_url>
<full_address>Roger de Lluria 50 SAT A, 08009 Barcelona, Barcelona, Spain</full_address>
<editable>true</editable>
<source/>
</address>
</addresses>
<channels>
<phones>
<channel_type>phone</channel_type>
<description>Teléfonos</description>
<phone>
<type>mobile</type>
<ref>1</ref>
<value>934546365</value>
<description>Móvil</description>
<comment />
<preferred>true</preferred>
<verified>true</verified>
<editable>true</editable>
<source/>
</phone>
<phone>
<ref>2</ref>
<type>ext</type>
<value>22</value>
<description>Ext.</description>
<comment />
<preferred>false</preferred>
<verified>false</verified>
<editable>true</editable>
<source/>
</phone>
<phone>
<ref>4</ref>
<type>work</type>
<value>935555555</value>
<description>Oficina</description>
<comment />
<preferred>false</preferred>
<verified>false</verified>
<editable>true</editable>
<source/>
</phone>
</phones>
<emails>
<channel_type>email</channel_type>
<description>Correo electrónico</description>
<email>
<ref>5</ref>
<type>work</type>
<value>PITIKLIN@LINKCARE.ES</value>
<description>Oficina</description>
<comment />
<preferred>true</preferred>
<verified>false</verified>
<editable>true</editable>
<source/>
</email>
<email>
<ref>6</ref>
<type>home</type>
<value>RPELAEZ@LINKCARE.ES</value>
<description>Casa</description>
<comment />
<preferred>false</preferred>
<verified>false</verified>
<editable>true</editable>
<source/>
</email>
</emails>
<aims>
<channel_type>aim</channel_type>
<description>Mensajería instantánea</description>
<aim>
<ref>7</ref>
<type>Skype</type>
<value>SKYPEUSER</value>
<description>Skype</description>
<comment />
<preferred>false</preferred>
<verified>false</verified>
<editable>true</editable>
<source/>
</aim>
</aims>
<device>
<channel_type>device</channel_type>
<description>Dispositivos</description>
<ref>8</ref>
<type>bluetooth</type>
<value>D898989</value>
<description>bluetooth</description>
<source />
<comment />
</device>
<devices />
</channels>
</contact>
ERROR CODE | |
---|
INVALID_TOKEN | The session token provided is not valid |
INSUFFICIENT_PRIVILEGES | The session user does not have the necessary privileges to … |
The Gender, Birthdate and Nationality information returned in versions before 2.7.27 had a different format:
2.7.24 and previous | 2.7.25 and newer |
---|
<data>
<bdate>1998-03-20</bdate>
<age>17</age>
<gender>F</gender>
<nationality>Spain</nationality>
<nationality_ref>ES</nationality_ref>
<editable>true</editable>
<source/>
</data>
|
<data>
<bdate>
<bdate>1998-03-20</bdate>
<age>17</age>
<editable>true</editable>
<source/>
</bdate>
<gender>
<gender>F</gender>
<editable>true</editable>
<source/>
</gender>
<nationality>
<name>Spain</name>
<ref>ES</ref>
<editable>true</editable>
<source/>
</nationality>
</data>
|