Skip to content

Commit

Permalink
Format
Browse files Browse the repository at this point in the history
  • Loading branch information
george-hoffer authored Jan 3, 2018
1 parent 0fbf4db commit 4c500ed
Showing 1 changed file with 0 additions and 2 deletions.
2 changes: 0 additions & 2 deletions healthcare-toolkit/v/3.1/hl7-edi.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,6 @@ See the xref:seealso[EDI Schema Language Reference] for more details.
YAML uses a combination of lists and sets of key-value pairs. The order of values is not important, as long as the required items are present. Quotes (either single or double quotes) are used around values which may consist of digits but are meant to be interpreted as strings (since otherwise the YAML parser treats the values as numbers). Indentation is used to show the nesting of lists.

For readability, the ESL structures shown here define all simple key-value pairs before any lists that are part of the same definition.
====

=== Copying and Editing Schema Definitions

Expand Down Expand Up @@ -165,7 +164,6 @@ If you want to define a non-standard segment for your message structure, add the

See the following section for an example of a schema combining a message structure and segment definitions.

=== Simplifying a Schema Using Example Messages

The HL7 standard definitions are very complex, with segments often having twenty or more components and many of the components composites which themselves are broken down into many subcomponents. This can make mapping HL7 difficult, since the DataSense view of the message has to contain all these subcomponents.
Expand Down

0 comments on commit 4c500ed

Please sign in to comment.