- 1 -

Migration Details

For Referential Monographs, Drug-Drug

Interactions, and Patient Education

Leaflets

- 2 -

Introduction

We at Lexicomp are constantly striving to include more Lexicomp-created content into our Lexi-Data product. We have recently

completed and released the addition of Lexi-Drugs Referential Monograph Content, Lexi-Interact Drug-Drug and Drug-Food

Interaction Content, and Lexi-Patient Education Leaflets. The purpose of this document is to help Lexi-Data customers understand

the steps needed to migrate to this new content. When adding this new content, we carefully considered how this would impact

our customers, and tried to minimize that impact as much as possible, while not sacrificing what we believe to be the quality and

value our customers have come to trust and expect from Lexicomp. If after reviewing this document you require further assistance,

please don’t hesitate to contact your Lexicomp Sales Representative directly or contact our Integration Support team at

integration.support@lexi.com and we’ll be glad to assist you in making the transition to this new content.

- 3 -

Contents

Referential Monograph Overview .......................................................................................................................................................... - 4 - Database Details ................................................................................................................................................................................. - 4 - API Details ........................................................................................................................................................................................... - 6 -

Drug-Drug/Drug-Food Interaction Overview.......................................................................................................................................... - 9 - Database Details ............................................................................................................................................................................... - 11 - API Details ......................................................................................................................................................................................... - 13 -

Patient Education Leaflet Overview ..................................................................................................................................................... - 14 - Database Details ............................................................................................................................................................................... - 14 - API Details ......................................................................................................................................................................................... - 14 -

Appendix ............................................................................................................................................................................................... - 15 - Table 1 – Referential Monograph API Method Changes .................................................................................................................. - 15 - Table 2 – Referential Monograph API Class Changes ....................................................................................................................... - 17 - Table 3 – Referential Monograph API Class Property Changes........................................................................................................ - 18 - Table 4 – Drug-Drug Interaction API Method Changes .................................................................................................................... - 20 - Table 5 – Drug-Drug Interaction API Class Changes ......................................................................................................................... - 21 - Table 6 – Patient Education Leaflet Types........................................................................................................................................ - 22 -

- 4 -

Referential Monograph Overview

Lexi-Data now contains Lexicomp Referential Content, specifically a sub-set of our most widely known and trusted Lexi-Drugs

database. Independently ranked as the #1 drug database, Lexi-Drugs contains content covering Adverse Reactions,

Contraindications, Dosing, Medication Safety Issues, Pharmacodynamics and Kinetics, and much more. Lexi-Drugs covers every

patient population, as well as the following clinical specialties: pharmacy, nursing, internal medicine, cardiology, oncology,

psychiatry, anesthesiology and dentistry. This new content resides in new tables within the Lexi-Data database, and is accessed via

new API methods. With the addition of this new content, we’ve revamped how we structure referential content within Lexi-Data.

Database Details

Previously, each “topic” of referential content lived in its own separate table (e.g., REF_LACTWARNING, REF_DOSING,

REF_GENERALWARNING, etc.). We felt that this structure was limiting, and forced our users to deal with multiple tables of differing

structures. With the new Lexicomp Referential Content, we’ve structured it in a more content-agnostic manner, treating all

referential content as “fields” of text. To make transitioning to this new structure easier, we’ve created what we call Lexi

Monographs. These are groupings of referential fields that match the topics previously segregated into separate tables, as well as

include some new topics, such as Dental and Usage information.

For example, to retrieve General Warning content for abacavir, the following query was previously used:

SELECT DRUG_ID, GENERAL_WARNING_ID, WARNING_MESSAGE_TEXT

FROM REF_GENERALWARNING

WHERE DRUG_ID = 'd04376'

And to retrieve Pharmacology content for abacavir,

SELECT DRUG_ID, PHARMACOLOGY_ID, PHARMACOLOGY_TEXT

FROM REF_PHARMACOLOGY

- 5 -

WHERE DRUG_ID = 'd04376'

Using the new structure, to retrieve the General Warning content for abacavir from the new Lexicomp referential content, the

