custom schemas Flashcards
For Ensemble or HealthShare to properly parse an HL7 message, it must be assigned a
schema category (e.g. 2.3) and a document type (e.g. ADT_A01)
a custom schema can
modify existing structures
add additional structures
How would you navigate to HL7 schemas?
Ensemble
Interoperate
HL7
HL7 Schema structures
How would you create a custom schema from HL7 schemas?
New
choose base schema
name custom schema
ok
What option adds both message type and message structure?
copy from base
to edit a custom message
select the message
message structure
edit
In the raw definition what characters define an optional field?
[]
e.g. [~EVN~]
In the raw definition what characters define an repeating field?
{}
e.g. {~SFT~}
What is the syntax of a field that is both optional and repeating?
[{}]
e.g. [~[~NK1~}~]
What is the syntax of a mandatory field that does not repeat?
~~
e.g. ~PID~
All elements must be separated by
~
a tilde
How would you add a Z segment to a custom schema?
segment structures tab new add name add fields ok
To view the internal organization of a message structure,
click its name from the DocType Structures tab on the HL7 Schemas page.
To view the structure of a message segment,
click on its name in THE HL7 Schema Message Structure page
On the segment structure page, the symbol !
indicates (1 only) The field is required; it must occur only once.
On the segment structure page, the symbol ?
indicates (0 or 1) The field is optional, but if it occurs, it may occur only once.
On the segment structure page, the symbol +
(1 or more) The field may repeat one or more times.
On the segment structure page, the symbol *
indicates (0 or more) The field may repeat zero or more times.
On the segment structure page, the symbol &
The field may be present, and may repeat, but only under certain conditions.
On the segment structure page, the symbol n*
(0 to n) The field repeats a maximum of n times.
