New Segment for Allergies - IAR

[Nunziato, Mark G]

Hello everyone,

 

We are looking to add a new Segment, IAR for Allergy Reactions and Severities to a new schema that we going to create, but can’t seem to find where this is created?  We will then add the IAR after the IAM within our new schema for the ADT_A60.  We have a downstream system that is looking for the IAM, followed by the IAR segment. 

 

 

2.6:ADT_A60 ADT message - Update allergy information

MSH

SFT

UAC

EVN

PID

ARV

PV1

PV2

ARV

IAM

 

Thank you for your assistance.

 

Mark Nunziato

 

Albany Medical Center

Integration Services

Nun...@Mail.AMC.EDU

518-262-8754

 

 

 

[Marc Lang]

If you export a schema to file, you can alter the XML and re-import, alternative is through Studio, expland the "Other" folder and you should see 2.6.HL7

--
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare Community" group.
To post to this group, send email to Ensemble-in...@googlegroups.com
To unsubscribe from this group, send email to Ensemble-in-Healt...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/Ensemble-in-Healthcare?hl=en

[Graham, Ben]

Keep in mind, you do not want to modify the 2.6HL7 schema, since this will be overwritten the next time you do an upgrade.

Rather, you should create a custom schema based on 2.6, copy the definitions you need from 2.6 to your custom schema, and then modify as needed.

 

You will need to prefix the segment names with ‘base:’ to inherit the segment definitions from the base…

 

It is a bit cumbersome, but it works. I am guessing you can find more information on custom schemas in the documentation.

 

-Ben

---

This electronic transmission and any documents accompanying this electronic transmission may contain information that is confidential and/or legally privileged. The information is intended only for the use of the individual or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on or regarding the contents of this electronically transmitted information is strictly prohibited. If you have received this e-mail in error, please notify the sender and delete this message immediately.

[Ted Peck]

Depending what version you have, the "base:" prefix may not be needed. The proper behavior is to just look for the named segment/structure in the custom schema and if not present then look through to the base schema.  I believe we fixed this at some point.  (Allowing base: to be specified meant that you could specify 2 different definitions of the same segment in the same message structure, which was not our intention.)
Ted