Skip to main content
  • 1748 Accesses

Abstract

The preceding chapters, especially Chap. 5, describe conformance constructs used in message profiles or document types. Chapter 7 describes in detail the different relationship among profiles. This chapter seeks to clarify the use of the conformance constructs by providing a context in which the requirements can be assessed. An example conformity assessment is presented for the usage, cardinality, and vocabulary conformance constructs. The example takes into consideration both the possible states of data-presence with regard to the specific attribute each conformance construct addresses as well as the conditional outcomes (if applicable). The result is a set of truth tables that will aid readers in interpreting the meaning of the conformance constructs. Similar assessments can be performed for the other constructs. The information provided in this chapter can serve as a guide when conducting conformance testing.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 219.00
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 279.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 279.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    At least for consequential data elements.

  2. 2.

    In the constraint model defined in the conformance chapter (i.e., not the base standard).

  3. 3.

    A required data element is defined as required because of its importance for a specific use case. Otherwise it would be sufficient to mark such an element as “required but may be empty”. Therefore, if such an element is missing it should always lead to an appropriate exception.

  4. 4.

    The assessment is based on the action of the receiver for the element in the analysis. There may be other reasons why the message is not processed (i.e., non-conformity of other elements).

  5. 5.

    Only codes in the delta are problematic (which may or may not be addressed in the test set).

References

  1. Health Level 7 (HL7) Standard Version 2.7.1, ANSI/HL7, July, 2012, Chapter 2B – Conformance http://www.hl7.org.

  2. HL7 Version 2.5.1 Implementation Guide. S&I Framework Lab Results Interface interoperability standards (DSTU), Release 2, September 2015; http://www.hl7.org

  3. Snelick R. HL7 v2 Value Set Specification Proposal. Profiling Vocabulary in HL7 v2 Implementation Guides. Original September 2013; last update June 2015. http://hl7v2tools.nist.gov (Publications/Presentations and Technical Documents).

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Frank Oemig .

Rights and permissions

Reprints and permissions

Copyright information

© 2016 Springer International Publishing Switzerland

About this chapter

Cite this chapter

Oemig, F., Snelick, R. (2016). Conformity Assessment. In: Healthcare Interoperability Standards Compliance Handbook. Springer, Cham. https://doi.org/10.1007/978-3-319-44839-8_12

Download citation

  • DOI: https://doi.org/10.1007/978-3-319-44839-8_12

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-319-44837-4

  • Online ISBN: 978-3-319-44839-8

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics