NEMSIS Explorer

EMS Data Dictionary & Schematron Rule Reference

Schematron Rules

244 matching rules — National — NEMSIS 3.5.1

nemSch_eNilNvPn_rule_1
National EMSDataSet REPORT [WARNING]

What this means

This rule enforces no constraints on the combination of xsi:nil, Not Value, and Pertinent Negative attributes on eCustomResults.01.

What to check

Review the documentation associated with eCustomResults.01 and compare the recorded values with the rule.

Possible correction

This is a reporting condition rather than an automatic assertion failure. Review the reported finding and determine whether any documentation correction is needed.

Related NEMSIS fields

eCustomResults.01
Official message and technical rule details

Original NEMSIS message

This rule enforces no constraints on the combination of xsi:nil, Not Value, and Pertinent Negative attributes on eCustomResults.01.

Pattern: nemSch_eNilNvPn

Rule ID: nemSch_eNilNvPn_rule_1

Assertion ID:

Context XPath:

nem:eCustomResults.01

Test XPath:

false()

Source:

Schematron/rules/EMSDataSet.sch
nemSch_eNilNvPn_rule_2
National EMSDataSet REPORT [WARNING]

What this means

This rule enforces no constraints on the Pertinent Negative attribute on elements in eExam.AssessmentGroup.

What to check

Review the documentation described by the official message and the applicable NEMSIS fields.

Possible correction

This is a reporting condition rather than an automatic assertion failure. Review the reported finding and determine whether any documentation correction is needed.

Official message and technical rule details

Original NEMSIS message

This rule enforces no constraints on the Pertinent Negative attribute on elements in eExam.AssessmentGroup.

Pattern: nemSch_eNilNvPn

Rule ID: nemSch_eNilNvPn_rule_2

Assertion ID:

Context XPath:

nem:eExam.AssessmentGroup//*[@PN]

Test XPath:

false()

Source:

Schematron/rules/EMSDataSet.sch
nemSch_eNilNvPn_rule_3
National EMSDataSet REPORT [WARNING]

What this means

This rule enforces no constraints on the Pertinent Negative attribute on eHistory.10.

What to check

Review the documentation associated with eHistory.10 and compare the recorded values with the rule.

Possible correction

This is a reporting condition rather than an automatic assertion failure. Review the reported finding and determine whether any documentation correction is needed.

Related NEMSIS fields

eHistory.10
Official message and technical rule details

Original NEMSIS message

This rule enforces no constraints on the Pertinent Negative attribute on eHistory.10.

Pattern: nemSch_eNilNvPn

Rule ID: nemSch_eNilNvPn_rule_3

Assertion ID:

Context XPath:

nem:eHistory.10[@PN]

Test XPath:

false()

Source:

Schematron/rules/EMSDataSet.sch
nemSch_e003
National EMSDataSet ASSERT [ERROR]

What this means

When has a Pertinent Negative of "Unable to Complete", it should be empty and it should not have a Not Value (Not Applicable, Not Recorded, or Not Reporting).

What to check

Review the documentation associated with eSituation.01 and compare the recorded values with the rule.

Possible correction

If the documented information is inconsistent with the requirement, review the actual encounter and correct inaccurate or incomplete entries. Do not change accurate clinical documentation simply to eliminate an error.

Related NEMSIS fields

eSituation.01
Official message and technical rule details

Original NEMSIS message

When has a Pertinent Negative of "Unable to Complete", it should be empty and it should not have a Not Value (Not Applicable, Not Recorded, or Not Reporting).

Pattern: nemSch_eNilNvPn

Rule ID: nemSch_eNilNvPn_rule_4

Assertion ID: nemSch_e003

Context XPath:

nem:eSituation.01[@PN = '8801023']

Test XPath:

@xsi:nil = 'true' and not(@NV)

Source:

Schematron/rules/EMSDataSet.sch
nemSch_e188
National EMSDataSet ASSERT [ERROR]

What this means

When has a Pertinent Negative of "Unable to Complete", it should be empty and it should not have a Not Value (Not Applicable, Not Recorded, or Not Reporting).