following query would be used:

SELECT LM.MONOGRAPH_ID, LM.MONOGRAPH_DESCRIPTION, LMSG.DRUG_ID, LMSF.FIELD_ID,

LMFT.FIELD_TYPE_ID, LMFT.FIELD_TYPE_DESCRIPTION, LMS.SECTION_ID, LMS.SECTION_DESCRIPTION,

LMFT2.SEQUENCE_NUMBER, LMF.FIELD_CONTENT

FROM LEXI_MONO_SECTION_GENDRUG LMSG

INNER JOIN LEXI_MONO_SECTION LMS ON LMSG.SECTION_ID = LMS.SECTION_ID

INNER JOIN LEXI_MONO_SECTION_FIELD LMSF ON LMS.SECTION_ID = LMSF.SECTION_ID

INNER JOIN LEXI_MONO_FIELD LMF ON LMSF.FIELD_ID = LMF.FIELD_ID

INNER JOIN LEXI_MONO_FIELD_TYPE LMFT ON LMF.FIELD_TYPE_ID = LMFT.FIELD_TYPE_ID

INNER JOIN LEXI_MONOGRAPH_FIELD_TYPE LMFT2 ON LMFT2.FIELD_TYPE_ID = LMFT.FIELD_TYPE_ID

INNER JOIN LEXI_MONOGRAPH LM ON LMFT2.MONOGRAPH_ID = LM.MONOGRAPH_ID

WHERE LMSG.DRUG_ID = 'd04376'

AND LM.MONOGRAPH_ID = 3

ORDER BY LMFT2.SEQUENCE_NUMBER

You may notice that querying these new tables is more complex, but the benefit is any referential content can be accessed using the

same query, with only key identifiers needing to be changed (drug_id and monograph_id). In this example, to retrieve

Pharmacology content for abacavir, you would only need to change the MONOGRAPH_ID from 3 (General Warning) to 5

(Pharmacology). The list of available monograph groupings can be found in the LEXI_MONOGRAPH table.

- 6 -

API Details

To make all of this simpler, we highly recommend our customers make use of the Lexi-Data API when possible. We have created

“topic” specific API methods, similar to those previously available. Methods to retrieve References and Warning Labels will be

deprecated. Please refer to Table 1 in the Appendix for a full list of existing methods and their new counterparts.

Using the same General Warning/Pharmacology example from above:

Existing methods

List<GeneralWarningResult> result = GetGeneralWarningResults(‘d04376’);

List<PharmacologyResult> result = GetPharmacologyResults(‘d04376’);

New methods

LexicompRefMonograph result = GetLexicompGeneralWarningMonograph(‘d04376’);

LexicompRefMonograph result = GetLexicompPharmacologyMonograph(‘d04376’);

We have also created additional API methods to offer our customers additional flexibility:

• LexicompRefMonograph GetLexicompFullRefMonographByGenericDrug(string drugId) – This method returns all Lexicomp

referential content for a given drug, crossing all topics available in Lexi-Data

• LexicompRefMonograph GetLexicompRefMonographByURN(string URN) – The new Lexicomp referential content can

contain links to additional content, Chemotherapy Regimens, for example. These links are proprietary URNs. Implementers

should capture navigation events to these links, pass the given URN to this method, and display the resulting content.

• LexicompRefMonograph GetLexicompRefMonograph(string drugId, int monographId, int localDataSetID) – This method can

be used in place of the topic-specific named methods, by specifying the appropriate monographId.

As noted above, the new referential methods all return a common LexicompRefMonograph object. Again, our prior object structure

was inconsistent between referential topics. This new LexicompRefMonograph object is a close analog to the original Dosing object.

- 7 -

The LexicompRefMonograph object contains the following properties:

• DrugID – Generic Drug Identifier this Monograph refers to

• MonographDescription – Name of this Monograph, such as “Dosing Monograph”, “Side Effect Monograph”, or “Dental

Information Monograph”

• MonoFields – List of LexicompRefMonoField objects containing the actual referential content

• NOTE - This object also contains properties referring to our Localization support. Please refer to our Lexi-Data

