This wiki has undergone a migration to Confluence found Here
Difference between revisions of "September2008WGM arb doc"
Jump to navigation
Jump to search
m |
|||
| Line 1: | Line 1: | ||
| − | = | + | =Stack of specifications that support ISCS's= |
| − | + | [[Services_Aware_Enterprise_Architecture_Framework|Return to SAEAF Table of Contents]] | |
| − | + | ==Reference== | |
| − | + | #Reference Information Model (Rim) | |
| − | + | #Abstract data types (adt) | |
| − | + | #HL7 Development framework | |
| − | + | ##Message Development framework | |
| − | + | ##Services Development framework | |
| − | + | ##Structured Document Development framework | |
| − | + | ##Electronic Health Record Functional Model | |
| − | + | ###Profile | |
| − | + | #cpp (Email to Grahame) | |
| − | + | #Guidance for using vocabulary in information structures(terminfo) | |
| − | + | #Structured Vocabulary (sv) | |
| − | + | #dmel | |
| − | + | #IV (email to Grahame ) | |
| − | + | #Service Specification Methodology | |
| − | + | == Blueprint== | |
| − | + | #Domain analysis Model(DAM) | |
| − | + | #Domain Message Information Model(DMIM) | |
| − | + | #Service Functional Model SFM | |
| − | + | #Electronic Health Record Functional Model (EHR-FM) | |
| − | + | ==Platform Independent Model== | |
| − | + | #Refined Message Information models(RMIM) | |
| − | == | + | #Templates |
| − | + | #CDA lgs | |
| − | + | #IHE Profiles(parts) | |
| − | + | #Dynamic Models (Instance) | |
| − | + | #Logical Service Model | |
| − | + | ==Platform specific model== | |
| − | + | #Implementable/Implementation Technology Specification (ITS) | |
| − | + | #Serialization models | |
| − | + | #Web Services Description Language (WSDL) Fragments | |
| − | + | #Vertical Bar (AKA Version 2) (VBAR) | |
| − | + | ==Platform Instance== | |
| − | + | #Full WSDLs | |
| − | + | #Simple Object Access Protocol (SOAP) | |
| − | + | #JAVA POJO/EJB | |
| − | + | #Lower Level Protocol (LLP) | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 13:44, 7 August 2008
Contents
Stack of specifications that support ISCS's
Return to SAEAF Table of Contents
Reference
- Reference Information Model (Rim)
- Abstract data types (adt)
- HL7 Development framework
- Message Development framework
- Services Development framework
- Structured Document Development framework
- Electronic Health Record Functional Model
- Profile
- cpp (Email to Grahame)
- Guidance for using vocabulary in information structures(terminfo)
- Structured Vocabulary (sv)
- dmel
- IV (email to Grahame )
- Service Specification Methodology
Blueprint
- Domain analysis Model(DAM)
- Domain Message Information Model(DMIM)
- Service Functional Model SFM
- Electronic Health Record Functional Model (EHR-FM)
Platform Independent Model
- Refined Message Information models(RMIM)
- Templates
- CDA lgs
- IHE Profiles(parts)
- Dynamic Models (Instance)
- Logical Service Model
Platform specific model
- Implementable/Implementation Technology Specification (ITS)
- Serialization models
- Web Services Description Language (WSDL) Fragments
- Vertical Bar (AKA Version 2) (VBAR)
Platform Instance
- Full WSDLs
- Simple Object Access Protocol (SOAP)
- JAVA POJO/EJB
- Lower Level Protocol (LLP)
