The composer of a COMPOSITION should always be known, not just if it happens to be one with an EVENT_CONTEXT. In the current specification, EVENT_CONTEXT is only recorded on the one COMPOSITION in a CONTRIBUTION group, which corresponds to the health system event, like a patient encounter. That means that there is no composer on the other COMPOSITIONS in the CONTRIBUTION, which is probably dangerous.
When the composer is the patient, the composer attribute will be set to a value of PARTY_PROXY which corresponds logically to "self". Details of this are in the Common IM, generic package.
Activity
Fixed
Details
Assignee
JeffJ
JeffJ
Reporter
JeffJ
JeffJ
Priority
Minor
Created November 11, 2005 at 12:00 AM
Updated January 6, 2006 at 12:00 AM
Resolved January 6, 2006 at 12:00 AM
Flag notifications
Something's gone wrong
Looks like you've been signed out. Try logging in again.
The composer of a COMPOSITION should always be known, not just if it happens
to be one with an EVENT_CONTEXT. In the current specification, EVENT_CONTEXT
is only recorded on the one COMPOSITION in a CONTRIBUTION group, which
corresponds to the health system event, like a patient encounter. That means
that there is no composer on the other COMPOSITIONS in the CONTRIBUTION, which
is probably dangerous.
When the composer is the patient, the composer attribute will be set to
a value of PARTY_PROXY which corresponds logically to "self". Details of this
are in the Common IM, generic package.