Real Time Information Director User Documentation

RTID Security and Auditing
Hewlett-Packard Company 16 529618 - 002
If you look at the header, you’ll notice that it doesn’t include the consumer ID. The
reason, in this case, is that the audited event was the registration of a new patient; such a
patient would not yet have had a consumer ID assigned. The consumer, in this case,
happens also to be a doctor, the doctor we know as CDE from earlier transactions. Also
according to the header, the agent who registered the doctor as a patient was none other
than ABC, whose role was “DoctorAdmin” in the context of that transaction.
<?xml version="1.0" encoding="ISO-8859-1" ?>
-
<PERSONALDATA>
-
<HEADER>
<AGENT>ABC</AGENT>
<AGENTTYPECODE>PCP</AGENTTYPECODE>
<CONSUMERTYPECODE>PCP</CONSUMERTYPECODE>
<DATE>2004-01-24</DATE>
<ROLE>DoctorAdmin</ROLE>
</HEADER>
-
<PERSON>
<EXTERNALIDENTIFIER>GOP</EXTERNALIDENTIFIER>
<IDENTIFIERTYPECODE>PCP</IDENTIFIERTYPECODE>
<UNIQUEIDENTIFIER>1000</UNIQUEIDENTIFIER>
<DATEOFBIRTH>1972-08-27</DATEOFBIRTH>
<POSTCODE>95129</POSTCODE>
<FAMILYNAME>ROSS</FAMILYNAME>
…
-
<CONSENTMODEL>
…
</CONSENTMODEL>
-
<CONTACTS>
…
</CONTACTS>
-
<RELATIONSHIPS>
…
</RELATIONSHIPS>
-
<ADDRESSES>
…
</ADDRESSES>
</PERSON>
</PERSONALDATA
Tracking Director Transactions, End to End
In addition to recording various kinds of events in the WLS log, the Director supports
end-to-end tracking of transactions, from the arrival of a document to its insertion, or in
the case of a query, to the moment when processing is completed. Tracking occurs,
whether processing succeeded or failed.