What to check

Review the documentation associated with eSituation.18 and compare the recorded values with the rule.

Possible correction

If the documented information is inconsistent with the requirement, review the actual encounter and correct inaccurate or incomplete entries. Do not change accurate clinical documentation simply to eliminate an error.

Related NEMSIS fields

eSituation.18
Official message and technical rule details

Original NEMSIS message

When has a Pertinent Negative of "Unable to Complete", it should be empty and it should not have a Not Value (Not Applicable, Not Recorded, or Not Reporting).

Pattern: nemSch_eNilNvPn

Rule ID: nemSch_eNilNvPn_rule_12

Assertion ID: nemSch_e188

Context XPath:

nem:eSituation.18[@PN = '8801023']

Test XPath:

@xsi:nil = 'true' and not(@NV)

Source:

Schematron/rules/EMSDataSet.sch
nemSch_e189
National EMSDataSet ASSERT [ERROR]

What this means

When has a Pertinent Negative of "Unable to Complete", it should be empty and it should not have a Not Value (Not Applicable, Not Recorded, or Not Reporting).

What to check

Review the documentation associated with eArrest.14 and compare the recorded values with the rule.

Possible correction

If the documented information is inconsistent with the requirement, review the actual encounter and correct inaccurate or incomplete entries. Do not change accurate clinical documentation simply to eliminate an error.

Related NEMSIS fields

eArrest.14
Official message and technical rule details

Original NEMSIS message

When has a Pertinent Negative of "Unable to Complete", it should be empty and it should not have a Not Value (Not Applicable, Not Recorded, or Not Reporting).

Pattern: nemSch_eNilNvPn

Rule ID: nemSch_eNilNvPn_rule_13

Assertion ID: nemSch_e189

Context XPath:

nem:eArrest.14[@PN = '8801023']

Test XPath:

@xsi:nil = 'true' and not(@NV)

Source:

Schematron/rules/EMSDataSet.sch
nemSch_e190
National EMSDataSet ASSERT [ERROR]

What this means

When has a Pertinent Negative of "Approximate", it should have a value and it should not have a Not Value (Not Applicable, Not Recorded, or Not Reporting).

What to check

Review the documentation associated with ePatient.15 and compare the recorded values with the rule.

Possible correction

If the documented information is inconsistent with the requirement, review the actual encounter and correct inaccurate or incomplete entries. Do not change accurate clinical documentation simply to eliminate an error.

Related NEMSIS fields

ePatient.15
Official message and technical rule details

Original NEMSIS message

When has a Pertinent Negative of "Approximate", it should have a value and it should not have a Not Value (Not Applicable, Not Recorded, or Not Reporting).

Pattern: nemSch_eNilNvPn

Rule ID: nemSch_eNilNvPn_rule_14

Assertion ID: nemSch_e190

Context XPath:

nem:ePatient.15[@PN = '8801029']

Test XPath:

not(@xsi:nil = 'true') and not(@NV)

Source:

Schematron/rules/EMSDataSet.sch
nemSch_e004
National EMSDataSet ASSERT [ERROR]

What this means

When has a Pertinent Negative of "Approximate", it should have a value and it should not have a Not Value (Not Applicable, Not Recorded, or Not Reporting).

What to check

Review the documentation associated with eSituation.01 and compare the recorded values with the rule.

Possible correction

If the documented information is inconsistent with the requirement, review the actual encounter and correct inaccurate or incomplete entries. Do not change accurate clinical documentation simply to eliminate an error.

Related NEMSIS fields

eSituation.01
Official message and technical rule details

Original NEMSIS message

When has a Pertinent Negative of "Approximate", it should have a value and it should not have a Not Value (Not Applicable, Not Recorded, or Not Reporting).

Pattern: nemSch_eNilNvPn

Rule ID: nemSch_eNilNvPn_rule_5

Assertion ID: nemSch_e004

Context XPath:

nem:eSituation.01[@PN = '8801029']

Test XPath:

not(@xsi:nil = 'true') and not(@NV)

