347:
relates a set of artifacts that collectively specify the relevant semantics of a software component specification or other system-of- interest. In summary, the ECCF SS provides an organizational framework in which inter-related artifacts are sorted by content – for example a
Unified Modeling Language (UML) activity diagram in the Business viewpoint that contains static data constructs (for example, documents or data structures) which passes between the various structures would all have the relevant static constructs detailed in artifacts, specifically, business rules, information constructors, behavioral contracts, and level-of-abstraction.
22:
121:
63:
217:
SAIF is a way of thinking about producing specifications that explicitly describe the governance, conformance, compliance, and behavioral semantics that are needed to achieve computable semantic working interoperability. The intended information transmission technology might use a messaging, document
355:
The
Interoperability Specification Matrix (ISM) defines a 5-column-by-3-row matrix (“table”) which distributes the multiple aspects of a given component's specification across the various cells of the matrix. The structure of the ISM is based on proven cognitive models for describing complex systems
346:
The major goal of the
Enterprise Consistency and Conformity Framework (ECCF) is enabling working interoperability between different users, organizations, and systems. The ECCF is manifest in a structure called the ECCF specification stack (SS). This structure identifies, defines, organizes, and
307:
The
Behavioral Framework (BF) provides a set of constructs for defining the behavioral semantics of specifications, which enable working interoperability. As a result, the focus of the BF is accountability – a description of “who does what when.” Accountability describes the perspective of the
281:
The SAIF Introduction and
Overview describes the general constructs that frame the SAIF. SAIF represents a synthesis of best practices and concepts from multiple architectural frameworks. This introduction to SAIF goes into a lot of technical depth and assumes you are already familiar with
298:
are discussed in detail in separate documents, and are mentioned in the course of this document only when necessary to either contextualize or logically link GF content to the larger context of the
Services Aware Interoperability Framework.
308:
various technology components that are involved in a particular instance or scenario designed to achieve
Working Interoperability. The BF is technology-neutral and, therefore, can be used within model-driven specification stacks.
316:
The
Information Framework (IF) is a SAIF-compliant recasting of existing HL7 expertise regarding the specification of static semantics. The Information Framework will draw on the information available from the following sources:
35:
356:
which revolve around the notion of partitioning complexity based on a number of
Dimensions while simultaneously viewing each of these dimensions from multiple Perspectives.
41:
139:
210:
The HL7 Services-Aware
Interoperability Framework Canonical Definition (SAIF-CD) provides consistency between all artifacts, and enables a standardized approach to
232:. Since the release of this document, the SAIF-CD has been balloted as a Draft Standard for Trial Use. The document will be made available by the end of May, 2012.
440:
328:
196:
192:
community and specifically the former HL7 Architecture Board (ArB) to develop an interoperability framework that would support services, messages, and
84:
71:
445:
175:
157:
102:
49:
420:
202:
HL7 provides a framework and standards for the exchange, integration, sharing, and retrieval of electronic health information.
193:
425:
435:
290:
The Governance Framework (GF) describes the motivation for, the structure, content and utilization of the GF. The
430:
225:
for achieving interoperability, but it is not a whole-solution design for enterprise architecture management.
211:
221:
SAIF is the framework that is required to rationalize interoperability of standards. SAIF is an
189:
414:
402:
229:
214:(EA) development and implementation, and a way to measure the consistency.
391:
364:
This section defines the creation of a compliant implementation guide.
291:
236:
114:
56:
15:
135:
80:
263:
Enterprise Consistency and Conformity Framework (ECCF)
380:
239:
was made to provide insight to users of the SAIF-CD.
130:
may be too technical for most readers to understand
282:architectural standards and the HL7 organization.
247:The SAIF-CD consists of the following sections:
342:Enterprise Consistency and Conformity Framework
8:
351:Interoperability Specification Matrix (ISM)
266:Interoperability Specification Matrix (ISM)
50:Learn how and when to remove these messages
295:
228:The informative document may be found at
188:This article documents the effort of the
176:Learn how and when to remove this message
158:Learn how and when to remove this message
142:, without removing the technical details.
103:Learn how and when to remove this message
373:
441:American National Standards Institute
140:make it understandable to non-experts
7:
360:Compliant SAIF Implementation Guides
269:Compliant SAIF Implementation Guides
194:Clinical Document Architecture(CDA)
327:Reference Information Model (RIM)
14:
31:This article has multiple issues.
218:exchange, or services approach.
119:
61:
20:
39:or discuss these issues on the
1:
324:Domain Analysis Models (DAM)
462:
446:Data interchange standards
237:Short introduction to SAIF
260:Information Framework(IF)
257:Behavioral Framework (BF)
254:Governance Framework (GF)
75:may need to be rewritten
421:International standards
392:HL7 Architecture Board
212:enterprise architecture
190:Health Level Seven(HL7)
312:Information Framework
426:Agent-based software
303:Behavioral Framework
286:Governance Framework
436:Information science
381:Health Level Seven
337:HL7 Core Principles
334:Vocabulary concepts
243:Document Divisions
186:
185:
178:
168:
167:
160:
113:
112:
105:
85:lead layout guide
54:
453:
431:Health standards
405:
400:
394:
389:
383:
378:
181:
174:
163:
156:
152:
149:
143:
123:
122:
115:
108:
101:
97:
94:
88:
81:improve the lead
65:
64:
57:
46:
24:
23:
16:
461:
460:
456:
455:
454:
452:
451:
450:
411:
410:
409:
408:
401:
397:
390:
386:
379:
375:
370:
362:
353:
344:
314:
305:
288:
279:
245:
208:
182:
171:
170:
169:
164:
153:
147:
144:
136:help improve it
133:
124:
120:
109:
98:
92:
89:
78:
66:
62:
25:
21:
12:
11:
5:
459:
457:
449:
448:
443:
438:
433:
428:
423:
413:
412:
407:
406:
395:
384:
372:
371:
369:
366:
361:
358:
352:
349:
343:
340:
339:
338:
335:
332:
325:
322:
313:
310:
304:
301:
287:
284:
278:
275:
274:
273:
270:
267:
264:
261:
258:
255:
252:
244:
241:
230:Public SAIF CD
207:
204:
184:
183:
166:
165:
127:
125:
118:
111:
110:
70:The article's
69:
67:
60:
55:
29:
28:
26:
19:
13:
10:
9:
6:
4:
3:
2:
458:
447:
444:
442:
439:
437:
434:
432:
429:
427:
424:
422:
419:
418:
416:
404:
399:
396:
393:
388:
385:
382:
377:
374:
367:
365:
359:
357:
350:
348:
341:
336:
333:
330:
326:
323:
320:
319:
318:
311:
309:
302:
300:
297:
293:
285:
283:
276:
271:
268:
265:
262:
259:
256:
253:
250:
249:
248:
242:
240:
238:
233:
231:
226:
224:
219:
215:
213:
206:SAIF Overview
205:
203:
200:
198:
195:
191:
180:
177:
162:
159:
151:
141:
137:
131:
128:This article
126:
117:
116:
107:
104:
96:
93:November 2016
86:
83:and read the
82:
76:
73:
68:
59:
58:
53:
51:
44:
43:
38:
37:
32:
27:
18:
17:
398:
387:
376:
363:
354:
345:
315:
306:
289:
280:
277:Introduction
251:Introduction
246:
234:
227:
223:architecture
222:
220:
216:
209:
201:
187:
172:
154:
145:
129:
99:
90:
79:Please help
74:
72:lead section
47:
40:
34:
33:Please help
30:
321:Storyboards
415:Categories
368:References
148:April 2019
36:improve it
42:talk page
272:Appendix
403:SAIF-CD
199:10871.
134:Please
331:21731
294:and
292:ECCF
329:ISO
197:ISO
138:to
417::
296:BF
235:A
45:.
179:)
173:(
161:)
155:(
150:)
146:(
132:.
106:)
100:(
95:)
91:(
87:.
77:.
52:)
48:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.