Configuration and details for the Clinical tab
The Clinical tab in the Patient 360 displays clinical
information such as vitals, lab results, medications, and allergies that are associated
with the patient record. You can manage the records by using the buttons and tools
provided. The Clinical tab uses data that comes in from various
sources (FHIR, EMR, EHR, patient reporting, assessments, and care manager entry). The
system displays the readings that are captured for the patient based on FHIR data in
Pega Foundation for Healthcare. Vitals and lab results are mapped to LOINC codes, which
supports electronic exchange and gathering of clinical results. The
Clinical tab also displays the entry of medications and
allergies. Because look-up data pages do not support dynamic class referencing, you need to save the
D_LOINCUnits rule in the appropriate implementation-layer class
context so that the data page can fetch the implementation-layer specific data.
Otherwise, the look-up fails and the data page does not return any data. The following topics include details that are related to the Clinical tab: The Clinical tab displays the readings that might be retrieved
by the FHIR APIs. Vitals and lab results are mapped to LOINC codes, which support electronic
exchange of clinical observations. The data class is
PegaHC-Data-Observation. Because look-up data pages do not support dynamic class referencing, you need to save the
D_GetObservationObject rule in the appropriate
implementation-layer class context so that the data page can fetch the
implementation-layer specific data. Otherwise, the look-up fails and the data page does
not return any data. No parameters No
parameters Parameters are MemberID: .pyCustomer, CodeType:
pyWorkPage.ObservationFilterOption, and Name:
pyWorkPage.SearchObservation No
parameters Parameter
is LOINCNum: SelectedObservation.LOINC_NUM No
parameters You can view trend charts of the lab results captured over time by clicking the specific
lab result in the listing at the left. A trend chart displays on the right side with the
details that are related to the specific lab result that might have been captured
manually or through an assessment. The following table shows the key rules to fetch and display observations for vitals and
lab results. For example, you might want to create a data page to get ICD-10 codes. No parameters No parameters Parameters are
MemberID: pyWorkPage.pyCustomer and LoincNum: .Code Parameter is ID:
Primary.pxResults(<CURRENT>).ID No
parameters No
parameters No parameters Parameters are MemberID: pyWorkPage.pyCustomer and
LoincNum: SelectedObservation.LOINC_NUM No parameters No parameters No parameters No
parameters No parameters Parameter is IDPrefix:
"OBS-" No parameters Parameters are MemberID and
LoincNum No parameters Parameters are
MemberID and ObservationFilterOption The Medications section displays the existing medications list
that is available on the patient profile. The medications might have been captured manually,
through an assessment, or fetched by using an API. You can use the rules listed in this
section to provide another source for a list. Pega Care Management offers support for two medication types: You can update to the new medication model. In Dev Studio, click The toggle functionality is handled by the EnableMedicationUpgrade
dynamic system setting. By default, its value is set to true, which indicates that the
new medication model is being used. After you reset the value, the Upgrade
medication button is enabled. And once you select the Upgrade
medication button, then the all the old medications are converted to new
medications by the UpgradeMemberMedications utility in the backend.
Then only the new medication model is effective. You cannot revert to the old
medication model. Parameters are CodeType:
NULL and CodeSearch: NDC No parameters No parameters Parameters are MemberID
and .pyCustomer No parameters No parameters No parameters Parameter is Declare_CommonMedication Parameter is UnitsForMedicationDose Parameter is Frequency Parameter is
MemberID No
parameters No parameters Parameter is IDPrefix:
.LISTING_PREFIX Parameter is Event:
Medications Update Parameters are CustomerID,
pgMedListPageName, and .Active Parameters are
CustomerID and .Active The Conditions section displays the health status or the
condition of the patient with its severity and the recorded date. You can filter and sort
conditions based on the condition code, description, clinical and verification status. The
data class is PegaHC-Data-ClinicalCondition. The data model for
clinical conditions is maintained through this class. fieldValue: ClinicalStatus / VerificationStatus /
ConditionCat and ClassName:
PegaHC-Data-ClinicalCondition No parameters No parameters Parameter is
MemberID No parameters No parameters Parameter is
IDPrefix No parameters In addition clinical information such as vitals, lab results, and medications, the
Clinical tab displays allergies information that is associated
with the patient record. Parameter is
MemberID No parameters No parameters Parameter is IDPrefix:
"ALLERGY-" No parameters No
parametersClinical vitals and laboratory observations and trends
Rules for displaying observation
Rule name Rule type Purpose SetDefaultObservationTrend Activity Defers to the load wrapper activity for setting the default
observation details. ClearSearchObservation Data transform Clears observation values and sets observation values. D_GetObservationCodes Data page Fetches observation codes based on member ID, code type, and
observation name. SetSelectedObservation Data transform Maps selected observation details on a temporary page. D_GetDefaultUnitForLoincCode Data page Fetches units for LOINC codes based on the LOINC number. ObservationHasComponents Decision table Checks whether the selected LOINC code has components. Trends for vitals and labs
Rule name Rule type Purpose ObservationMetrics Report definition Fetches all readings (without multiple components) for each
observation based on the Member ID, LOINC number, and only when fewer
than 30 days. D_ObservationMetricsWithComponents Data page Fetches all readings (with multiple components, for example, blood
pressure with systolic and diastolic component values for each reading)
for each observation based on the Member ID, LOINC number, and only when
fewer than 30 days. GetComponents Data transform Fetches the component of an observation. A component is used for any
supporting result that cannot reasonably be interpreted and used outside
the scope of the Observation of which it is a component. Components
should only be used when there is only one method, one observation, one
performer, one device, and one time. For example, systolic and diastolic
blood pressure are represented as a single observation. D_GetObservationObject Data page Fetches the observation details. PreAddObservation Data transform Pre-action rule to add a new reading under
Chart and set the properties of the selected
LOINC code to capture the observation record. ObservationHasComponents Decision table Checks whether the selected LOINC code has components. SaveObservationInstance Activity Saves a new or updated reading. D_ObservationsByLoincNum Data page Gets the observations for a LOINC code - list source under
Chart. Key rules to display trend charts for vital signs and lab results
Rule name Rule type Purpose ClearObservationRecords Data transform Extension point for the pre-action rule while adding a new reading.
Clears the Observations list and adds one empty
row to the grid. SaveObservationInstance Activity Saves a new or updated reading instance. ObservationUnitConversion Data transform Converts the supporting units to the default unit for the clinical
observations. RangePresent Decision table Checks if the range is maintained for the selected LOINC code. RangeEvaluation Activity Evaluates whether the lab result is out-of-range, based on the code,
gender, age, and test value. GenerateDataID Activity Generates a unique ID for an instance SetComponentProperties Data transform Sets the LOINC codes for the components for the blood pressure vital.
D_RecentObservationsByCode Property - Prompt List Gets the observations for a LOINC code. ObservationFilterOption Property - Prompt List The drop-down source for the Observation list, that is Lab or
Vitals. D_SearchObservationCodes Data page The source for the LOINC code drop-down list. Medications
New medication model: Rules for source lists when adding new medications
Rule name Rule type Purpose D_DrugCodesSearchResults Data page The source for the drop-down list for new medication details such as
name, code, strength, dosage form, and route. Type Property - Prompt List The source for the Dose units drop-down
list. Timing Property - Prompt List The source for the Medication frequency
drop-down list. New medication model: Rules for adding, updating, deleting, and viewing
medications
Rule name Rule type Purpose MemberMedicationsByMemberID Report definition Fetches new medication data for a patient. ResetMemberMedication Data transform Resets patient medication data. SaveMemberNewMedication Activity Saves a new medication instance to the database (including added,
updated, and deleted medication records). SaveConversation Activity Saves new or updated medication details to the conversation
logs. Old medication model: Rules for source lists when adding new medications
Rule name Rule type Purpose Declare_CommonMedication Data page Source for the Old medication drop-down
list. UnitsForMedicationDose Property - Prompt List Source for the Dosage units drop-down
list. Frequency Property - Prompt List Source for the Medication frequency drop-down
list. Old medication model: Key rules for adding, updating, deleting, and viewing
medications
Rule name Rule type Purpose PrescriptionsByMemberID Report definition Fetches the old medication data for a patient. ClearMedicationsOnAdd Data transform Pre-action rule when adding a new medication. ActionSaveCurrentInstance Activity Saves the old medication instance to the database (including added,
updated, and deleted medication records). GenerateDataID Activity Generates a unique ID for an instance. AuditLogClinicalData Activity Wrapper rule for adding an audit log. getMedicationListForMember Activity Gets the patient's list of medications. MedicationsByMemberID Report definition Fetches the medication list for a patient. Conditions
Rules for displaying or adding clinical conditions
Rule name Rule type Purpose D_fetchFieldValues Data transform The source for the drop-down list based on the
parameters. Severity Property - Prompt List The source for the Condition severity
drop-down list. D_SnomedCodesList Data transform The source for the Condition code and
description drop-down list. Rules to add or update clinical conditions
Rule name Rule type Purpose ClinicalConditionByMember Report definition Fetches clinical conditions of the patient. PreClinicalCondition Data transform Extension point for the pre-action rule while adding a new clinical
condition. ActionSaveCurrentInstance Activity Saves the condition details. GenerateDataID Activity Generates a unique id for an instance. PopulateConditionDetails Activity Opens and fetches clinical condition details; used while updating a
condition record. Allergies
Key rules for allergy information
Rule name Rule type Purpose AllergyByMemberID Report definition Fetches the allergy details for a patient. RemoveAllergyPage Data transform Extension point for a pre-action rule while adding a new
allergy. ActionSaveCurrentInstance Activity Saves the allergy instance. GenerateDataID Activity Generates a unique ID for an instance. PopulateAllergyDetails Activity Opens and fetches allergy details. Used when updating an allergy
record. DeleteAllergyDetails Activity Acquires a lock and deletes an allergy instance.
Previous topic Configuration and details for the Care tab Next topic Configuration and details for the History tab