Implementation Guide for further details regarding Localization.

In the previous implementation of referential content, citations/references were separated into their own objects/tables. At this

time, all citations/references are contained within a single LexicompRefMonoField

The LexicompRefMonoField object contains the following properties:

• DrugID – Same Generic Drug identifier as found in the parent LexicompRefMonograph object

• FieldID – Unique identifier for a specific field of referential content for a specific drug

• FieldContent – Text of referential content. NOTE: The FieldContent is HTML-tagged text. This text on occasion will include

URN links. The intention of these links is for the implementer to trap navigation events to these URN links, and pass their

target to the GetLexicompRefMonographByURN API method. This will return the LexicompRefMonograph referred to by

the URN target.

• FieldTypeID - Unique identifier for the type of field this object represents. See the LEXI_MONO_FIELD_TYPE for a list of all

available Field Types

• FieldTypeDescription – Name of the type of field this object represents, such as “Mechanism of Action”, “Dosing: Geriatric”,

or “Medication Safety Issues”

• SectionID/SectionDescription – These two fields represent the internal Lexicomp section this particular field appears in.

These fields are not intended to be displayed, but are available to provide to Integration Support if reporting a concern.

- 8 -

• SequenceNumber – The position this field should be displayed. NOTE: This SequenceNumber applies across the entire

collection of fields. Depending on which fields a particular LexicompRefMonograph contains, the SequenceNumber may not

be sequential beginning at 1, and may contain gaps. Fields should be ordered from smallest to largest SequenceNumber.

• NOTE - This object also contains properties referring to our Localization support. Please refer to our Lexi-Data

Implementation Guide for further details regarding Localization.

Both the LexicompRefMonograph and LexicompRefMonoField objects have a method called FormattedText. When called on a

LexicompRefMonoField object, you will get a string containing both the FieldTypeDescription (when applicable) and

FieldContent properties. When called on a LexicompRefMonograph object, you will get a string containing the

MonographDescription as well as FormattedString results for each LexicompRefMonoField associated with it.

- 9 -

Drug-Drug/Drug-Food Interaction Overview

Lexi-Data now contains Lexicomp Drug-Drug and Drug-Food Interaction Content, specifically a sub-set of our most widely known and

trusted Lexi-Interact database. This new content resides in new tables within the Lexi-Data database, and is accessed via new API

methods.

This interactions information is built in-house at Lexicomp by a team of clinicians and is designed to be as clinically relevant as

possible – which can help reduce alert fatigue for your users. This is especially clear in the new Risk filter which is now available for

interactions. Although Severity is still available as a standalone filter, the Risk filter is a multi-dimensional assessment of an

interaction that takes into account the severity of the interaction, the likelihood of its occurrence, the reliability of the literature

reporting the interaction, and other factors. Because of the unique nature of the Lexicomp Risk rating, many clinicians find it is

useful for quickly identifying the most relevant and meaningful interactions.

Here are all of the filter points that can be used to help tailor the alerts you display to your users, along with details for each value

available:

- Severity describes the potential outcome hazard of an interaction if it is not managed appropriately, but does not take into

account the likelihood of the interaction occurring.

o Major: Effects may result in death, hospitalization, permanent injury, or therapeutic failure.

o Moderate: Medical intervention needed to treat effects; effects do not meet criteria for Major.

o Minor: Effects would be considered tolerable in most cases – no need for medical intervention

- Reliability characterizes the volume and quality of the literature supporting an interaction.

o Excellent: Multiple clinical trials, or a clinical trial plus more than two case reports

o Good: Single clinical trial plus two or fewer case reports

o Fair: More than two case reports or less than two case reports plus other supporting data. Fair is also available in

three additional distinctions

� Fair: Reported in the prescribing information

� Fair: Existing data/reports are inconsistent

� Fair: Multiple reported cases, but no apparent mechanism or confirmatory studies

- 10 -

- Onset describes the magnitude of elapsed time from therapy initiation to manifestation of an adverse event

o Immediate: 0-12 hours

o Rapid: 12-72 hours

