Business name: B: Care Composition Identifier

Unique identifier of an encounter, condition or care-based collection.

Allows care compositions to be uniquely identified and referenced, and is therefore mandatory

IMMUNIZATION INTERPRETATION.REFERENCED DATA

Business name: A: Care Composition Type

Identifies the kind of composition represented. Examples include encounters ("Emergency Encounter", "Long Term Care Encounter", etc), health condition (episode)-based collections (e.g. "Diabetes", "Hypertension", etc) and general care-based collections such as "gynecological care".

Allows care compositions to be captured and categorized at different levels of abstraction, and is therefore mandatory.

EPHS: vocab concepts needed for LAB ID, Special Considerations ID etc.

IMMUNIZATION INTERPRETATION.REFERENCED DATA

Business name: K:Other Identifier

Alternate Identifiers for the Patient (e.g., Drivers License number, Health insurance number).

Other identification numbers associated with identifying a patient.

Business name: J:Other Identifier Type

Describes the identification type (driver's license, etc.)

Used to set the type of identier

Business name: Identifying Charateristics Observation Type

Describes the observation type. For this usage, the observation type is fixed to LOINC code "10186-5"

Used to categorize this observation event. For this model, the observation is a description of patient characteristics used for identification.

invariant( x) { code.code = 10186-5 code.codeSystemName = LOINC; }

Business name: I:Patient Characteristics Text

A text attribute that is specifically used to describe identifying characteristics of a patient.

When a lab does not have access to the client registry to identify the patient, additional information is helpful in patient identification. This text description allows for non-coded patient descriptive details which don't change measurable over time and can be used to assist in patient identification.

Business name: A:Patient Identifier

Business name: E:Patient Address

Business name: F:Patient Contact Phone and E-Mails

Business name: L:Patient Health Card Version Code

Business name: B:Patient Name

The name by which the patient is known and which apply to a particular clinical action that has been reported or recorded.

Used, with other patient identity attributes, to confirm patient identity, as well as when addressing the patient. Element is populated because the patient's name is frequently necessary for positive identification of the patient in the jurisdictional client registry.

Business name: D:Patient Gender

Indicates the gender (sex) of the patient. Complex genetic genders are handled as observations if they are considered relevant.

Used to confirm patient identity.

Business name: C: Patient Birth Datetime

Indicates the date on which the patient was born.

Used to confirm patient identity.

Business name: G:Patient Deceased Indicator

Indicates whether the patient is deceased.

Business name: H:Patient Deceased Datetime

The date/time the patient died or was ruled "deceased."

Business name: A:Patient Identifier

Unique identifier issued as part of the patient identity verification process.

Allows a patient to be referred to unambiguously. Because this is the principal mechanism for identifying patients to electronic systems, the attribute is mandatory.

C39 (Extension)

PTT.050.01 (Extension)

PTT.050.02 (Root)

A.1

PID.2

Patient.332-CY (Extension)

Patient.331-CX (Root)

Claim.330-CW

Health Card Number

PID.2

PID.4

ZDU.2

ZKW.3

Jurisdiction (Root)

Person.PHN (Extension)

Business name: A:Patient Identifier

Unique identifier assigned to a person by Federal, Provincial and Territorial jurisdiction for the purposes of uniquely identifying the person within the EHR.

The EHR will define which identifier to use within a jurisdiction.

Allows a patient to be referred to unambiguously. Because this is the principal mechanism for identifying patients to computer systems, the attribute is mandatory. If an identifier is not known, it should be looked up using the 'client registry' capabilities of the EHR application.

C39 (Extension)

PTT.050.01 (Extension)

PTT.050.02 (Root)

A.1

PID.2

Patient.332-CY (Extension)

Patient.331-CX (Root)

Claim.330-CW

Health Card Number

PID.2

PID.4

ZDU.2

ZKW.3

Jurisdiction (Root)

Person.PHN (Extension)

Business name: B:Patient Name

The name by which the patient is known to the underlying client registry application

Used, with other patient identity attributes, to confirm patient identity.

This element is 'populated' because the patient's name is necessary for positive identification of the patient in the jurisdictional client registry, however in some circumstances it may not exist in the registry (e.g. newborn).

ZPA.1 (partType=Given)

ZPA.2 (partType=Family)

ZPA.3 (partType=Given - all repetitions except first)

C37 (partType=Given)

C38 (partType=Family)

PTT.030-01 (partType=Family)

PTT.030-02 (partType=Given - 1st occurrence)

PTT.030-03 (partType=Given - subsequen occurrences)

PTT.030-04 (partType=Suffix)

PTT.030-05 (partType=Prefix)

patient Initials

PID.5

Patient.310-CA (partType=Given)

Patient.311-CB (partType=Family)

Recipient Name First (partType=Given)

Recipient Name Last (partType=Family)

PID.5

PID.9 (any name other than first repetition is an alias)

ZDU.3

ZKW.2

Person.givenName

Person.lastName

Person.middleName

Person.namePrefix

Person.nameSuffix

Business name: F:Patient Gender

Indicates the gender (sex) of the patient as known by the client registry. Complex genetic genders are handled as observations if they are considered relevant.

Used to confirm patient identity.

The element is mandatory because the patient's gender is necessary for positive identification of the patient in the jurisdictional client registry and should always be known.

Business name: E:Patient Birth Date

Indicates the date on which the patient was born, as known by the client registry.

Used to confirm patient identity.

This element is 'populated' because the patient's birth date is necessary for positive identification of the patient in the jurisdictional client registry. However, there may be circumstances where the date of birth is not known to the registry.

Business name: A:Patient Identifier

Unique identifier assigned to a person, possibly by a local system or some other non-client-registry identifier.

Allows a patient to be referred to unambiguously. Because this CMET deals with patients not confirmable against a client registry, it's possible that no identifier will be known and therefore the attribute is only 'populated'.

C39 (Extension)

PTT.050.01 (Extension)

PTT.050.02 (Root)

A.1

PID.2

Patient.332-CY (Extension)

Patient.331-CX (Root)

Claim.330-CW

Health Card Number

PID.2

PID.4

ZDU.2

ZKW.3

Jurisdiction (Root)

Person.PHN (Extension)

Business name: C:Patient Contact Address

Physical address for the patient where they may be visited or found.

Contact information specific to the patient for a particular action (prescription, lab test, etc.) will be conveyed as part of the payload.

Provides basic contact information for the patient.

ZPA2.1 (use)

ZPA2.2 (usablePeriod(IVL<TS).low)

ZPA2.4 (partType=UNID)

ZPA2.5 (DMODID - following DMOD=P.P.Box)

ZPA2.6 (partType=??)

ZPA2.7 (partType=??)

ZPA2.8 (partType=CTY)

ZPA2.9 (partType=CNT - populate mnemonic of SC)

ZPA2.10 (partType=ZIP)

ZPA2.11 (partType=SINST=PST)

ZPA2.12 (partTYpe=STA)

ZPA2.13 (partType=DMODID-followingDMOD=RR)

ZPA2.14 (partType=DIR)

ZPA2.15 (partType=STB)

ZPA2.16 (partType=BNR) BC:ZPA2.17 (partType=STTYP)

ZPA2.18 (usablePeriod (IVL<TS).high)

ZPA2.19 (Line demarked by carriage return)

PTT.060-01 (partType=SAL)

PTT.060-02 (partType=CTY)

PTT.060-03 (partType=CNT)

PTT.060-04 (partType=ZIP)

PID.11

Patient.322-CM (partType=SAL)

Patient.323-CN (partType=CTY)

Patient.324-CO (partType=STA)

Patient.325-CP (partType=ZIP)

PID.11

Business name: D:Patient Contact Phone and E-mails

Telephone, fax and/or e-mail addresses intended as the principal means of contact for the patient.

Contact information specific to the patient for a particular action (prescription, lab test, etc.) will be conveyed as part of the payload.

Provides basic contact information for the patient.

Important for following up with patient but not always available, and therefore only marked as 'populated'.

ZPA1.1 (Use and/or URL.scheme)

ZPA1.2 (usablePeriod (IVL<TS>).low) BC:ZPA1.3 (url.address - as per RFC2396)

ZPA1.4 (url.address - as per RFC2396)

ZPA1.5 (usablePeriod (IVL<TS>).high)

PTT.070-01

PTT.070-02

D99.03 (url.address - as per RFC2396)

patient.326-CQ

PID.13

PID.14

Business name: B:Patient Name

The name by which the patient is known.

Used by to help identify the patient and also when referring to the patient

The element is populated because the patient's name is important for display. However, there may be circumstances where a name is not known by the reporting system.

ZPA.1 (partType=Given)

ZPA.2 (partType=Family)

ZPA.3 (partType=Given - all repetitions except first)

C37 (partType=Given)

C38 (partType=Family)

PTT.030-01 (partType=Family)

PTT.030-02 (partType=Given - 1st occurrence)

PTT.030-03 (partType=Given - subsequen occurrences)

PTT.030-04 (partType=Suffix)

PTT.030-05 (partType=Prefix)

patient Initials

PID.5

Patient.310-CA (partType=Given)

Patient.311-CB (partType=Family)

Recipient Name First (partType=Given)

Recipient Name Last (partType=Family)

PID.5

PID.9 (any name other than first repetition is an alias)

ZDU.3

ZKW.2

Person.givenName

Person.lastName

Person.middleName

Person.namePrefix

Person.nameSuffix

Business name: F:Patient Gender

Indicates the gender (sex) of the patient as known by the client registry. Complex genetic genders are handled as observations if they are considered relevant.

Used to confirm patient identity. May affect clinical decision support such as drug dosing, lab test appropriateness, etc.

The element is 'populated' because there are some situations where the patient's gender may not be known by the sending system when dealing with non-client registry patients.

C40 eScript:PTT.040

3

Sex

PID.8

Patient.305-C5

PID.8

Business name: E:Patient Birth Date

Indicates the date on which the patient was born as known by the client registry.

Used to confirm patient identity.

May also influence clinical decision support such as dosage and therapy appropriateness.

The element is populated because the patient's birth date may not be known, particularly for patients not found in the client registry.

C34

PTT.020

A.2b

HC-SA

PID.7

patient.304-C4

PID.7

Business name: A:Patient Identifier

Unique identifier assigned to a person by Federal, Provincial and Territorial jurisdiction for the purposes of uniquely identifying the person within the EHR.

The EHR will define which identifier to use within a jurisdiction.

Allows a patient to be referred to unambiguously. Because this is the principal mechanism for identifying patients to computer systems, the attribute is mandatory.

C39 (Extension)

PTT.050.01 (Extension)

PTT.050.02 (Root)

A.1

PID.2

Patient.332-CY (Extension)

Patient.331-CX (Root)

Claim.330-CW

Health Card Number

PID.2

PID.4

ZDU.2

ZKW.3

Jurisdiction (Root)

Person.PHN (Extension)

Business name: C:Patient Contact Address

Physical address for the patient where they may be visited or found.

Contact information specific to the patient for a particular action (prescription, lab test, etc.) will be conveyed as part of the payload.

Provides basic contact information for the patient avoiding the need to separately query the client registry.

ZPA2.1 (use)

ZPA2.2 (usablePeriod(IVL<TS).low)

ZPA2.4 (partType=UNID)

ZPA2.5 (DMODID - following DMOD=P.P.Box)

ZPA2.6 (partType=??)

ZPA2.7 (partType=??)

ZPA2.8 (partType=CTY)

ZPA2.9 (partType=CNT - populate mnemonic of SC)

ZPA2.10 (partType=ZIP)

ZPA2.11 (partType=SINST=PST)

ZPA2.12 (partTYpe=STA)

ZPA2.13 (partType=DMODID-followingDMOD=RR)

ZPA2.14 (partType=DIR)

ZPA2.15 (partType=STB)

ZPA2.16 (partType=BNR) BC:ZPA2.17 (partType=STTYP)

ZPA2.18 (usablePeriod (IVL<TS).high)

ZPA2.19 (Line demarked by carriage return)

PTT.060-01 (partType=SAL)

PTT.060-02 (partType=CTY)

PTT.060-03 (partType=CNT)

PTT.060-04 (partType=ZIP)

PID.11

Patient.322-CM (partType=SAL)

Patient.323-CN (partType=CTY)

Patient.324-CO (partType=STA)

Patient.325-CP (partType=ZIP)

PID.11

Business name: D:Patient Contact Phone and E-mails

Telephone, fax and/or e-mail addresses intended as the principal means of contact for the patient.

Contact information specific to the patient for a particular action (prescription, lab test, etc.) will be conveyed as part of the payload.

Provides basic contact information for the patient avoiding the need to separately query the client registry.

Important for following up with patient but not always available, and therefore only marked as 'populated'.

ZPA1.1 (Use and/or URL.scheme)

ZPA1.2 (usablePeriod (IVL<TS>).low) BC:ZPA1.3 (url.address - as per RFC2396)

ZPA1.4 (url.address - as per RFC2396)

ZPA1.5 (usablePeriod (IVL<TS>).high)

PTT.070-01

PTT.070-02

D99.03 (url.address - as per RFC2396)

patient.326-CQ

PID.13

PID.14

Business name: B:Patient Name

The name by which the patient is known to the client registry.

Potentially used by PoS systems to confirm patient identity. Also acts as the visual confirmation to the user about the patient being viewed.

The element is populated because the patient's name is important for display. However, there may be circumstances where a name is not available in the registry (e.g. newborns).

ZPA.1 (partType=Given)

ZPA.2 (partType=Family)

ZPA.3 (partType=Given - all repetitions except first)

C37 (partType=Given)

C38 (partType=Family)

PTT.030-01 (partType=Family)

PTT.030-02 (partType=Given - 1st occurrence)

PTT.030-03 (partType=Given - subsequen occurrences)

PTT.030-04 (partType=Suffix)

PTT.030-05 (partType=Prefix)

patient Initials

PID.5

Patient.310-CA (partType=Given)

Patient.311-CB (partType=Family)

Recipient Name First (partType=Given)

Recipient Name Last (partType=Family)

PID.5

PID.9 (any name other than first repetition is an alias)

ZDU.3

ZKW.2

Person.givenName

Person.lastName

Person.middleName

Person.namePrefix

Person.nameSuffix

Business name: F:Patient Gender

Indicates the gender (sex) of the patient as known by the client registry. Complex genetic genders are handled as observations if they are considered relevant.

Used to confirm patient identity. May affect clinical decision support such as drug dosing, lab test appropriateness, etc.

Element is mandatory because the patient's gender is necessary for positive identification of the patient in the jurisdictional client registry and should always be known.

C40 eScript:PTT.040

3

Sex

PID.8

Patient.305-C5

PID.8

Business name: E:Patient Birth Date

Indicates the date on which the patient was born as known by the client registry.

Used to confirm patient identity.

May also influence clinical decision support such as dosage and therapy appropriateness.

The element is populated because the patient's birth date is necessary for positive identification of the patient in the jurisdictional client registry. However, in some cases the date of birth may not be known to the client registry

C34

PTT.020

A.2b

HC-SA

PID.7

patient.304-C4

PID.7

Business name: Y:Specimen Container Risk

Describes any risk to the handlers of this container (containing a specimen).

Used to document container risks to those who handle the container.

Business name: Other Specimen Identifiers

Associated specimen identifiers.

For referral and redirected orders, this information helps keep track of the different id's assigned during each phase of processing.

Business name: Other Specimen Identifier Type

Describes the type of other specimen identifier (referral, primary, etc.)

Categorized the type of role identifier.

Business name: V:Specimen Code

The code of the specimen material collected e.g. skin, blood, etc.

The specimen code differentiates testing types, methods, and resulting processing of specimen material.

Business name: W:Specimen Text

Any descriptive specimen information not sufficiently communicated by the code attribute.

Used when information is not able to be coded or represented using the available other attributes.

Business name: Organization Identifier

A unique identifier for the organization

Allows the organization to be referenced when determining privileges and for drill-downs to retrieve additional information. Because of its importance, the attribute is mandatory.

Business name: Organization Name

Identifies the name of the organization

Allows for human recognition of the organization as well as confirmation of the identifier. As a result, the attribute is mandatory.

Business name: A:Specimen Identifier

A unique identifier for the specimen. Frequently the accession number which often uniquely identifies the specimen is used as the unique specimen identifier in communications. However, accessioning may group multiple specimens (identified) under one accession number. Therefore, it is recommended that this be truly the specimen identifier and not the accession number.

For a referral, this attribute should be Required so it is reflected back in the result. If Lab A has collected and or done something to the specimen, then the identifier would be sent.

A unique specimen identifier is necessary for specimen tracking and management.

The specimen is a product of a specimen collection procedure. This productOf participation associates an identified specimen with the documentation of that specimen's collection process.

Business name: G:Specimen Collection Text

Used to describe any additional information regarding the specimen collection procedure or the collected material, e.g. left ear; where "ear" is atomically represented by the Natural entity code but the "left" is not able, at this time, to also be communicated within the Natural entity. This attribute is not used for notes or comments regarding the specimen collection process. Notes and annotations are documented using the Annotation CMET.

The text attribute documents any additional information regarding this specimen collection procedure event that is not able to be communicated using the other attribution of this act e.g. for granularity of coding reasons.

Business name: E:Specimen Collection Date/Time

The date/time the specimen was collected. This can be a date/time interval (start - stop).

The time may not always be known, but a date should always be entered.

The specimen collection date/time is relevant to the testing and resulting outcome of that specimen for some laboratory tests.

Business name: Specimen Observation Type

Describes the specific observation being performed/documented.

Type of observation.

Business name: Specimen Observation Date/Time

When this observation took place (or over what time interval; for collection).

The date/time when the observation took place. The date and time of the specimen observation can be relevant in the result.

Business name: Specimen Observation Value

Business name: P:Transportation Type

Describes the type of process step being documented and communicated e.g. specimen received data, specimen action codes, transportation type.

Categorizes the type of transportation act being communiated.

Business name: R:Transportation Status

The state or status of this transportation process step.

Indicates (along with the mood) whether this act's action has been completed or is still being acted upon (or has yet to be acted upon).

Business name: Q:Transportation Date/Time

The date/time the process step took place or the duration of that step (days or time in transit, start time, end time).

Holds the date/time the process step took place. This attribute is especially important for those process steps which document the date/time the process happened (specimen received date/time).

Business name: A: Healthcare Worker Identifier

Unique identifier the person involved in the action.

Allows unique identification of the person which can be critical for authentication, permissions, drill-down and traceability and is therefore mandatory.

Business name: C: License Number

The license number issued to the provider and relevant to the current action.

If the identifier used in the root of the CMET is the same as the license number, the license number should be sent in both places.

Allows lookup on college website, confirmation of identity, etc. Regulations occasionally require license numbers to be specified as part of clinical records.

Business name: D: Organization identifier

A unique identifier for the organization

Allows the organization to be referenced when determining privileges and for drill-downs to retrieve additional information. Because of its importance, the attribute is mandatory.

Business name: E: Organization Name

Identifies the name of the organization

Allows for human recognition of the organization as well as confirmation of the identifier. As a result, the attribute is mandatory.

Business name: B: Healthcare Worker Name

The name of the involved person.

This is a human-readable name and is essential for validation of the person. As a result, the attribute is mandatory

Business name: A:Healthcare Worker Identifier

Unique identifier the person involved in the action.

Allows unique identification of the person which can be critical for authentication, permissions, drill-down and traceability and is therefore mandatory.

Business name: B: Healthcare Worker Type

Indicates the "kind" of healthcare participant, such as "physician", "dentist", "lab technician", "receptionist", etc.

Provides context around the actions of the participant and is therefore mandatory.

Business name: E: Healthcare Worker Phone and Emails

Indicates phone and/or e-mail addresses at which the healthcare worker can be reached.

This is the most commonly used piece of contact information and is returned here to avoid unnecessary queries of the provider registry.

Business name: G: Organization Type

Identifies the type of organization on whose behalf the action was taken. E.g. Pharmacy, Clinic, Hospital, etc.

Provides context to the action and is therefore mandatory.

Business name: I: Organization Phone and Emails

Identifies contact information for the responsible organization.

This is the most commonly used contact information and is returned to avoid unnecessary queries against the client registry.

Business name: D: License Number

The license number issued to the provider and relevant to the current action.

If the identifier used in the root of the CMET is the same as the license number, the license number should be sent in both places.

Detailed information about the status and effective period of licenses must be retrieved from the provider registry.

Allows lookup on college website, confirmation of identity, etc. Regulations occasionally require license numbers to be specified as part of clinical records.

Business name: F: Organization identifier

A unique identifier for the organization

Allows the organization to be referenced when determining privileges and for drill-downs to retrieve additional information. Because of its importance, the attribute is mandatory.

Business name: H: Organization Name

Identifies the name of the organization

Allows for human recognition of the organization as well as confirmation of the identifier. As a result, the attribute is mandatory.

Business name: C: Healthcare Worker Name

The name of the participating person.

This is a human-readable name and is thus essential for both display and validation of the person. As a result, the attribute is mandatory.

Business name: C:Application Id

Unique identifier of an application or a system.

To uniquely identify an application/system.

Attribute is mandatory to allow for distinguishing different applications/systems.

PVD.020-01 (extension)

PVD.020-02 (root)

Dispensing Pharmacy number

Pharmacy Identifier

Facility.facilityKey

DispensedItem.facilityKey

Business name: B: Application Name

The name assigned to the application/system.

Used for human communication. The name of the application must be known and is therefore marked as 'mandatory'.

PVD.070

Dispensing Pharmacy Name

Facility.name

Business name: Repository Identifier

A unique identifier for the EHR repository.

Allows repositories to be uniquely identified for linking or grouping purposes and is therefore mandatory.

Business name: Repository Name

The name of the repository which is responsible for maintaining the record. E.g. "Ontario Health Respository #3"

Provides a human-readable name for the repository and is therefore mandatory

Business name: Repository Jurisdiction Name

The name of the jurisdiction that is responsible for the EHR infostructure that contains and manages the record.

Establishes business context for determining custodianship, and is therefore mandatory.

Business name: D: Organization identifier

A unique identifier for the organization

Allows the organization to be referenced when determining privileges and for drill-downs to retrieve additional information. Because of its importance, the attribute is mandatory.

Business name: E: Organization Name

Identifies the name of the organization

Allows for human recognition of the organization as well as confirmation of the identifier. As a result, the attribute is mandatory.

Business name: F: Organization Type

Identifies the type of organization on whose behalf the action was taken. E.g. Pharmacy, Clinic, Hospital, etc.

Provides context to the action and is therefore mandatory.

Business name: H: Organization Phone and Emails

Identifies contact information for the responsible organization.

This is the most commonly used contact information and is returned to avoid unnecessary queries against the client registry.

Business name: E: Organization identifier

A unique identifier for the organization

Allows the organization to be referenced when determining privileges and for drill-downs to retrieve additional information. Because of its importance, the attribute is mandatory.

Business name: G: Organization Name

Identifies the name of the organization

Allows for human recognition of the organization as well as confirmation of the identifier. As a result, the attribute is mandatory.

Business name: Diagnosis Type

Identifies the type of condition described (diagnosis or indication)

Identifies this measurement as a type of diagnosis and is therefore mandatory.

Business name: A:Diagnosis Code

A coded form of the diagnosis that is the reason for the current action.

Allows cross-checking the use of a therapy against its indication. Also allows analysis of best practices, etc. This is the attribute that actually identifies the indication and is therefore mandatory.

This element makes use of the CD datatype because some terminologies used for the domain require use of modifiers.

Business name: Other Indication

A code indicating some other action which is the reason for a therapy.

Allows for coded representation of a non-condition based indication such as administration of a contrast agent for a lab test.

EPHS: vocab proposal needed for simple concepts of i) sign or symptom related to investigation disease ii) sign or symptom not related to investigation disease. EPHS: act.code value needed for encounter reason; reason for treatment; immunization interpretation reason

