25.01.2015 Views

Ensemble HL7 Version 2 Development Guide - InterSystems ...

Ensemble HL7 Version 2 Development Guide - InterSystems ...

Ensemble HL7 Version 2 Development Guide - InterSystems ...

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Naming Conventions<br />

Variation<br />

If you have decided to organize an interface so that one application receives messages from <strong>Ensemble</strong><br />

via more than one business operation, also include a keyword that classifies the MessageTypes that<br />

passes through each business operation. A typical MessageTypes keyword uses the first three letters<br />

of the <strong>HL7</strong> <strong>Version</strong> 2 message structure, such as ADT, ORM, or ORU. In this case the convention for<br />

the business operation name is as follows:<br />

Examples<br />

ToMainLabADT, ToMainLabORM, ToMainLabOther<br />

1.6.5 Data Transformations<br />

Convention<br />

Remember that the SourceMessageType and TargetMessageType may have the same name, but represent<br />

the same message structure in different schema categories.<br />

Examples<br />

ERChartADTA03ToMainLabADTA03, ERChartADTA02ToMainLabADTA01<br />

<strong>Ensemble</strong> <strong>HL7</strong> <strong>Version</strong> 2 <strong>Development</strong> <strong>Guide</strong> 15

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!