o Delayed: more than 72 hours

o Immediate (Sequence Important): 0-12 hours, dependant upon sequence of administration of interacting agents

o Rapid (Sequence Important): 12-72 hours, dependant upon sequence of administration of interacting agents

o Delayed (Sequence Important): more than 72 hours, dependant upon sequence of administration of interacting

agents

- Risk rating provides a rapid indicator of the level of urgency and appropriate action steps to preemptively manage or avoid

an interaction. The rating is assigned taking into account the outcome severity and reliability of supporting literature.

o A: No Known Interaction – Data have not demonstrated either pharmacodynamic or pharmacokinetic interactions

between the specified agents

o B: No Action Needed – Data demonstrate that the specified agents may interact with each other, but there is little to

no evidence of clinical concern resulting from their concomitant use.

o C: Monitor Therapy – Data demonstrate that the specified agents may interact with each other in a clinically

significant manner. The benefits of concomitant use of these two medications usually outweigh the risk. An

appropriate monitoring plan should be implemented to identify potential negative effects. Dosage adjustments of

one or both agents may be needed in a minority of patients.

o D: Consider Therapy Modification – Data demonstrate that the two medications may interact with each other in a

clinically significant manner. A patient-specific assessment must be conducted to determine whether the benefits of

concomitant therapy outweigh the risks. Specific actions must be taken in order to realize the benefits and/or

minimize the toxicity resulting from concomitant use of the agents. These actions may include aggressive monitoring,

empiric dosage changes, and/or choosing alternative agents.

o X: Avoid Combination – Data demonstrate that the specified agents may interact with each other in a clinically

significant manner. The risks associated with concomitant use of these agents usually outweigh the benefits. These

agents are generally considered contraindicated.

- 11 -

Database Details

The database structure for Lexi-Interact Drug-Drug content is similar to the existing Drug-Drug Interaction structure. This feature is

still driven off of a pair of Generic Drug ID’s associated with an Interaction ID. The content associated with a particular interaction is

much more robust, however.

As for Drug-Food Interaction content, we’ve migrated this out of the REF_* table structure to help with some confusion this may

have caused. Drug-Food Interaction content is now located in the INTERACT_DRUG_FOOD table.

For example, to retrieve Drug-Drug Interaction results between Warfarin and Aspirin, the following query was previously used:

SELECT DRUG1.DRUG_ID AS DRUGID1, DRUG2.DRUG_ID AS DRUGID2,

DIG.DRUG_INTERACTION_ID, DIG.INT_SEVERITY_ID,

DI.INTERACTION_DESCRIPTION, SEV.SEVERITY_DESCRIPTION,

LOCALSEV.INT_SEVERITY_ID AS LOCAL_INT_SEVERITY_ID, LOCALSEV.SEVERITY_DESCRIPTION AS

LOCAL_SEVERITY_DESCRIPTION,

DILOCAL.LOCAL_VALUE, DILOCAL.SUPPORT_URL, DILOCAL.LAST_REVISED, DILOCAL.LOCAL_DATASET_ID

FROM (((((DRUGINT_INTERACTION_GENDRUG DIG

INNER JOIN CORE_GENDRUG_INGREDIENT DRUG1 ON DIG.DRUG_ID_1 = DRUG1.INGREDIENT_DRUG_ID)

INNER JOIN CORE_GENDRUG_INGREDIENT DRUG2 ON DIG.DRUG_ID_2 = DRUG2.INGREDIENT_DRUG_ID)

INNER JOIN DRUGINT_SEVERITY SEV ON DIG.INT_SEVERITY_ID = SEV.INT_SEVERITY_ID)

INNER JOIN DRUGINT_INTERACTION DI ON DIG.DRUG_INTERACTION_ID = DI.DRUG_INTERACTION_ID)

LEFT JOIN DRUGINT_INTERACTION_LOCAL DILOCAL ON (DI.DRUG_INTERACTION_ID =

DILOCAL.DRUG_INTERACTION_ID AND DILOCAL.LOCAL_DATASET_ID = 0))