Business name: Other indication ad-hoc description

A textual description of an indication not meant to be either diagnosis or symptom.

Provides ability to describe indication without labeling it a diagnosis or symptom. Attribute as free form text is the only information allowed.

Business name: B: Note Text

Free text comments. Additional textual iinformation entered about an object.

Allows a provider to attach comments to objects for communication. This attribute is mandatory because there's no point in having a note class unless there's actually content in the note.

Language is supported to allow grouping or filtering comments based on language

Business name: A: Note Timestamp

The date and time at which the note was posted.

Identifies timing of the annotation for sorting and for audit purposes.

This attribute is mandatory because the time of creation of the annotation will always be known.

Business name: Change Datetime

The date on which the change was made. Note that this may be earlier or occassionally later than when the change is actually effective.

Gives other providers the frame of reference in evaluating any post-change issues with the event. Also used for sorting and audit purposes. Time of change is always known and thus the attribute is mandatory.

Business name: B:Change Identifier

A unique identifier for this particular change.

Allows referencing (and potentially undoing) a specific change. Every status change has an identifier, thus this attribute is mandatory.

Business name: A:Change Type

Identifies what kind of change occurred.

This attribute is mandatory to ensure that change types are distinguishable.

Business name: C:Change Effective Date and End Date

The date on which the various changes of an event become valid and applicable and potentially when the change is supposed to cease.

