Act.statusCode
The Act.statusCode is defined "a code specifying the state of the Act". This definition is further elaborated by the state-machine diagram for the Act class in the RIM documentation and the ActStatus vocabulary.
The interaction between statusCode and SNOMED CT semantics varies according to the nature of the statusCode and the value of the Act.moodCode.
Need to look at V2 statuses. RH
- The most general HL7 Act.statusCode values ("NORMAL", "OBSOLETE" and "NULLIFIED") relate to whether the Act class instance is currently valid. These states do not result in any overlaps with SNOMED CT semantics.
- Other states overlap with aspects of SNOMED CT semantics in a manner that is to some extent dependent on the mood of the Act.
Unlike the other attributes discussed in this section the value of the statusCode may progress over time. Thus the fact that a "request" was aborted implies that a request was made, as well as indicating that the request was not acted upon. Therefore, the impact of a Act.statusCode on SNOMED CT semantics depends on whether the concern is to know what steps were taken or to know whether a step was completed.
The relevance of statusCode is fairly clear cut when the Act.moodCode value is "EVN", since this implies an actual occurrence.
In these cases, the statusCode pertains to whether the event is complete and thus directly to the SNOMED CT [ 408730004 |
procedure context ].
In other moods, this relationship is less clear. For example, the Act.statusCode applies to an Act with moodCode "RQO" refers
to the status of the request, whereas the [ 408730004 | procedure context ] refers to the progress of the concept specified
by the [ 363589002 | associated procedure ].
The following rules deal only with cases where the Act.statusCode has a clear effect on the meaning of an Act class instance in a particular mood. Other rules or guidelines, based on similar principles, may be added in the future.
- Act class instances SHALL be interpreted taking account of the Act.statusCode and the way particular values of this attribute when combined with the Act.moodCode may alter the default or permitted [ 408730004 | procedure context ] values.
- In the case of an Act in "event" mood the defaults and constraints specified in [[]] and [[]] should be modified in accordance with statusCode as shown in HL7 statusCode impact of defaults and constraints applicable to procedure context for Acts in "event" mood.
| statusCode | Default procedure context | Procedure context constraints |
|---|---|---|
| new | pre-starting action status ] | pre-starting action status ] |
| active | post-starting action status ] | post-starting action status ] |
| complete | done ] | done ] |
| held | under consideration ] | under consideration ] |
| cancelled | cancelled ] | cancelled ] |
| suspended | suspended ] | suspended ] |
| aborted | abandoned ] | abandoned ] |
The HL7 statusCode changes throughout the life cycle of an Act in its specified mood, until it reaches an end-state. Consideration of the impact of a statusCode on aspects of semantics depends on whether the requirement is to know 'what steps were taken' or 'whether a step was completed'. Thus the fact that a "request" was aborted implies that a request was made, as well as indicating that the request was not taken through to normal completion.
The statusCode values "new", "active", "held", "completed", "cancelled", "suspended", "nullified" and "obsolete" track the
progress of the Act in its specified mood. The semantic relevance of statusCode in "event" mood is more clear cut than in
other moods.
- For example, statusCode="completed"
- when applied to an Act with moodCode="ENV" implies [ 408730004 | procedure context = 385658003 | done ]
- when applied to an Act with moodCode="RQO" implies that the act of request has been completed. It does not mean that the requested action has been completed.
The statusCode values "NORMAL", "OBSOLETE" and "NULLIFIED" relate to the validity of a particular representation of an Act class instance. These states do not result in any overlaps with SNOMED CT semantics because the meaning of an Act class instance is no longer relevant if it has been "NULLIFIED" or marked as "OBSOLETE".