LEFT JOIN DRUGINT_SEVERITY LOCALSEV ON DILOCAL.INT_SEVERITY_ID = LOCALSEV.INT_SEVERITY_ID

WHERE DRUG1.DRUG_ID IN ('d00170', 'd00022') AND DRUG2.DRUG_ID IN ('d00170', 'd00022')

ORDER BY DIG.DRUG_INTERACTION_ID, DRUG1.DRUG_ID, DRUG2.DRUG_ID;

Using the new Lexi-Interact based structure to retrieve Drug-Drug Interaction results between the same pair of drugs, the following

query will be used:

- 12 -

SELECT DRUG1.DRUG_ID AS DRUGID1, DRUG2.DRUG_ID AS DRUGID2, IDP.INTERACTION_ID,

IDP.SEVERITY_ID, II.TITLE, II.RISK_ID, RISK.RISK,

II.SUMMARY, II.ONSET_ID, ONSET.ONSET, II.RELIABILITY_ID, REL.RELIABILITY, II.MANAGEMENT,

II.DISCUSSION, II.FOOTNOTES, II.DEPENDENCIES, II.ANALYSIS_FILTER,

IDP.SEVERITY_ID, SEV.SEVERITY, LOCALSEV.SEVERITY_ID AS LOCAL_SEVERITY_ID,

LOCALSEV.SEVERITY AS LOCAL_SEVERITY_DESCRIPTION, IIL.LOCAL_VALUE, IIL.SUPPORT_URL,

IIL.LAST_REVISED, IIL.LOCAL_DATASET_ID

FROM (((((INTERACT_DRUG_PAIRS IDP INNER JOIN CORE_GENDRUG_INGREDIENT DRUG1 ON

IDP.DRUG_ID_1 = DRUG1.INGREDIENT_DRUG_ID)

INNER JOIN CORE_GENDRUG_INGREDIENT DRUG2 ON IDP.DRUG_ID_2 = DRUG2.INGREDIENT_DRUG_ID)

INNER JOIN INTERACT_SEVERITY SEV ON IDP.SEVERITY_ID = SEV.SEVERITY_ID)

INNER JOIN INTERACT_INTERACTION II ON IDP.INTERACTION_ID = II.INTERACTION_ID)

LEFT JOIN INTERACT_ONSET ONSET ON ONSET.ONSET_ID = II.ONSET_ID

INNER JOIN INTERACT_RELIABILITY REL ON REL.RELIABILITY_ID = II.RELIABILITY_ID

INNER JOIN INTERACT_RISK RISK ON RISK.RISK_ID = II.RISK_ID

LEFT JOIN INTERACT_INTERACTION_LOCAL IIL ON (II.INTERACTION_ID = IIL.INTERACTION_ID AND

IIL.LOCAL_DATASET_ID = 0))

LEFT JOIN INTERACT_SEVERITY LOCALSEV ON IIL.SEVERITY_ID = LOCALSEV.SEVERITY_ID

WHERE DRUG1.DRUG_ID IN ('d00170', 'd00022') AND DRUG2.DRUG_ID IN ('d00170', 'd00022')

ORDER BY IDP.INTERACTION_ID, DRUG1.DRUG_ID, DRUG2.DRUG_ID;

One of the key benefits of the Lexi-Interact content is that it can help combat alert fatigue, due to additional data points on

interactions that can be used for filtering purposes. These include Risk, Reliability, and Onset. Note: While the Severity of the

interaction is still present, we recommend using the new Risk field as a key for filtering. Available values for Risk, Reliability, Onset,

as well as Severity are located in INTERACT_RISK, INTERACT_RELIABILITY, INTERACT_ONSET, and INTERACT_SEVERITY accordingly.

- 13 -

API Details

The API changes needed to switch to the new Lexi-Interact content are relatively minor. The main existing Drug-Drug and Drug-Food

Interaction API methods have new Lexicomp counterparts that have the same method signature. Methods to retrieve References

and Advice do not have new Lexicomp counterparts. Please refer to Table 4 in the Appendix for a full list of existing methods and

their new counterparts.

