ITI Technical Framework - IHE

More documents

Recommendations

Info

18051810IHE IT Infrastructure Technical Framework, Volume 2a (ITI TF-2a): Transactions Part A_________________________________________________________________________________3.11.3.3.2 Message SemanticsThe Retrieve Specific Information for Display transaction is performed by the invocation of a webservice. The Display Actor shall generate a web service request whenever a user needs to review theinformation stored as part of a patient’s clinical history on the Information Source Actor.To specify the type of information to be returned, a web service request shall include the followingparameters (keys) to filter the subset of information (See Table 3.11.4-7). All parameter names andvalues (see Table 3.11.4-7) are case-sensitive.Table 3.11.4-6 Web Service Request KeysParameter REQ Description NotesNamerequestType R requestType specifies what type ofinformation shall be retrieved. Thisparameter shall always be valued.patientID R This attribute identifies the subject ofthe results being queried for. Its valueshall include identification of assigningauthority.See Table 3.11.4-7 for the list of possible values.PatientID value shall be formatted as HL7 CX datatype (including assigning authority) according to therequirements specified for the Patient Identity Feedtransaction (see ITI TF-2a: 3.8.4.1.2.3)requestType valueLIST-ALLERGIESLIST-MEDSTable 3.11.4-7 Web Service Request TypesDescriptionList of allergies and adverse reactions for a patient known to the Information SourceList of medications currently taken by or administered to a patient181518201825Formal definition of the web service in WSDL is provided in the ITI TF-2x: Appendix A.The only binding required for both Display Actor and Information Source Actor is the binding to theHTTP-GET. In this binding the sample message will be formatted as follows:http:///IHERetrieveListInfo?requestType=LIST-MEDS&patientID=99998410^^^%26www.mlhlife.com%26DNSThe part of the URL is configurable by the implementation, and must contain the host name,an optional port address, and may be followed by an optional path. The path if present may not containa ‘?’ character. The remainder of the URL, including IHERetrieveListInfo and the following requestparameters are specified by the WSDL and may not be changed. See the discussion about location inITI TF-2a: 3.11.4.1.2 Message Semantics above.In addition, the Display Actor shall support the following field of the HTTP request:Table 3.11.4-8 HTTP Request and Response FieldsHTTP FieldAccept-LanguageREQODescriptionThis field restricts the set of natural languages that are preferredas a response to the request.ValuesAny valid value according toRFC2616_________________________________________________________________________________Rev. 7.0 Final Text 2010-08-10 80 Copyright © 2010 IHE International, Inc.
IHE IT Infrastructure Technical Framework, Volume 2a (ITI TF-2a): Transactions Part A_________________________________________________________________________________The Information Source actor shall support the following field of the HTTP response.Table 3.11.4-9 HTTP Request FieldsHTTPFieldREQDescriptionExpires R This field gives the date/time after whichthe response is considered staleCache-ControlRThis field indicates that this responseshould not be cached.ValuesShall be 0. This is now deprecated usage, but it is thewidely supported means of specifying no cacheing.Shall be no-cache1830If necessary, the Display Actor may perform the request to the web service utilizing HTTPS protocol.Information Source Actors may return HTTP redirect responses (responses with values of 301, 302, 303or 307) in response to a request. Display Actors can expect to receive an error response, or the datarequested, or a request to look elsewhere for the data. A Display Actor must follow redirects, but ifa loop is detected, it may report an error.3.11.3.3.3 Expected Actions1835184018451850Upon reception of the Request for Specific Information, the Information Source Actor shall parse therequest and if there are no errors, shall return the Response with Specific Information as specified in ITITF-2a: 3.11.4.2, and HTTP response code 200 - OK.If the requestType specified is not supported, the Information Source Actor shall return HTTP responsecode404 (not found) with the suggested reason-phrase “requestType not supported”. If the InformationSource Actor is not able to format the document in any content types listed in the 'Accept' field, it shallreturn HTTP response code 406 – Not Acceptable.If the Patient ID specified by the Display Actor is not known to the Information Source Actor, it shallreturn HTTP response-code 404 (not found) with the suggested reason-phrase “Patient ID not found”. Ifthe Display Actor provides the Patient ID from a different domain than the one the Information SourceActor belongs to, and the Information Source Actor is grouped with the Patient ID Consumer Actor, itmay attempt to obtain a mapping of the provided Patient ID into its domain before responding.Note: Other HTTP response codes may be returned by the Information Source Actor, indicating conditions outside of the scope ofthis profile, for example, 401 – Authentication Failed might be returned if Information Source Actor is grouped with theKerberized Server Actor.Note: It is recommended that the Information Source Actor complement returned error code with a human readable description ofthe error condition.If an error condition cannot be automatically recovered, at a minimum, the error should be displayed tothe user by the Display Actor.3.11.3.4 Response with Specific Information - List18553.11.3.4.1 Trigger EventsThis message is sent by the Information Source Actor in response to the Request For SpecificInformation web service request._________________________________________________________________________________Rev. 7.0 Final Text 2010-08-10 81 Copyright © 2010 IHE International, Inc.
Page 1 and 2:
Integrating the Healthcare Enterpri
Page 3 and 4:
707580859095100105110IHE IT Infrast
Page 5 and 6:
160IHE IT Infrastructure Technical
Page 7 and 8:
205210215220IHE IT Infrastructure T
Page 9 and 10:
275280IHE IT Infrastructure Technic
Page 11 and 12:
IHE IT Infrastructure Technical Fra
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30: 670IHE IT Infrastructure Technical
Page 35 and 36: IHE IT Infrastructure Technical Fra
Page 37 and 38: 875880885IHE IT Infrastructure Tech
Page 41 and 42: 980985IHE IT Infrastructure Technic
Page 79: 1770IHE IT Infrastructure Technical
Page 85 and 86: 191519201925IHE IT Infrastructure T
Page 99 and 100: 229022952300230523102315IHE IT Infr
Page 105 and 106: 24502455IHE IT Infrastructure Techn
Page 115 and 116: 2830283528402845IHE IT Infrastructu
Page 117 and 118: 29552960296529702975298029852990299
Page 119 and 120: 30903095310031053110IHE IT Infrastr
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
34953500IHE IT Infrastructure Techn
Page 141 and 142:
Page 143 and 144:
35953600360536103615IHE IT Infrastr
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
428042854290IHE IT Infrastructure T
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
4515452045254530IHE IT Infrastructu
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191:
show all

ITI Technical Framework - IHE

Create successful ePaper yourself

Delete template?

Save as template?