Overview
The iSalusEMR.ProblemPatient webservice is used to obtain a list of diagnosis and corresponding data for the diagnosis from the Problem List chart tab for a given patient. This can be found here: EMR > Select Patient > Problem List. The webservice will accept a patient ID as an input and the entire problem object will be returned.
Sample Call
Request
<request><security><key>REDACTED</key><version>1.0</version><userid /><account>REDACTEDC</account></security><patient_id>9388</patient_id></request>
Response
<response xmlns="http://www.isalushealthcare.webservices/">
<auto_queue>0</auto_queue>
<icd10_conversion_ind>N</icd10_conversion_ind>
<icd_mode>ICD10</icd_mode>
<patient_id>9388</patient_id>
<patient_problem_list>
<list_item>
<problem_list_id>76</problem_list_id>
<priority>14</priority>
<description>Essential (primary) hypertension</description>
<code_id>34523</code_id>
<code>I10</code>
<onset_date>10/30/2009</onset_date>
<created_by>Administrator, Local</created_by>
<short_description>Essential (primary) hypertension</short_description>
<problem_description>Essential (primary) hypertension</problem_description>
<problem_list_status_code>1</problem_list_status_code>
<problem_list_status_desc>Active</problem_list_status_desc>
<note_list>
<note_item>
<problem_list_note_id>16</problem_list_note_id>
<note>uncontrolled, poor compliance</note>
<creation_date>03/02/2011</creation_date>
<note_by>Head, Blake</note_by>
<note_security_users_id>89</note_security_users_id>
</note_item>
<note_item>
<problem_list_note_id>10</problem_list_note_id>
<note>Doing better now that he is taking his meds and exercising as recommended.</note>
<creation_date>02/14/2011</creation_date>
<note_by>Head, Blake</note_by>
<note_security_users_id>89</note_security_users_id>
</note_item>
</note_list>
<modified>N</modified>
<interaction>
<medication_list>
<medication_item>
<med_concept_id>260058</med_concept_id>
<med_concept_id_typ>3</med_concept_id_typ>
<med_concept_id_desc>Adderall XR 10 mg capsule,extended release</med_concept_id_desc>
<disease_severity_level>2</disease_severity_level>
</medication_item>
</medication_list>
</interaction>
<post_date>03/03/2011 10:40AM (EDT)</post_date>
<chronic_ind>Y</chronic_ind>
</list_item>
<list_item>
<problem_list_id>516</problem_list_id>
<priority>15</priority>
<description>Attn-defct hyperactivity disorder, predom hyperactive type</description>
<code_id>83902</code_id>
<code>F901</code>
<onset_date>04/08/2014</onset_date>
<created_by>Wundt, Wilhelm</created_by>
<short_description>Attn-defct hyperactivity disorder, predom hyperactive type</short_description>
<problem_list_status_code>1</problem_list_status_code>
<problem_list_status_desc>Active</problem_list_status_desc>
<note_list>
<note_item>
<problem_list_note_id>249</problem_list_note_id>
<note>started on medication. Recheck next time.</note>
<creation_date>04/08/2014</creation_date>
<note_by>Wundt, Wilhelm</note_by>
<note_security_users_id>212</note_security_users_id>
</note_item>
</note_list>
<modified>N</modified>
<post_date>04/08/2014 2:11PM (EDT)</post_date>
<snomed_conceptid>698692009</snomed_conceptid>
<chronic_ind>Y</chronic_ind>
</list_item>
...
</patient_problem_list>
<patient_history_list>
<list_item>
<problem_list_id>267</problem_list_id>
<priority>10</priority>
<description>Rheumatic heart failure</description>
<code_id>34520</code_id>
<code>I0981</code>
<onset_date>03/11/2011</onset_date>
<created_by>Head, Blake</created_by>
<short_description>Rheumatic heart failure</short_description>
<problem_list_status_code>1</problem_list_status_code>
<problem_list_status_desc>Active</problem_list_status_desc>
<note_list>
<note_item>
<problem_list_note_id>62</problem_list_note_id>
<note>Activated</note>
<creation_date>06/09/2011</creation_date>
<note_by>Nemeth, Phil</note_by>
<note_security_users_id>141</note_security_users_id>
</note_item>
</response>
Element Description
Request
The Request element will serve as a wrapper for the entire body of the XML request.
Request > Security
See documentation for the Security node here: Access to Webservices
Request > Patient_ID
Chat number for the patient data you would like to retrieve.
Response
The Response element will server as a wrapper for the entire body of the XML response.
Response > Auto_Queue
Depreciated.
Response > ICD_Conversion_Indicator
Depreciated. Should always be set to N. Used in the past for converting ICD-9 to ICD-10.
Response > ICD_Mode
Should always be set to ICD10. Used in the past for converting ICD-9 to ICD-10.
Response > patient_id
Echoed patient_id from original request.
Response > patient_problem_list
This will serve as a wrapper for all items that are on the patient's active problem list. All inactive items can be found in the <patient_history_list> section.
Response > patient_problem_list > List_item
This will serve as a wrapper for all details related to a problem. This will repeat for each problem in the list.
Response > patient_problem_list > List_item > Problem_list_id
Internal ID used to identify this unique entry.
Response > patient_problem_list > List_item > Priority
The priority of this problem list item for this patient.
Response > patient_problem_list > List_item > Description
Name of the problem as defined by the user who entered it. This is subject to change from patient to patient even for the same problem.
Response > patient_problem_list > List_item > Code_id
Internal Id used to identify the outward facing code for this problem.
Response > patient_problem_list > List_item > Code
The ID used to identify this condition - this is usually an ICD-9 or ICD-10 code.
Response > patient_problem_list > List_item > Onset_Date
The date of onset for the given condition.
Response > patient_problem_list > List_item > Created_By
Name of the user that added the problem to the problem list. Formatted as Last Name, First Name.
Response > patient_problem_list > List_item > Short_Description
Short description for the code used to identify this problem. This description does not change from patient to patient for the given code.
Response > patient_problem_list > List_item > Problem_List_Status_code
Encoded value for the status of the problem.
- 1 = Active
- 2 = Inactive
- 3 = Resolved
- 4 = Removed
Response > patient_problem_list > List_item > Problem_List_Status_Desc
Description of the problem list status.
Response > patient_problem_list > List_item > Note_List
Problems may have one to many notes that are added over time. The Note_List will serve as a wrapper for all note_items.
Response > patient_problem_list > List_item > Note_List > Note_item
The Note_Item will server as a wrapper for all of the note details.
Response > patient_problem_list > List_item > Note_List > Note_Item > Problem_list_note_id
The internal ID used to identify this specific note entry.
Response > patient_problem_list > List_item > Note_List > Note_Item > Note
The note that was typed in or created.
Response > patient_problem_list > List_item > Note_List > Note_Item > Creation_date
Date the note was entered.
Response > patient_problem_list > List_item > Note_List > Note_Item > Note_by
The user that entered the note. Formatted as Last, First.
Response > patient_problem_list > List_item > Note_List > Note_Item > Note_security_users_id
The internal ID that identifies the user.
Response > patient_problem_list > List_item > Modified
Indicator if the problem list item was modified today.
- N = No
- Y = Yes
Response > patient_problem_list > List_item > Interaction
Problems may interact with medications that a patient is prescribed to. This section will identify those conflicts. The Interaction node will serve as a wrapper for this section.
Response > patient_problem_list > List_item > Interaction > Medication_list
The list of medications that this problem interacts with will be housed in this section.
Response > patient_problem_list > List_item > Interaction > Medication_list > Medication_item
The medication_item node will serve as a wrapper for all details related to the medication that is interacting with this problem.
Response > patient_problem_list > List_item > Interaction > Medication_list > Medication_item > Med_concept_id
The MedConcept ID for the medication as defined by First Data Bank.
Response > patient_problem_list > List_item > Interaction > Medication_list > Medication_item > Med_concept_id_typ
The MedConcept type for the medication.
Response > patient_problem_list > List_item > Interaction > Medication_list > Medication_item > Med_concept_id_desc
The name of the medication.
Response > patient_problem_list > List_item > Interaction > Medication_list > Medication_item > Disease_severity_level
The severity of the interaction between the problem and the identified medication.
- 1 = Sever
- 2 = Moderate
- 3 = Interaction
Response > patient_problem_list > List_item > Post_date
Date/Time the problem was added into the application.
Response > patient_problem_list > List_item > Chronic_ind
Indicator if the specified problem is considered to be a chronic aliment.
- Y = Yes (chronic)
- N = No (not chronic)
Response > patient_history_list
The Patient_History_List node contains all problems for a patient that are no longer considered Active. The sub elements of this node follow the same schema as defined above.