Existing properties within the DrugDrugInteractionResult and DrugFoodInteractionResult classes remain the same.

DrugDrugInteractionResult has a new property, InteractMonograph, which is a class containing the new content available from Lexi-

Interact. This InteractMonograph class will contain the new data points that should help alleviate some alert fatigue.

To help with migration, some Lexi-Interact content will be located both within the InteractMonograph class and in the

DrugDrugInteractionResult class as well. This will allow you to continue to refer to the properties you currently use today, such as

Severity and Interaction Description, while still having the option to explore the additional Lexi-Interact content within the

InteractMonograph class. Please refer to Table 5 in the Appendix for a full list of class properties.

Note: While the Severity of the interaction is still present, we recommend using the new Risk property in the InteractMonograph

property as a key for filtering.

- 14 -

Patient Education Leaflet Overview

Lexi-Data now contains Lexicomp Patient Education Leaflets, specifically a sub-set of our most widely known and trusted Lexi-Patient

Education database. One of the biggest benefits of the Lexi-Patient Education Leaflets is expanded coverage with English, Spanish

and French language support for both Adult and Pediatric age groups. Lexicomp’s patient education is currently used in over 1,600

hospitals worldwide, and is often considered the first choice among clinicians for patient-facing information – in part because of the

flexibility that users have in providing documents that fit specific patient needs. This new content is accessible using existing API

methods.

Database Details

The Lexi-Patient Education Leaflets are located within the same table structure as the current Leaflets. They have their own distinct

set of Type Identifiers. Please refer to Table 6 for a list of Type Identifiers and how existing leaflet types correlate to the new Lexi-

Patient Education Leaflets.

API Details

There are no signature changes to the existing GetMonographs method in order to access the Lexi-Patient Education content. The

only change that needs to be made is supplying the appropriate new Type ID.

For example, to retrieve the existing HTML Adult Spanish Leaflet, you would specify a Type ID of 22, and to retrieve the new Lexi-

Patient Education Leaflet you would specify a Type ID of 102. Please refer to Table 6 for a list of Type Identifiers and how existing

leaflet types correlate to the new Lexi-Patient Education Leaflets.

You will still get a MonographResult object which will contain a FileName property. This FileName will still be relative to the path

you install the Images and Leaflets to when you install Lexi-Data using the Lexi-Data Management Utility.

- 15 -

Appendix These tables were designed to be a reference to, and help highlight, the differences between existing API methods, classes,

properties, and types of data.

Table 1 – Referential Monograph API Method Changes

Existing API Methods New API Methods Description

GetDosing

GetDosingReferences

GetLexicompDosingMonograph Returns Dosing related referential content for a given Generic Drug

GetGeneralWarningResults

GetGeneralWarningResultReferences

GetLexicompGeneralWarningMonograph Returns General Warning related referential content for a given Generic Drug

GetLactationWarningResults

GetLactationWarningResultReferences

GetLexicompLactationMonograph Returns Lactation related referential content for a given Generic Drug

GetPregnancyWarningResults

GetPregnancyWarningResultReferences

GetLexicompPregnancyMonograph Returns Pregnancy related referential content for a given Generic Drug

GetPharmacologyResults

GetPharmacologyResultReferences

GetLexicompPharmacologyMonograph Returns Pharmacology related referential content for a given Generic Drug

GetSideEffectResults

GetSideEffectResultReferences

GetLexicompSideEffectMonograph Returns Side Effect related referential content for a given Generic Drug

GetGenericProductWarningLabels N/A Returns Warning Label content for a given Generic Product

GetPackagedProductWarningLabels N/A Returns Warning Label content for a given Packaged Product

N/A GetLexicompDentalMonograph Returns Dental related referential content for a given Generic Drug

N/A GetLexicompUsageMonograph Returns Usage related referential content for a given Generic Drug

N/A GetLexicompPregLacMonograph Returns Pregnancy related and Lactation related referential content for a given Generic Drug

N/A GetLexicompFullRefMonographByGenericDrug Returns all Lexicomp referential content for a given Generic Drug

- 16 -

