PPA+UC+2+-+Dataset+Requirements+for+sending+eMDR





= The content within this page has been incorporated into the full Use Case posted here =

Dataset Requirements
Furthermore, it is important to understand that the identification of data elements forms the foundation for harmonization activities. The data elements identified in the Use Case set constraints on the contents of documents and messages. Workgroups should make every effort to ensure that the dataset requirements are complete, accurate, and precise.
 * Section Description: ** This table lists the data elements and data element sets) that will be available within the message or document. Historically, the optional/required nature of each data element is deferred to the discussions during the harmonization phase. Each data element listed below is necessary for some aspect of the Use Case; however, the table does not specify exactly how they may be used together. All data element sets may contain multiple data elements unless otherwise stated. For the purposes of this section, **do not** assume that any data elements are inferred. Be sure to provide elements at their most granular level. For example, if it is necessary to specify a zip code, do not use the less specific data element set, ‘address’.

Time || No || Date and Time of the eMDR || This is a timestamp created by the originator of the request and propagated by all intermediaries ||
 * //eMDR Request://**
 * **Section** || **Data Element** || **Multiple Values (yes/no)** || **Data Element Description** || **Additional Notes** ||
 * Unique eMDR Message ID || Unique eMDR Message ID || No || Unique Message ID for this eMDR || eMDR IDs must be globally unique across all payers and able to accommodate expected request volumes (Ex. UUID). Unique ID may be a concatenation of more than one data element. ||
 * Timestamp || Date
 * Payer Organization || __Demographics__
 * Name
 * Address
 * City
 * State
 * Zip Code || No || The organization’s name, street address, city, state, and zip code ||  ||
 * ^  || * Signature Artifact || No || Signature artifact encrypted by owners private key || Exact nature of artifact to be determined during harmonization ||
 * ^  || * Public Digital Certificate || No || X.509 Token Profile || Signed by trust authority ||
 * ^  || __Contact information__
 * Person / Role / Department
 * Telephone
 * Email Address || No || Information used to contact the organization by telephone or email || Contact would include a person OR department OR role. Contact information is optional ||
 * Payer Contractor || __Demographics__
 * Name
 * Address
 * City
 * State
 * Zip Code || No || The organization’s name, street address, city, state, and zip code ||  ||
 * ^  || * Signature Artifact || No || Signature artifact encrypted by owners private key || Exact nature of artifact to be determined during harmonization ||
 * ^  || * Public Digital Certificate || No || X.509 Token Profile || Signed by trust authority ||
 * ^  || __Contact information__
 * Person / Role / Department
 * Telephone
 * Email Address || No || Information used to contact the organization by telephone or email || Contact would include a person OR department OR role. Contact information is optional ||
 * Provider Organization || __ Demographics __
 * Organization Name (XYZ health system)
 * Organization Address
 * City
 * State
 * Zip Code || No || The organization’s name, street address, city, state, and zip code || As registered with NPI or alternative ID ||
 * ^  || NPI || No || NPI issued to this provider organization or organization sub-part by NPPES ||   ||
 * ^  || Alternate ID (if no NPI) || No || ID issued to this provider organization or organization sub-part by Alternative ID issuer || ID should include the issuer and the ID itself to allow tracking ||
 * Individual Provider || __ Demographics __
 * First Name
 * Middle Name
 * Last Name
 * Address
 * City
 * State
 * Zip code || No || The individual’s name, street address, city, state, and zip code || As registered with NPI or alternative ID ||
 * ^  || NPI || No || NPI issued to this provider by NPPES ||   ||
 * ^  || Alternate ID (if no NPI) || No || ID issued to this provider by Alternative ID issuer ||   ||
 * eMDR Request Information || Unique ID for eMDR Object || No || Unique ID for eMDR Object ||  ||
 * ^  || Date and Time of eMDR Object || No || The Date and time when the structured content of the eMDR included in this message was created ||   ||
 * ^  || Request Purpose || No || Purpose of eMDR || A code set will need to be identified or created that defines the purpose of the eMDR ||
 * ^  || eMDR Object || No || Structured Content of the eMDR as an object || See table below ||
 * ^  || Request Type || No || Indicator if this is a replacement to a prior request, a new request, or a termination request || Values: ‘New,’ ‘Replacement,’ ‘Termination’ ||
 * Message Signature || Public Digital certificate of transmitter || No || X.509 Token Profile || Signed by trust authority ||
 * ^  || Encrypted hash of message || No || Digest (hash) of the message encrypted with the transmitters private key ||   ||