iNTERFACEWARE™ Inc.

News Products Downloads Support Services Resources Company Contact

Previous

iNTERFACEWARE Products Manual > Chameleon > Designing HL7 Interfaces > Five Steps to Building HL7 Interfaces > Design the Message, Segment and Table Grammar > Extracting Almost Everything > Using Flat Segment Grammars

Next

About This Manual

HL7 Overview

Iguana

Chameleon

Getting Started

Chameleon Overview

Chameleon Interface

Learning the Basics

Using Python Scripting

HL7 <-> HL7 Transformation

XML <-> HL7 Translation

Learning the Advanced Features

Using the Tools and Utility Applications

Deploying Chameleon Applications

Tutorials and Exercises

Designing HL7 Interfaces

Five Steps to Building HL7 Interfaces

Acquire Real Data

Analyze the Data

Design the Message, Segment and Table Grammar

Getting Smart About Standards

How Much Information is Necessary?

Extracting a Small Data Subset

Extracting Almost Everything

Dividing Messages

Avoiding Segment Filtering

Using the msgtransform Tool

Using Flat Segment Grammars

Designing, Coding, and Deployment

Regression Testing

Interface Types

Implementation Considerations

Using Multi-Threading Intelligently

Performance (Speed) Considerations

Dealing with Multiple Vendors

Transport Design Issues

Troubleshooting

Unix Support

Language API Documentation

Using Flat Segment Grammars

You should try and end up with a segment grammar that is as flat as possible. Flat message structures are much easier to parse and process programmatically than deeply nested ones. Fortunately most commercial HL7 implementations are not as deeply nested in practice as the standard says they can be.

Previous

iNTERFACEWARE Products Manual > Chameleon > Designing HL7 Interfaces > Five Steps to Building HL7 Interfaces > Design the Message, Segment and Table Grammar > Extracting Almost Everything > Using Flat Segment Grammars

Next