Allows applications to sort and filter by time. The date on which a change is effective should always be known and thus is mandatory. The end date may be left unspecified if there isn't a specific targetted end date (e.g. with a suspend including a planned release date).

Business name: D:Change Reason

Denotes the reason the record was modified.

Ensures consistent terminology in capturing and interpreting reasons for change. Allows CWE because not all reasons will correspond to a pre-defined code.

Business name: A:Device Code

An identifier for a type of device.

Used to ensure clear communication by uniquely identifying a particular device product when prescribing or dispensing. This attribute is only marked as 'populated' because some devices will not have codes associated with them.

Business name: B:Device Name

The name assigned to a type of device.

First occurrence is preferred for display.

Names are used for human reference communication, to allow selection from dropdowns and for local searching. If a code is available, the name acts as a cross-check. If the code is not available the name acts as the primary identifier. The attribute is therefore mandatory.

Business name: C:Device Description

A free form textual description of a device and its characteristics (e.g. size, shape, etc.). This is used when additional information must be conveyed that is not apparent by just specifying code and name.

Allows description of characteristics of the device not necessarily conveyed by the code or name.

Business name: F:Device Package Quantity

The quantity of devices contained in the package given or to be given to the patient.

Sometimes ordering and dispensing is by package rather than individual units, and package is important in calculating total amount supplied.