Source:

Schematron/rules/EMSDataSet.sch
nemSch_e191
National EMSDataSet ASSERT [ERROR]

What this means

When has a Pertinent Negative of "Approximate", it should have a value and it should not have a Not Value (Not Applicable, Not Recorded, or Not Reporting).

What to check

Review the documentation associated with eSituation.18 and compare the recorded values with the rule.

Possible correction

If the documented information is inconsistent with the requirement, review the actual encounter and correct inaccurate or incomplete entries. Do not change accurate clinical documentation simply to eliminate an error.

Related NEMSIS fields

eSituation.18
Official message and technical rule details

Original NEMSIS message

When has a Pertinent Negative of "Approximate", it should have a value and it should not have a Not Value (Not Applicable, Not Recorded, or Not Reporting).

Pattern: nemSch_eNilNvPn

Rule ID: nemSch_eNilNvPn_rule_15

Assertion ID: nemSch_e191

Context XPath:

nem:eSituation.18[@PN = '8801029']

Test XPath:

not(@xsi:nil = 'true') and not(@NV)

Source:

Schematron/rules/EMSDataSet.sch
nemSch_e192
National EMSDataSet ASSERT [ERROR]

What this means

When has a Pertinent Negative of "Approximate", it should have a value and it should not have a Not Value (Not Applicable, Not Recorded, or Not Reporting).

What to check

Review the documentation associated with eArrest.14 and compare the recorded values with the rule.

Possible correction

If the documented information is inconsistent with the requirement, review the actual encounter and correct inaccurate or incomplete entries. Do not change accurate clinical documentation simply to eliminate an error.

Related NEMSIS fields

eArrest.14
Official message and technical rule details

Original NEMSIS message

When has a Pertinent Negative of "Approximate", it should have a value and it should not have a Not Value (Not Applicable, Not Recorded, or Not Reporting).

Pattern: nemSch_eNilNvPn

Rule ID: nemSch_eNilNvPn_rule_16

Assertion ID: nemSch_e192

Context XPath:

nem:eArrest.14[@PN = '8801029']

Test XPath:

not(@xsi:nil = 'true') and not(@NV)

Source:

Schematron/rules/EMSDataSet.sch
nemSch_e005
National EMSDataSet ASSERT [ERROR]

What this means

When has a Pertinent Negative, it should have a value and it should not have a Not Value (Not Applicable, Not Recorded, or Not Reporting).

What to check

Review the documentation associated with eSituation.10 and compare the recorded values with the rule.

Possible correction

If the documented information is inconsistent with the requirement, review the actual encounter and correct inaccurate or incomplete entries. Do not change accurate clinical documentation simply to eliminate an error.

Related NEMSIS fields

eSituation.10
Official message and technical rule details

Original NEMSIS message

When has a Pertinent Negative, it should have a value and it should not have a Not Value (Not Applicable, Not Recorded, or Not Reporting).

Pattern: nemSch_eNilNvPn

Rule ID: nemSch_eNilNvPn_rule_6

Assertion ID: nemSch_e005

Context XPath:

nem:eSituation.10[@PN]

Test XPath:

not(@xsi:nil = 'true') and not(@NV)

Source:

Schematron/rules/EMSDataSet.sch
nemSch_e006
National EMSDataSet ASSERT [ERROR]

What this means

When has a Pertinent Negative, it should have a value and it should not have a Not Value (Not Applicable, Not Recorded, or Not Reporting).

What to check

Review the documentation associated with eMedications.03 and compare the recorded values with the rule.

Possible correction

If the documented information is inconsistent with the requirement, review the actual encounter and correct inaccurate or incomplete entries. Do not change accurate clinical documentation simply to eliminate an error.

Related NEMSIS fields

eMedications.03
Official message and technical rule details

Original NEMSIS message

When has a Pertinent Negative, it should have a value and it should not have a Not Value (Not Applicable, Not Recorded, or Not Reporting).

Pattern: nemSch_eNilNvPn

Rule ID: nemSch_eNilNvPn_rule_7

