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...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Elements of a Routing Production<br />

<strong>Ensemble</strong> provides a built-in schema category definition for each published version of the <strong>HL7</strong> standard.<br />

These <strong>HL7</strong> category definitions can be viewed and edited in XML format by opening the corresponding<br />

.<strong>HL7</strong> file in <strong>Ensemble</strong> Studio. Each .<strong>HL7</strong> file consists of a set of XML statements which define the<br />

<strong>HL7</strong> messages.<br />

To create your own custom schema category, simply create a new .<strong>HL7</strong> file and add XML statements<br />

to it. You can do this by creating a new file or copying an existing file, as follows:<br />

1. Start <strong>Ensemble</strong> Studio and change to an <strong>Ensemble</strong>-enabled user namespace.<br />

Important:<br />

<strong>InterSystems</strong> recommends that you do not place custom code or data in the systemprovided<br />

namespaces ENSLIB or ENSDEMO where it will be deleted the next<br />

time you upgrade <strong>Ensemble</strong>. The ENSEMBLE namespace and any new namespace<br />

that you create to hold your work is preserved across <strong>Ensemble</strong> upgrades.<br />

2. From the File menu, choose New.<br />

3. The New dialog displays. Select the Custom tab.<br />

4. Select the <strong>HL7</strong> Schema icon and click OK.<br />

5. Enter a New Schema Name. This is the name of the new schema. When you save the<br />

schema definition, it becomes the name of the new *.<strong>HL7</strong> file.<br />

6. Enter a Base Schema Name. Specify the name of the schema base. Use one of the<br />

built–in categories: 2.1, 2.2, 2.3, 2.3.1, 2.4, or 2.5.<br />

7. Click OK.<br />

If you have already created a custom schema category that matches your requirements closely, you<br />

might prefer to copy and edit this custom schema instead of creating a new custom schema. Use the<br />

following steps:<br />

1. Open any existing custom schema category file as follows:<br />

• Start Studio.<br />

• Select File Open.<br />

• For the Look in field choose an <strong>Ensemble</strong>-enabled user namespace.<br />

• In the Files of type field select All files.<br />

• In the File name field enter the extension *.hl7 or *.<strong>HL7</strong>. The names of several schema<br />

category files appear.<br />

• Select an existing custom schema category file as the model for your new file. Do not select<br />

any of the built–in schema category files (2.1.<strong>HL7</strong>, 2.2.<strong>HL7</strong>, 2.3.<strong>HL7</strong>, 2.3.1.<strong>HL7</strong>,<br />

2.4.<strong>HL7</strong>, or 2.5.<strong>HL7</strong>). If there are no custom schema category files to choose from, create<br />

a new file as described in the previous procedure.<br />

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

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

Saved successfully!

Ooh no, something went wrong!