Attribute is marked as "mandatory" to ensure that quantity in a package is always known.

Business name: F:Drug Package Quantity

The quantity of the medication dosage form contained in the package given or to be given to the patient.

Sometimes ordering and dispensing is by package rather than individual units, and package is important in calculating total amount supplied.

ZDP.10.2.2

ZDP.9.2.2

Business name: D:Drug Does Not Contain Indicator

An indication that a drug does not contain the specified ingredient (active or inactive).

Useful for filtering searches. Allows providers to search for drugs not containing a specific active ingredients or excipients. E.g. lactose-free, gluten-free, etc.

The attribute is 'populated' because the distinction between "does/must contain" and "does/must not contain" is essential, however in some circumstances it is necessary to say "may contain".

Business name: C:Drug Ingredient Quantity

The quantity of the ingredient in a drug. This is represented/measured in various forms/units including: mg, mg/vol, %, etc.

Essential for evaluating appropriate dosage based on strength, as well as for creating custom compounds with proper composition.

CompoundIngredient.amount(numerator)

CompoundIngredient.proportionOfFinal(e.g. 10% = .1mg/1mg)

ZPC.4(quantity)

ZPC.5(unit)

ZPJ1.4(quantity)

ZPJ1.5(unit)

ZPJ1.6(e.g. 10% = .1mg/1mg)