Assertion ID: nemSch_e006

Context XPath:

nem:eMedications.03[@PN]

Test XPath:

not(@xsi:nil = 'true') and not(@NV)

Source:

Schematron/rules/EMSDataSet.sch
nemSch_e007
National EMSDataSet ASSERT [ERROR]

What this means

When has a Pertinent Negative, it should have a value and it should not have a Not Value (Not Applicable, Not Recorded, or Not Reporting).

What to check

Review the documentation associated with eProcedures.03 and compare the recorded values with the rule.

Possible correction

If the documented information is inconsistent with the requirement, review the actual encounter and correct inaccurate or incomplete entries. Do not change accurate clinical documentation simply to eliminate an error.

Related NEMSIS fields

eProcedures.03
Official message and technical rule details

Original NEMSIS message

When has a Pertinent Negative, it should have a value and it should not have a Not Value (Not Applicable, Not Recorded, or Not Reporting).

Pattern: nemSch_eNilNvPn

Rule ID: nemSch_eNilNvPn_rule_8

Assertion ID: nemSch_e007

Context XPath:

nem:eProcedures.03[@PN]

Test XPath:

not(@xsi:nil = 'true') and not(@NV)

Source:

Schematron/rules/EMSDataSet.sch
nemSch_e008
National EMSDataSet ASSERT [ERROR]

What this means

When has a Pertinent Negative, it should be empty and it should not have a Not Value (Not Applicable, Not Recorded, or Not Reporting).

What to check

Review the documentation described by the official message and the applicable NEMSIS fields.

Possible correction

If the documented information is inconsistent with the requirement, review the actual encounter and correct inaccurate or incomplete entries. Do not change accurate clinical documentation simply to eliminate an error.

Official message and technical rule details

Original NEMSIS message

When has a Pertinent Negative, it should be empty and it should not have a Not Value (Not Applicable, Not Recorded, or Not Reporting).

Pattern: nemSch_eNilNvPn

Rule ID: nemSch_eNilNvPn_rule_9

Assertion ID: nemSch_e008

Context XPath:

*[@PN]

Test XPath:

@xsi:nil = 'true' and not(@NV)

Source:

Schematron/rules/EMSDataSet.sch
nemSch_e001
National EMSDataSet ASSERT [ERROR]

What this means

When is empty, it should have a Not Value (Not Applicable, Not Recorded, or Not Reporting, if allowed for the element) or a Pertinent Negative (if allowed for the element), or it should be omitted (if the element is optional).

What to check

Review the documentation described by the official message and the applicable NEMSIS fields.

Possible correction

If the documented information is inconsistent with the requirement, review the actual encounter and correct inaccurate or incomplete entries. Do not change accurate clinical documentation simply to eliminate an error.

Official message and technical rule details

Original NEMSIS message

When is empty, it should have a Not Value (Not Applicable, Not Recorded, or Not Reporting, if allowed for the element) or a Pertinent Negative (if allowed for the element), or it should be omitted (if the element is optional).

Pattern: nemSch_eNilNvPn

Rule ID: nemSch_eNilNvPn_rule_10

Assertion ID: nemSch_e001

Context XPath:

*[@xsi:nil = 'true']

Test XPath:

@NV or @PN

Source:

Schematron/rules/EMSDataSet.sch
nemSch_e002
National EMSDataSet ASSERT [ERROR]

What this means

When has a Not Value (Not Applicable, Not Recorded, or Not Reporting), it should be empty.

What to check

Review the documentation described by the official message and the applicable NEMSIS fields.

Possible correction

If the documented information is inconsistent with the requirement, review the actual encounter and correct inaccurate or incomplete entries. Do not change accurate clinical documentation simply to eliminate an error.

Official message and technical rule details

Original NEMSIS message

When has a Not Value (Not Applicable, Not Recorded, or Not Reporting), it should be empty.

Pattern: nemSch_eNilNvPn

Rule ID: nemSch_eNilNvPn_rule_11

Assertion ID: nemSch_e002

Context XPath:

*[@NV]

Test XPath:

@xsi:nil='true'

Source:

Schematron/rules/EMSDataSet.sch
nemSch_eNvPn_rule_1
National EMSDataSet REPORT [WARNING]

What this means

This rule enforces no constraints on the uniqueness of eCustomResults.01 with Not Value or Pertinent Negative attribute.

What to check

Review the documentation associated with eCustomResults.01 and compare the recorded values with the rule.

Possible correction

This is a reporting condition rather than an automatic assertion failure. Review the reported finding and determine whether any documentation correction is needed.

Related NEMSIS fields

eCustomResults.01
Official message and technical rule details

Original NEMSIS message

This rule enforces no constraints on the uniqueness of eCustomResults.01 with Not Value or Pertinent Negative attribute.

Pattern: nemSch_eNvPn

Rule ID: nemSch_eNvPn_rule_1

Assertion ID:

Context XPath:

nem:eCustomResults.01

Test XPath:

false()

Source:

Schematron/rules/EMSDataSet.sch
nemSch_eNvPn_rule_2
National EMSDataSet REPORT [WARNING]

What this means

This rule enforces no constraints on the uniqueness of elements in eExam.AssessmentGroup with a Pertinent Negative Attribute.

What to check

Review the documentation described by the official message and the applicable NEMSIS fields.

Possible correction

This is a reporting condition rather than an automatic assertion failure. Review the reported finding and determine whether any documentation correction is needed.

Official message and technical rule details

Original NEMSIS message

This rule enforces no constraints on the uniqueness of elements in eExam.AssessmentGroup with a Pertinent Negative Attribute.

Pattern: nemSch_eNvPn

Rule ID: nemSch_eNvPn_rule_2

Assertion ID:

Context XPath:

nem:eExam.AssessmentGroup//*[@PN]

Test XPath:

false()

Source:

Schematron/rules/EMSDataSet.sch
nemSch_eNvPn_rule_3
National EMSDataSet REPORT [WARNING]

What this means

This rule enforces no constraints on the uniqueness of eSituation.10 with a Pertinent Negative Attribute.

What to check

Review the documentation associated with eSituation.10 and compare the recorded values with the rule.

Possible correction

This is a reporting condition rather than an automatic assertion failure. Review the reported finding and determine whether any documentation correction is needed.

Related NEMSIS fields

eSituation.10
Official message and technical rule details

Original NEMSIS message

This rule enforces no constraints on the uniqueness of eSituation.10 with a Pertinent Negative Attribute.

Pattern: nemSch_eNvPn

Rule ID: nemSch_eNvPn_rule_3

Assertion ID:

Context XPath:

nem:eSituation.10[@PN]

Test XPath:

false()

Source:

Schematron/rules/EMSDataSet.sch
nemSch_e009
National EMSDataSet ASSERT [WARNING]

What this means

When has a Not Value, no other value should be recorded.

What to check

Review the documentation described by the official message and the applicable NEMSIS fields.

Possible correction

If the documented information is inconsistent with the requirement, review the actual encounter and correct inaccurate or incomplete entries. Do not change accurate clinical documentation simply to eliminate an error.

Official message and technical rule details

Original NEMSIS message

When has a Not Value, no other value should be recorded.

Pattern: nemSch_eNvPn

Rule ID: nemSch_eNvPn_rule_4

Assertion ID: nemSch_e009

Context XPath:

*[@NV][local-name() = (local-name(preceding-sibling::*[1]), local-name(following-sibling::*[1]))]

Test XPath:

false()

Source:

Schematron/rules/EMSDataSet.sch
nemSch_e010
National EMSDataSet ASSERT [WARNING]

What this means

When has a Pertinent Negative, no other value should be recorded.

What to check

Review the documentation described by the official message and the applicable NEMSIS fields.

Possible correction

If the documented information is inconsistent with the requirement, review the actual encounter and correct inaccurate or incomplete entries. Do not change accurate clinical documentation simply to eliminate an error.

Official message and technical rule details

Original NEMSIS message