N/A GetLexicompRefMonographByURN Returns referential content linked to by an URN within other referential content

N/A GetLexicompRefMonograph Returns referential content for a given Generic Drug and given Monograph ID

- 17 -

Table 2 – Referential Monograph API Class Changes

Existing API Classes New API Classes

Dosing

DosingInformation

Citation

LexicompRefMonograph

GeneralWarningResult

Citation

LexicompRefMonograph

LactationWarningResult

Citation

LexicompRefMonograph

PregnancyWarningResult

Citation

LexicompRefMonograph

PharmacologyResult

Citation

LexicompRefMonograph

SideEffectResult

Citation

LexicompRefMonograph

WarningLabel N/A

N/A LexicompRefMonoField

- 18 -

Table 3 – Referential Monograph API Class Property Changes

Existing Class Existing Property New Class New Property

Dosing DrugID LexicompRefMonograph DrugId

Dosing DosingData LexicompRefMonograph MonoFields

DosingInformation DrugID LexicompRefMonoField DrugId

DosingInformation SectionID N/A N/A

DosingInformation SequenceNumber N/A N/A

DosingInformation DosingText LexicompRefMonoField FieldContent

DosingInformation DisplayOrder LexicompRefMonoField SequenceNumber

DosingInformation SectionName N/A N/A

DosingInformation Condition N/A N/A

GeneralWarningResult GeneralWarningID LexicompRefMonoField FieldId

GeneralWarningResult WarningText LexicompRefMonoField FieldContent

GeneralWarningResult GenericDrugID LexicompRefMonograph DrugId

LactationWarningResult LactationWarningID LexicompRefMonoField FieldId

LactationWarningResult SpecificityLevel N/A N/A

LactationWarningResult MessageText LexicompRefMonoField FieldContent

LactationWarningResult SignificanceDescription N/A N/A

LactationWarningResult GenericDrugID LexicompRefMonograph DrugId

PregnancyWarningResult PregnancyWarningID LexicompRefMonoField FieldId

PregnancyWarningResult SpecificityLevel N/A N/A

PregnancyWarningResult MessageText LexicompRefMonoField FieldContent

PregnancyWarningResult SignificanceDescription N/A N/A

PregnancyWarningResult GenericDrugID LexicompRefMonograph DrugId

PharmacologyResult PharmacologyID LexicompRefMonoField FieldId

PharmacologyResult Text LexicompRefMonoField FieldContent

PharmacologyResult GenericDrugID LexicompRefMonograph DrugId

SideEffectResult SideEffectID LexicompRefMonoField FieldId

SideEffectResult SpecificityLevel N/A N/A

SideEffectResult SideEffectText LexicompRefMonoField FieldContent

SideEffectResult DisplayOrder N/A N/A

SideEffectResult SystemDescription N/A N/A

- 19 -

SideEffectResult GenericDrugID LexicompRefMonograph DrugId

Citation CitationID N/A N/A

Citation AuthorNames N/A N/A

Citation ReferenceTitle N/A N/A

Citation Pages N/A N/A

Citation VolumeIssue N/A N/A

Citation YearComplete N/A N/A

Citation JournalAbbreviation N/A N/A

WarningLabel EnglishShortText N/A N/A

WarningLabel EnglishFullText N/A N/A

WarningLabel SpanishShortText N/A N/A

WarningLabel SpanishFullText N/A N/A

- 20 -

Table 4 – Drug-Drug Interaction API Method Changes

Existing API Methods New API Methods Description

GetDrugDrugInteractionResult

GetDrugDrugInteractionResultReferences

GetDrugDrugInteractionResultAdvice

GetLexicompDrugDrugInteractionResult Return details for a given Drug-Drug Interaction ID

GetDrugFoodInteractionResult

GetDrugFoodInteractionResultReferences

GetDrugFoodInteractionResultAdvice

GetLexicompDrugFoodInteractionResut Return details for a given Drug-Food Interaction ID

GetDrugDrugInteractions GetLexicompDrugDrugInteractions Given a ScreeningContext, describing what a set of drugs, return any drug-drug interactions found between the given drugs