ZCP.3

ZDU.4.3

ZDU.6.1.2

Compound.448-ED (quantity)

Compound.451-EG (unit)

Business name: A:Drug Code

An identifier for a type of drug. Depending on where the drug is being referenced, the drug may be identified at different levels of abstraction. E.g. Manufactured drug (including vaccines), generic formulation, generic, therapeutic class, etc.

Used to ensure clear communication by uniquely identifying a particular drug product when prescribing or dispensing. This attribute is only marked as 'populated' because some custom compounds will not have unique identifiers Datatype has been retained as CE (Translatable Code) to support translation between multiple code sets for drugs (e.g. DIN, GTIN, UPC).

DrugProduct.activeIngredientId

DrugProduct.ActiveIngredientGroupNumber

DrugProduct.DIN

DrugProduct.StandardProductId (Mnemonic)

DrugProduct.StandardIDType(Code System)

D56(use code system to distinguish different types)

ZPB2.1

ZPB3.1

ZPC.1

ZPC1.3

ZPD.1

ZPD1.1

ZPD.6(scoping a specialized kind of therapeutic equivalent)

MB.05.03B

ZPS.11

ZDP.3a(code system)

ZDU.4.1

ZDP.7

DRU.010-03(mnemonic)

DRU.010-04(code system)