When has a Pertinent Negative, no other value should be recorded.

Pattern: nemSch_eNvPn

Rule ID: nemSch_eNvPn_rule_5

Assertion ID: nemSch_e010

Context XPath:

*[@PN][local-name() = (local-name(preceding-sibling::*[1]), local-name(following-sibling::*[1]))]

Test XPath:

false()

Source:

Schematron/rules/EMSDataSet.sch
nemSch_e011
National EMSDataSet ASSERT [WARNING]

What this means

in the patient care report should match in the agency demographic information.

What to check

Review the documentation associated with eResponse.01, dAgency.02 and compare the recorded values with the rule.

Possible correction

If the documented information is inconsistent with the requirement, review the actual encounter and correct inaccurate or incomplete entries. Do not change accurate clinical documentation simply to eliminate an error.

Related NEMSIS fields

eResponse.01 dAgency.02
Official message and technical rule details

Original NEMSIS message

in the patient care report should match in the agency demographic information.

Pattern: nemSch_eResponse

Rule ID: nemSch_eResponse_rule_1

Assertion ID: nemSch_e011

Context XPath:

nem:eResponse.01

Test XPath:

. = ancestor::nem:Header/nem:DemographicGroup/nem:dAgency.02

Source:

Schematron/rules/EMSDataSet.sch
nemSch_e012
National EMSDataSet ASSERT [WARNING]

What this means

When is "None/No Delay", no other value should be recorded.

What to check

Review the documentation associated with eResponse.08 and compare the recorded values with the rule.

Possible correction

If the documented information is inconsistent with the requirement, review the actual encounter and correct inaccurate or incomplete entries. Do not change accurate clinical documentation simply to eliminate an error.

Related NEMSIS fields

eResponse.08
Official message and technical rule details

Original NEMSIS message

When is "None/No Delay", no other value should be recorded.

Pattern: nemSch_eResponse

Rule ID: nemSch_eResponse_rule_2

Assertion ID: nemSch_e012

Context XPath:

nem:eResponse.08[. = '2208013'][1]

Test XPath:

count(../nem:eResponse.08) = 1

Source:

Schematron/rules/EMSDataSet.sch
nemSch_e013
National EMSDataSet ASSERT [WARNING]

What this means

When is "None/No Delay", no other value should be recorded.

What to check

Review the documentation associated with eResponse.09 and compare the recorded values with the rule.

Possible correction

If the documented information is inconsistent with the requirement, review the actual encounter and correct inaccurate or incomplete entries. Do not change accurate clinical documentation simply to eliminate an error.

Related NEMSIS fields

eResponse.09
Official message and technical rule details

Original NEMSIS message

When is "None/No Delay", no other value should be recorded.

Pattern: nemSch_eResponse

Rule ID: nemSch_eResponse_rule_3

Assertion ID: nemSch_e013

Context XPath:

nem:eResponse.09[. = '2209011'][1]

Test XPath:

count(../nem:eResponse.09) = 1

Source:

Schematron/rules/EMSDataSet.sch
nemSch_e014
National EMSDataSet ASSERT [WARNING]

What this means

When is "None/No Delay", no other value should be recorded.

What to check

Review the documentation associated with eResponse.10 and compare the recorded values with the rule.

Possible correction

If the documented information is inconsistent with the requirement, review the actual encounter and correct inaccurate or incomplete entries. Do not change accurate clinical documentation simply to eliminate an error.

Related NEMSIS fields

eResponse.10
Official message and technical rule details

Original NEMSIS message

When is "None/No Delay", no other value should be recorded.

Pattern: nemSch_eResponse

Rule ID: nemSch_eResponse_rule_4

Assertion ID: nemSch_e014

Context XPath:

nem:eResponse.10[. = '2210017'][1]

Test XPath:

count(../nem:eResponse.10) = 1

Source:

Schematron/rules/EMSDataSet.sch
Page 1 of 10 Next

Explanations are documentation guidance derived from official NEMSIS messages and detected field references. The original Schematron XPath determines exact validation behavior. This page does not execute XML validation.