Roadmap to Blog
Aug 24, 2012I write about a number of different subjects. This page is an index of the more important posts. 3 laws of Interoperability
My basic 3 laws. I wish everyone understood them. I will often refer to these through my other posts.
- Interoperability: it’s all about the people
- Complexity: you can move it around, or externalize it, but you can’t make it go away
- Healthcare Software: Cheap, Flexible, Interoperable – you can have any two
Basic Requirements for Interoperability
A series of articles covering what is required in order to interoperate with someone else, along with some discussion of inferences for a standards organization like HL7 that exists to help interoperability.
- Transmission of Data
- Common Terminology
- Identification Policies
- Information Structures
- Behavioral Agreement
- Common Understanding
Also, further random ramblings about interoperability:
- Bad Metaphors
- Complexity of Standards
- XML Cowboys
- We don’t need no semantic interoperability
- Follow up:When do you need it?
-
Second Follow up:Semantic Interoperability #2
- Messages, Services, and Documents
- What makes Healthcare special? (followup, andanother)
- Establishing Compromise
- Reader vs Writer
- Being Prepared as a Vendor
- Clinical Safety:Example
Good Specification Design
- Repeating String Fields
- Useability vs Reuseability
- How to use XML?
- Microsoft vs Apple
- Intraoperability vs Interoperability(& vsIntegration)
- Messiness & Complexity
- How verbose?
- APIs instead of formats
Fast Healthcare Interoperable Resources (FHIR)
- RFH (Original Proposal): Resources For Health:Announcement,Comparison with v3…
- FHIR:
- v2 andCDA comparisons &Questions
- Connectathons: (2102Notice)
- Work:CSS,Licensing
HL7 Fresh Look Taskforce
- HL7’s Fresh Look task force(follow ups:#1,#2)
- Point/Counterpoint : Has v3failed orsucceeded?
Other HL7 Methodology
A number of other articles about methodological issues facing HL7.
- Where is HL7 up to?(and about CIMI)
- The flaws of Design By Constraint
- Speaking in RIM Grammar
- Enforcing HL7 standards by law?
- Context of Interoperability (Drive-By Interoperability)
- The community is broken
- The problems of national projects and standards
- Engaging with standards
- SAIFrelated posts
- OIDs & Identifiers
- HL7 licensing issues
- Just what is HL7 v3?
- General v3 questions:
- Should I use v2 or v3?
- Substance Administrations&Coding “PRN”
HL7 v3 Data Types & ISO 21090 (Healthcare datatypes)
Posts about the data types
- Design Considerations(andfollowup) +Irrelevant Features&Too High Quality Requirements
- Profiling ISO 21090
- Using ISO 21090 with ISO 11179
- NullFlavor basics (andrelated questions)
- CD: Codes in multiple fields,Value Sets
- ED Questions:.zip support,Integrity check,Where’s the data?
- EN:titles
- PQ:“tablets” as units,UCUM Validation
- IVL:value,boundaries
- AD:empty use
- GTS:Overview
CDA implementation
Posts about implementing CDA
- CDA Tools
- Improved CDA diagram
- Rendering:stylesheet control,links,attachments
- Managing Identifiers
- CDA Packaging
- Using greenCDA on the wire
- Interpreting CDA content
- Using SUBJ relationship
- Mapping from v2 to CDA:
- Data Types
Version 2
- Acknowledgements
- Character sets and Encoding
- Escaping end of lines( + More escaping)
- FT data type documentation
- Signing v2 Messages
- Code System Representation&Case Sensitivity
- Questions:
- PV1-3
Australian Implementation Issues
- The MSIA Messaging Initiative:#1,#2
- Why NEHTA uses CDA(+ theETP scrap) (+ Senate onPCEHRandSecurity)
- Identifiers in v2 and CDA, andCode Systems
- AMT in CDA(andPBS)
- CDA Clinical Safety Issue
- Implementing NEHTA Clinical Documents (FAQs!):
- Diagnostics:Method,PIT,Text,Attachments,Dates
- Exclusion Statements(#2,#3) andSHS Medical History
- Coding:ANZSCO,v2 table OIDs
Techie Stuff
Funny Stuff