DRU.010-08(mnemonic)

DRU.010-09(code system)

DRU.100-04 (mnemonic)

DRU.100-05 (code system)

Compound.488-RE (code system)

Compound.489-TE (mnemonic)

DUR/PPS.475-J9 (code system)

DUR/PPS.476-H6 (mnemonic)

Claim.436-E1 (code system)

Claim.407-D7 (mnemonic)

Claim.453-EJ (code system)

Claim.445-EA (mnemonic)

Claim.406-D6 (determined from code system)

RXA.5

A_BillablePharmacyDispense

Business name: B:Drug Name

The name assigned to a drug.

First occurrence is preferred for display.

Names are used for human reference communication, to allow selection from dropdowns and for local searching. If a code is available, the name acts as a cross-check. If the code is not available the name acts as the primary identifier. The attribute is therefore mandatory.

DrugProduct.Name (Search)

CoumpoundDrugProduct.name

Contraindication.interactingDrugName

DrugProduct.labelName(useCode=L)

ZPB2.2

ZPB3.2

ZPC.2

ZPD.2

ZPD1.2

ZPD.5

MB.01.03

Drug Name

ZDU.4.2

ZDU.6.1.1

DRU.010-02

RXA.TradeName

DRU.010-10->12

Brand Name

C.1a

