Function prototype	case_admission_list ( session, case ,[get],[subscription], [search_str])
API Version	2.7.11 and higher

Returns a list with the admissions of a case Only the ADMISSIONs in SUBSCRIPTIONS where the active user is member will be returned
Input parameters:	session: is the session id obtained in the session_init call case: is a case reference ID obtained by the URL or with the calls: case_list(), case_search() or case_get(). ( can be an external ID like SOURCE/ID/NNNN ) get: is an optional value. When true, admission_list retrieves the full admission data. When false, it retrieves only the admission ref. The default value is true. subscription: (default = null) If a subscription reference is provided, only the ADMISSIONS of that particular SUBSCRIPTION will be returned *search_str: (default = null) Allows to filter the list of ADMISSION. This parameter is a structured JSON expression to customize search. See below the JSON search expression format . This parameter is available from API version 2.7.15*
Output parameters:	*result: is an XML that contains the admission list admissions: admission objects with all fields in the XML status: status of the admission ACTIVE: An active admission ENROLLED: An admission not assigned to a PROTOCOL PREADMISSION: An admission assigned to a protocol with open admission forms PAUSED: An admission temporarily PAUSED REJECTED: An admission DISCHARGED: A discharged admission 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
Request sample:	case_admission_list( “LCAAAAAAAAAAAAAAAAAAA”, “{label:}case_id{@source}”, “true”);
Response sample:	<?xml version="1.0" encoding="utf-8" standalone="yes"?> <result> <admissions> <admission> <ref>{source/id/}16205</ref> <locked>true</locked> <refs> <next> <ref>{source/id/}16206</ref> </next> <prev> <ref /> </prev> </refs> <data> <case> <ref>{source/id/}10504</ref> </case> <subscription> <ref>111</ref> <version>12</version> <team> <ref>13</ref> <insignia>23</insignia> <name>CAP1</name> </team> <program> <id>15</id> <name>Seguimiento Post-Alta Hospitalaria (2012)</name> <description>Renewing Health Random</description> <prog_code>RENHEAL</prog_code> <image_info>{"resource_ref":14324,"description":"","mimeType":"jpg","code":"","scope":"PROGRAM"}</image_info> </program> </subscription> <enrol_date>2012-10-22 13:32:40</enrol_date> <admission_date>2012-10-22 13:33:52</admission_date> <discharge_request_date /> <discharge_date /> <suspended_date /> <rejected_date>2012-10-22 13:34:38</rejected_date> <notes /> <status>REJECTED</status> <date_to_display>2012-10-22 13:34:38</date_to_display> <age_to_display>31</age_to_display> <his_episode_ref /> <protocol> <id>1205</id> <name>Grupo de Intervención 3</name> <description>IG3. Renewing Health. Random</description> </protocol> </data> <performance> <compliance>5</compliance> <adherence>6</adherence> <outcome>4</outcome> </performance> </admission> </admissions> </result> <ErrorMsg></ErrorMsg>
Notes:	Replaces † admission_list_case ()

JSON search expression format

Starting at API version 2.7.15 It is possible to provide a JSON formatted string in the parameter search_str to customize the search of ADMISSIONs. The structure of the JSON string can contain:

Search by DATA_CODE: allows to search ADMISSIONs with FORMS that include an ITEM with a specific DATA CODE and the requested value assigned. It is mandatory to indicate the DATA_CODE name. To use this search type it is necessary to provide 2 values:
- code: name of the DATA_CODE (e.g. "BLOOD_O2").This parameter cannot be empty or it will be ignored.
- value: Value searched (the value assigned to the ITEM with the requested DATA_CODE)

The following example requests to search any ADMISSION of a CASE with a questionnaire that contains an ITEM with DATA_CODE="BLOOD_02" and with value "98"

{
  "data_code" : {
    "name": "BLOOD_O2",
    "value": "98"
  }
}

Browser not supported