GetDrugFoodInteractions GetLexicompDrugFoodInteractions Given a ScreeningContext, describing what a set of drugs, return any drug-food interactions found for the given drugs

GetDrugDrugInteractionResults GetLexicompDrugDrugInteractionResults For a given drug, return a list of all drug-drug interactions

GetDrugFoodInteractionResults GetLexicompDrugFoodInteractionResults For a given drug, return a list of all drug-food interactions

- 21 -

Table 5 – Drug-Drug Interaction API Class Changes

Existing Class Existing Property New Class New Property

DrugDrugInteractionResult InteractionID DrugDrugInteractionResult InteractionID

DrugDrugInteractionResult InteractionDescription DrugDrugInteractionResult InteractionDescription

DrugDrugInteractionResult SeverityID DrugDrugInteractionResult SeverityID

DrugDrugInteractionResult SeverityDescription DrugDrugInteractionResult SeverityDescription

DrugDrugInteractionResult LocalDataSetID DrugDrugInteractionResult LocalDataSetID

DrugDrugInteractionResult LocalSeverityID DrugDrugInteractionResult LocalSeverityID

DrugDrugInteractionResult LocalSeverityDescription DrugDrugInteractionResult LocalSeverityDescription

DrugDrugInteractionResult LocalValue DrugDrugInteractionResult LocalValue

DrugDrugInteractionResult LocalSupportURL DrugDrugInteractionResult LocalSupportURL

DrugDrugInteractionResult LocalLastRevised DrugDrugInteractionResult LocalLastRevised

n/a n/a DrugDrugInteractionResult InteractMonograph

n/a n/a InteractMonograph Title

n/a n/a InteractMonograph RiskID

n/a n/a InteractMonograph Risk

n/a n/a InteractMonograph Summary

n/a n/a InteractMonograph SeverityID

n/a n/a InteractMonograph Severity

n/a n/a InteractMonograph OnsetID

n/a n/a InteractMonograph Onset

n/a n/a InteractMonograph ReliabilityID

n/a n/a InteractMonograph Reliability

n/a n/a InteractMonograph Management

n/a n/a InteractMonograph Discussion

n/a n/a InteractMonograph Footnotes

n/a n/a InteractMonograph Dependencies

- 22 -

Table 6 – Patient Education Leaflet Types

Existing ID Existing Patient Leaflet Types New ID New Lexi-Patient Education Leaflet Types

12 Drug Specific SDK HTML Leaflet (English) 100 Lexi-Patient Education Adult HTML Leaflet (English)

14 Drug Specific SDK RTF Leaflet (English) n/a n/a

21 Drug Specific HTML ICONS Leaflet (English) 100 Lexi-Patient Education Adult HTML Leaflet (English)

22 Drug Specific SDK HTML Leaflet (Spanish) 102 Lexi-Patient Education Adult HTML Leaflet (Spanish)

23 Drug Specific SDK RTF Leaflet (Spanish) n/a n/a

32 Drug Specific HTML ICONS Leaflet (Spanish) 102 Lexi-Patient Education Adult HTML Leaflet (Spanish)

67 Drug Specific XML Leaflet (English) 101 Lexi-Patient Education Adult XML Leaflet (English)

68 Drug Specific XML Leaflet (Spanish) 103 Lexi-Patient Education Adult XML Leaflet (Spanish)

n/a n/a 104 Lexi-Patient Education Adult HTML Leaflet (French)

n/a n/a 105 Lexi-Patient Education Adult XML Leaflet (French)

n/a n/a 200 Lexi-Patient Education Pediatric HTML Leaflet (English)

n/a n/a 201 Lexi-Patient Education Pediatric XML Leaflet (English)

n/a n/a 202 Lexi-Patient Education Pediatric HTML Leaflet (Spanish)

n/a n/a 203 Lexi-Patient Education Pediatric XML Leaflet (Spanish)

n/a n/a 204 Lexi-Patient Education Pediatric HTML Leaflet (French)

n/a n/a 204 Lexi-Patient Education Pediatric XML Leaflet (French)