Trade Name

Other Name

Business name: C:Drug Description

A free form textual description of a drug. This usually is only populated for custom compounds, providing instructions on the composition and creation of the compound.

Allows description of compound ingredients and/or recipe in free text form.

DrugProduct.description

CompoundedDrugProduct.adhocSpecification

DRU.010-06

DIN Description

Business name: D:Drug Form

Indicates the form in which the drug product must be, or has been manufactured or custom prepared.

Must be recorded if the Drug Id does not specify the Drug Form.

Provides a constrained vocabulary for describing dose forms. The form of the drug influences how it can be used by the patient.

Prescription.dosageForm

DrugProduct.dosageForm

CompoundedDrugProduct.dosageForm

DispensedItem.dosageForm

D63

ZPC.3

ZPD.3

Drug form

ZDP.14.1

ZDP.3b

DRU.010-05

Compound.450-EF

A_BillablePharmacyDispense

Dosage Form

Dosage Form

Business name: Drug Container Type

A coded value denoting a specific kind of a container. Used to identify a requirement for a particular type of compliance packaging

Many insurance plans require that a prescriber specifically authorize the use of compliance packaging before it will be covered by the plan.

Business name: A:Drug Ingredient Identifier

The unique identifier for the drug or chemical.

Allows un-ambiguous identification of the ingredients of a drug for performing various alert checking.

Also allows for the identification of antigens as class of ingredients in a vaccine.

CompoundIngredient.IngredientDrug.activeIngredientCode

CompoundIngredient.IngredientDrug.DIN

CompoundIngredient.IngredientDrug.hcAigNumber

CompoundIngredient.IngredientDrug.standardProductId(mnemonic)

CompoundIngredient.IngredientDrug.standardProductIdType(code system)

ZPB3.6(mnemonic)

ZPB3.7(print name)

ZPJ1.1(mnemonic)

ZPJ1.2(print name)

ZCP.2

Business name: B:Drug Ingredient Name

The name of the contained drug or chemical.

Used for communication between and display to providers.

CompoundIngredient.IngredientDrug.drugProductName

Business name: F:Drug Package Quantity

The quantity of the medication dosage form contained in the package given or to be given to the patient.

Sometimes ordering and dispensing is by package rather than individual units, and package is important in calculating total amount supplied.

ZDP.10.2.2

ZDP.9.2.2

Business name: D:Drug Does Not Contain Indicator

An indication that a drug does not contain the specified ingredient (active or inactive).

Useful for filtering searches. Allows providers to search for drugs not containing a specific active ingredients or excipients. E.g. lactose-free, gluten-free, etc.

The attribute is 'populated' because the distinction between "does/must contain" and "does/must not contain" is essential, however in some circumstances it is necessary to say "may contain".

Business name: C:Drug Ingredient Quantity

The quantity of the ingredient in a drug. This is represented/measured in various forms/units including: mg, mg/vol, %, etc.

Essential for evaluating appropriate dosage based on strength, as well as for creating custom compounds with proper composition.

CompoundIngredient.amount(numerator)

CompoundIngredient.proportionOfFinal(e.g. 10% = .1mg/1mg)

ZPC.4(quantity)

ZPC.5(unit)

ZPJ1.4(quantity)

ZPJ1.5(unit)

ZPJ1.6(e.g. 10% = .1mg/1mg)

ZCP.3

ZDU.4.3

ZDU.6.1.2

Compound.448-ED (quantity)

Compound.451-EG (unit)

Business name: Manufacturer Id

An identifier denoting a specific drug manufacturer.

Allows sending of identifiers in place of manufacturer name. May be used in drug search where specific manufacturer is a criterion.

Business name: Manufacturer Name

The name of the drug manufacturer.

Used for reporting.

The attribute is marked as "mandatory" because there will always be a name for an organization.

Business name: A:Drug Code

An identifier for a type of drug. Depending on where the drug is being referenced, the drug may be identified at different levels of abstraction. E.g. Manufactured drug (including vaccines), generic formulation, generic, therapeutic class, etc.

Used to ensure clear communication by uniquely identifying a particular drug product when prescribing or dispensing. This attribute is only marked as 'populated' because some custom compounds will not have unique identifiers Datatype has been retained as CE (Translatable Code) to support translation between multiple code sets for drugs (e.g. DIN, GTIN, UPC).

DrugProduct.activeIngredientId

DrugProduct.ActiveIngredientGroupNumber

DrugProduct.DIN

DrugProduct.StandardProductId (Mnemonic)

DrugProduct.StandardIDType(Code System)

D56(use code system to distinguish different types)

ZPB2.1

ZPB3.1

ZPC.1

ZPC1.3

ZPD.1

ZPD1.1

ZPD.6(scoping a specialized kind of therapeutic equivalent)

MB.05.03B

ZPS.11

ZDP.3a(code system)

ZDU.4.1

ZDP.7

DRU.010-03(mnemonic)

DRU.010-04(code system)

DRU.010-08(mnemonic)

DRU.010-09(code system)

DRU.100-04 (mnemonic)

DRU.100-05 (code system)

Compound.488-RE (code system)

Compound.489-TE (mnemonic)

DUR/PPS.475-J9 (code system)

DUR/PPS.476-H6 (mnemonic)

Claim.436-E1 (code system)

Claim.407-D7 (mnemonic)

Claim.453-EJ (code system)

Claim.445-EA (mnemonic)

Claim.406-D6 (determined from code system)

RXA.5

A_BillablePharmacyDispense

Business name: B:Drug Name

The name assigned to a drug.

First occurrence is preferred for display.

Names are used for human reference communication, to allow selection from dropdowns and for local searching. If a code is available, the name acts as a cross-check. If the code is not available the name acts as the primary identifier. The attribute is therefore mandatory.

DrugProduct.Name (Search)

CoumpoundDrugProduct.name

Contraindication.interactingDrugName

DrugProduct.labelName(useCode=L)

ZPB2.2

ZPB3.2

ZPC.2

ZPD.2

ZPD1.2

ZPD.5

MB.01.03

Drug Name

ZDU.4.2

ZDU.6.1.1

DRU.010-02

RXA.TradeName

DRU.010-10->12

Brand Name

C.1a

Trade Name

Other Name

Business name: C:Drug Description

A free form textual description of a drug. This usually is only populated for custom compounds, providing instructions on the composition and creation of the compound.

Allows description of compound ingredients and/or recipe in free text form.

DrugProduct.description

CompoundedDrugProduct.adhocSpecification

DRU.010-06

DIN Description

Business name: D:Drug Form

Indicates the form in which the drug product must be, or has been manufactured or custom prepared.

Must be recorded if the Drug Id does not specify the Drug Form.

Provides a constrained vocabulary for describing dose forms. The form of the drug influences how it can be used by the patient.

Prescription.dosageForm

DrugProduct.dosageForm

CompoundedDrugProduct.dosageForm

DispensedItem.dosageForm

D63

ZPC.3

ZPD.3

Drug form

ZDP.14.1

ZDP.3b

DRU.010-05

Compound.450-EF

A_BillablePharmacyDispense

Dosage Form

Dosage Form

Business name: E:Drug Container Type

A coded value denoting a specific kind of a container. Used to identify a requirement for a particular type of compliance packaging

Many insurance plans require that a prescriber specifically authorize the use of compliance packaging before it will be covered by the plan.