ACK Management Framework
0.1.9 - ci-build

ACK Management Framework, published by FO. This guide is not an authorized publication; it is the continuous build for version 0.1.9 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/frankoemig/ack-ig/ and changes regularly. See the Directory of published versions

Obligations

Overview

Why do we need obligations? Because we want to have a formal definition of what should happen with a message or data!

What are the obligations for a message?

ObligationsConformance VerbspositiveSHALLSHOULDMAYnegative(MAYNOT)SHOULDNOTSHALLNOTActivityto senderRESPOND...to applicationPROCESS...IGNORE...INHERIT...forwardingSEND...Data Expectationexpected...unexpected...

Some examples:

Obligation ExamplesSHOULD:PROCESSSHOULDNOT:MODIFYSHALLNOT:SEND:missing

The idea behind obligations is to express three different aspects per statement:

  1. the conformance verb expresses the level of requirement.
  2. the activity specifies what exactly should be done. This can be separated for the internal processing, forwarding to another recipient, and as a response to the original sender.
  3. expectations for the data itself