ITI Technical Framework - IHE

More documents

Recommendations

Info

IHE IT Infrastructure Technical Framework, Volume 2a (ITI TF-2a): Transactions Part A_________________________________________________________________________________3.6 Change Context745This section corresponds to Transaction ITI-6 of the IHE IT Infrastructure Technical Framework.Transaction ITI-6 is used by the Context Participant and Context Manager actors.3.6.1 Scope750755760765770This transaction allows for an application supporting the Context Participant Actor to change the valuesfor one or more context subjects, forcing other Context Participant actors to synchronize based on thenew context values.The Change Context Transaction is composed of multiple methods as defined by the HL7 ContextManagement “CCOW” Standard. There are two key characteristics to this transaction. The first is thatthe transaction has multiple phases consisting of instigating the change, surveying the other participants,and finally publishing the decision as to whether the context changed or not. The second characteristic isthat the context change involves a specific subject. For the Patient Context Participant Actor the subjectbeing changed is the patient subject. For the Client Authentication Agent Actor the subject beingchanged is the user subject. Applications that implement only the Patient Context Participant Actor shallnot expect the user subject to be set in context.The semantics of the methods used are defined in the documents HL7 Context Management “CCOW”Standard: Component Technology Mapping: ActiveX or HL7 Context Management “CCOW” Standard:Component Technology Mapping: Web, in conjunction with the HL7 Context Management “CCOW”Standard: Subject Data Definitions document. The Context Participant Actor can choose the technologyimplementation it wishes to implement. The Context Manager Actor must support both technologyimplementations in order to accommodate whichever implementation a participant ends up choosing.In the case where Patient Context Participant Actors use identifiers from different patient identifierdomains the Context Manager Actor shall be grouped with the Patient Identifier Cross-referenceConsumer Actor and the corresponding PIX Query Transaction as defined in ITI TF-2a: 3.9 to retrieveall identifiers the patient is known by. The IHE Context Manager Actor encompasses more than aCCOW context manager function. See ITI TF-2x: Appendix D for a complete discussion of the groupingof these two actors.The CCOW architecture is defined as a set of components that implement defined interfaces and theirdetailed methods as specified in the HL7 Context Management “CCOW” Standard: TechnologyIndependent Architecture document. This structure is different than the traditional IHE networktransaction. As is depicted in the interaction diagram in Section 3.6.4, the IHE Change ContextTransaction is composed of multiple CCOW-defined methods._________________________________________________________________________________Rev. 7.0 Final Text 2010-08-10 32 Copyright © 2010 IHE International, Inc.
775IHE IT Infrastructure Technical Framework, Volume 2a (ITI TF-2a): Transactions Part A_________________________________________________________________________________3.6.2 Use Case RolesPatient ContextParticipant ActorClientAuthenticationAgent ActorChange ContextContextManager Actor780785Actor: Client Authentication AgentRole: Initiates context change for user subject by supplying new context values.Actor: Patient Context ParticipantRole: Initiates context change for patient subject by supplying new context values. After receiving thecontext survey results it finalizes context change decision. Applications containing this Actor without apatient lookup function would not use this transaction.Actor: Context ManagerRole: Manages Change Context Transaction lifecycle.3.6.3 Referenced Standard790HL7 Context Management “CCOW” Standard, Version 1.4:Technology and Subject Independent ArchitectureComponent Technology Mapping: ActiveXComponent Technology Mapping: WebSubject Data Definitions_________________________________________________________________________________Rev. 7.0 Final Text 2010-08-10 33 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 31: 740IHE IT Infrastructure Technical
Page 37 and 38: 875880885IHE IT Infrastructure Tech
Page 41 and 42: 980985IHE IT Infrastructure Technic
Page 83 and 84:
IHE IT Infrastructure Technical Fra
Page 85 and 86:
191519201925IHE IT Infrastructure T
Page 87 and 88:
1975IHE IT Infrastructure Technical
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
229022952300230523102315IHE IT Infr
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
24502455IHE IT Infrastructure Techn
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
2830283528402845IHE IT Infrastructu
Page 117 and 118:
29552960296529702975298029852990299
Page 119 and 120:
30903095310031053110IHE IT Infrastr
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
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:
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?