Real Time Information Director User Documentation

RTID Metadata Language
Hewlett-Packard Company 5 529618-002
• To specify audit options for specific types of documents
Reasons to Customize Metadata
The starting data model and metadata for a vertical industry provide a head start toward
developing a real-time solution for a customer, but every company will want to enhance
the data model and metadata.
Different companies, and even regional subsidiaries of companies, use the SAP data
model differently. Not only do business units vary in what IDocs they support, but
business-critical data might be stored in customer-defined SAP elements. Different
mappings of the same IDoc might be required to reconcile uses of SAP within regions,
subsidiaries, and acquired companies.
The same considerations apply to a healthcare solution. Different clinical systems might
support different HL7 messages or options within messages.
In addition to variations in the types of documents supported, customers will vary in how
they define the information to be captured in the data store. The RTSC data model, for
example, does not store every data element from every supported IDoc. In the field of
Electronic Health Records, health authorities might have different ideas about what
clinical data to include in the EHR data store. Thus, customers will require extensions or
modifications of starting data models.
Finally, solutions will vary in what kinds of documents need to be delivered to users. For
example, a supply-chain visibility application might demand information collected and
aggregated from various SAP IDocs, and an EHR system might need to support many
different kinds of queries from healthcare providers, patients, and hospital administrators.
Characteristics of Director Metadata
Director metadata is
• Descriptive
• Polymorphic
• Implemented in Java
• Easy to write