Difference between revisions of "Six Core Architecture Features"
WoodyBeeler (talk | contribs) |
WoodyBeeler (talk | contribs) |
||
| Line 6: | Line 6: | ||
# Are developed using '''shared, documented methodology''' | # Are developed using '''shared, documented methodology''' | ||
# Rely on generic '''computation and data standards''' wherever possible | # Rely on generic '''computation and data standards''' wherever possible | ||
| + | # Platform independence | ||
| + | '''Need an over arching schema''' (such as B. Blobel proposes) to bind these together in a functional fashion that will inform and guide | ||
| + | |||
| + | Notes: | ||
| + | |||
| + | |||
| + | I would add the reflection of the model driven architectural approach | ||
| + | using the Zachman model as well as MDA or the RM-ODP classification. | ||
| + | Interpretation of this approach can be found in the paper I've | ||
| + | distributed to T3F. | ||
| + | |||
| + | I'd like to add the need of ontology-based reference terminologies as | ||
| + | well as the separation of computation-independent, platform-independent | ||
| + | and platform-specific aspects. | ||
| + | |||
| + | Also the Unified Process | ||
| + | |||
| + | Even while security and privacy represent a special domain like others | ||
| + | (the term has been extended to the domain term used in HL7), the | ||
| + | importance of security and privacy services in the architectural | ||
| + | approach should be eventually emphasized. | ||
Revision as of 16:57, 16 January 2007
HL7 will develop health care interoperability standards that:
- Derive from single Reference Information Model (RIM)
- Use common, defined terminologies
- Reuse models, following consistent patterns
- Address multiple implementation paradigms (document, messaging, services)
- Are developed using shared, documented methodology
- Rely on generic computation and data standards wherever possible
- Platform independence
Need an over arching schema (such as B. Blobel proposes) to bind these together in a functional fashion that will inform and guide
Notes:
I would add the reflection of the model driven architectural approach
using the Zachman model as well as MDA or the RM-ODP classification.
Interpretation of this approach can be found in the paper I've
distributed to T3F.
I'd like to add the need of ontology-based reference terminologies as well as the separation of computation-independent, platform-independent and platform-specific aspects.
Also the Unified Process
Even while security and privacy represent a special domain like others (the term has been extended to the domain term used in HL7), the importance of security and privacy services in the architectural approach should be eventually emphasized.
