Avatar CareFabric 2023 Monthly Release 2023.04.00 Acceptance Tests

Last updated
Save as PDF

Update 15 Summary \| Details Flowsheet - backdated date Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Flowsheet assessments-historical-document Scenario 1: Validate the Back Dated flowsheet assessments show correctly for dates mapped using CareFabric Assessment Mappings Specific Setup: A Client (Client A) must be active and have episodes. Steps Select "Client A" and navigate to the 'Flowsheet' tab. Click on the 'I&O' link. Sign 'I&O' for 'Yesterday's Date' and the 'Day before Yesterday's date. Navigate to the 'Yesterday's Date'. Validate the date is backdated and the system displays the backdated data correctly.	Topics • CareFabric Assessment Management • CareFabric Assessment Mapping
Update 40 Summary \| Details '274 - Provider Directory Definition' CareFabric Support Scenario 1: Verification of 'GetPDOrganizationResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. Scenario 2: Verification of 'ListPDOrganizationResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. Scenario 3: Verification of 'GetPDOrganizationResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. '274 - Provider Directory Definition' CareFabric Support Scenario 1: Verification of 'GetPDLocationResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. Scenario 2: Verification of 'ListPDLocationResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. Scenario 3: Verification of 'GetPDLocationResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. '274 - Provider Directory Definition' CareFabric Support Scenario 1: Verification of 'GetPDPractitionerResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. Scenario 2: Verification of 'ListPDPractitionerResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. Scenario 3: Verification of 'GetPDPractitionerRoleResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. Scenario 4: Verification of 'ListPDPractitionerRoleResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. Scenario 5: Verification of 'GetPDHealthcareServiceResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. Scenario 6: Verification of 'ListPDHealthcareServiceResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. Scenario 7: Verification of 'GetPDPractitionerResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. Scenario 8: Verification of 'GetPDPractitionerRoleResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. Scenario 9: Verification of 'GetPDHealthcareServiceResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. '274 - Provider Directory Definition' CareFabric Support Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: 274 - Provider Directory Definition CareFabric Monitor Dictionary Update (PM) Scenario 1: '274 - Provider Directory Definition' - Validation of 'PDOrganizationResourceCreated' / 'PDOrganizationResourceUpdated' SDK Event Steps Open Avatar Cal-PM '274 - Provider Directory Definition' form. Note - Acceptance testing may also be confirmed via 274 Provider Directory Definition information filed via the Avatar Cal-PM 'File Import' form Navigate to 'Group Definition' section of form. Select value for 'Plan Type' field, and select 'Add' or 'Edit' in 'Add or Edit Group' field. Enter 'Provider Group Name (2100CA-NM1-03)' value and select value for 'Active' field (or search/select existing record in 'Provider Group' field if 'Edit Group' selected). Enter/select values for all other 'Group Definition' fields as desired. Click 'File Group Details' button to save/file 274 Provider Directory Group Definition entry; ensure user is presented with filing confirmation dialog. Open Avatar Cal-PM 'CareFabric Monitor' form. Enter values for 'From Date' and 'Through Date' fields (using dates which include 274 Provider Directory Group Definition entry/edit). Enter/select values for any other CareFabric Monitor fields as desired. Click 'View Activity Log' button to display CareFabric Monitor report results. In CareFabric Monitor report results - ensure that 'PDOrganizationResourceCreated' Event Out Activity is present for all 'Add Group' entries filed via the Avatar Cal-PM '274 - Provider Directory Definition' form, with 'Entity ID' reflecting the Provider Group ID (i.e. 'ProviderGroup-1'). In CareFabric Monitor report results - ensure that 'PDOrganizationResourceUpdated' Event Out Activity is present for all 'Edit Group' entries filed via the Avatar Cal-PM '274 - Provider Directory Definition' form, with 'Entity ID' reflecting the Provider Group ID (i.e. 'ProviderGroup-1'). Using the 'Click To View Record' link, ensure that the 'PDOrganizationResourceCreated'/'PDOrganizationResourceUpdated' Event Out Activity includes the following information fields: 'organizationResourceID' System-assigned ID, format 'ProviderGroup-[ID]' 'typeCodes' Static value 'prvgrp' 'name' From 'Provider Group Name (2100CA-NM1-03)' field 'isActive' 'True'/'False' 'aliases' From 'Additional Provider Group Name (2100CA-N2-01)'/'Provider Group Doing Business As Name (2100CA-N2-02)' fields ''fhirIdentifiers - NPI' From 'Provider Group Identifier (2100CA-NM1-09)' field 'fhirProfiles' Static value 'http://hl7.org/fhir/us/davinci-pdex-...t-Organization' Scenario 2: '274 - Provider Directory Definition' - Validation of 'PDLocationResourceCreated' / 'PDLocationResourceUpdated' SDK Event Steps Open Avatar Cal-PM '274 - Provider Directory Definition' form. Note - Acceptance testing may also be confirmed via 274 Provider Directory Definition information filed via the Avatar Cal-PM 'File Import' form Navigate to 'Site Definition' section of form. Select value for 'Plan Type' field, and select 'Add' or 'Edit' in 'Add or Edit Site' field. Enter 'Site or Location of Service Name (2100DA-NM1-03)' value and select value for 'Provider Group' and 'Active' fields (or search/select existing record in 'Provider Site' field if 'Edit Site' selected). Enter/select values for all other 'Site Definition' fields as desired (including 'Site Work Schedule' and 'Foreign Languages Spoken At This Site' multiple-entry grids). Click 'File Site Details' button to save/file 274 Provider Directory Site Definition entry; ensure user is presented with filing confirmation dialog. Open Avatar Cal-PM 'CareFabric Monitor' form. Enter values for 'From Date' and 'Through Date' fields (using dates which include 274 Provider Directory Site Definition entry/edit). Enter/select values for any other CareFabric Monitor fields as desired. Click 'View Activity Log' button to display CareFabric Monitor report results. In CareFabric Monitor report results - ensure that 'PDLocationResourceCreated' Event Out Activity is present for all 'Add Site' entries filed via the Avatar Cal-PM '274 - Provider Directory Definition' form, with 'Entity ID' reflecting the Provider Site ID (i.e. 'ProviderSite-1'). In CareFabric Monitor report results - ensure that 'PDLocationResourceUpdated' Event Out Activity is present for all 'Edit Site' entries filed via the Avatar Cal-PM '274 - Provider Directory Definition' form, with 'Entity ID' reflecting the Provider Site ID (i.e. 'ProviderSite-1'). Using the 'Click To View Record' link, ensure that the 'PDLocationResourceCreated'/'PDLocationResourceUpdated' Event Out Activity includes the following information fields: 'locationResourceID' System-assigned ID, format 'ProviderSite-[ID]' 'managingOrganizationID' Associated 274 Provider Directory Group, format 'ProviderGroup-[ID]' 'statusCode' 'Active' or 'Inactive' 'description' From 'Site or Location of Service Name (2100DA-NM1-03)' field 'aliases' From 'Additional Site or Location Name (2100DA-N2-01)'/'Site or Location Doing Business As Name (2100DA-N2-02)' fields 'address' From 'Site or Location Address (2110DA-N3-01)'/Site or Location Address 2 (2110DA-N3-02)'/Site or Location City Name (2110DA-N4-01)'/Site or Location State Code (2110DA-N4-02)'/'Site or Location Zip Code (2110DA-N4-03)' fields 'phoneNumbers' From 'Communication Number - 1 (2100DA-PER-04)'/'Communication Number - 2 (2100DA-PER-06)'/'Communication Number - 3 (2100DA-PER-08)' /'Communication Number - 4 (2100DA-PER-04 2nd Iteration)' fields 'typeCodes' From 'Facility Type (2100DA-N2-01)' field, using Other Tabled Files '(274193) Fhir Location Role Type' Extended Dictionary Data Element 'hoursOfOperation' From 'Site Work Schedule (2100DA-WS)' multiple entry grid, using Other Tabled Files '(274194) Fhir Office Hours Code' Extended Dictionary Data Element 'fhirIdentifiers - NPI' From 'Site or Location Identifier (2100DA-NM1-09)' field 'fhirExtensions - characteristics' From 'Gender Restriction Code (2100DA-PDI-01)'/'Age Range Minimum (2100DA-PDI-02)'/'Age Range Maximum (2100DA-PDI-03)' fields 'fhirExtensions - acceptingPatients' From 'Patient Acceptance Indicator (2100DA-CRC-03)' field 'fhirExtensions - accessibility' From 'Site or Location Assistive Aid Indicator (2100DA-CRC-03)' field 'fhirProfiles' Static value 'http://hl7.org/fhir/us/davinci-pdex-...annet-Location' Scenario 3: 'Practitioner Enrollment' - Validation of 'PDPractitionerResourceCreated' / 'PDPractitionerResourceUpdated' SDK Event Specific Setup: Avatar Cal-PM Registry Setting 'Practitioner Enrollment - Fields to Include' may optionally be set to include/exclude Taxonomy Code (in 'Categories/Taxonomy' section) Steps Open Avatar Cal-PM 'Practitioner Enrollment' form. Search/select existing Practitioner/Staff for update, or click 'New Staff' button for new Practitioner Enrollment entry. Enter/update values for 'Name', 'Registration Date', 'Office Address...', 'Office Telephone...' and 'NPI Number' fields (and all other Practitioner Enrollment fields as desired/required). Navigate to 'Categories/Taxonomy' section of form. Enter/update Practitioner Categories entry/entries as required/desired (including value for 'Taxonomy Code' field where enabled). Click 'Submit' button to save/file Practitioner Enrollment record. Open Avatar Cal-PM '274 - Provider Directory Definition' form. Note - Acceptance testing may also be confirmed via 274 Provider Directory Definition information filed via the Avatar Cal-PM 'File Import' form Navigate to 'Provider Definition' section of form. Select value for 'Plan Type' field. Search/select Provider (Practitioner) for association to Site in 'Provider' field. Search/select 274 Site for Provider association/update in 'Associated Site' field. Select value for 'Active' field. Enter/select values for all other 'Provider Definition' fields as desired. Click 'File Provider Details' button to save/file 274 Provider Directory Provider Definition entry; ensure user is presented with filing confirmation dialog. Open Avatar Cal-PM 'CareFabric Monitor' form. Enter values for 'From Date' and 'Through Date' fields (using dates which include Practitioner Enrollment entry/edit). Enter/select values for any other CareFabric Monitor fields as desired. Click 'View Activity Log' button to display CareFabric Monitor report results. In CareFabric Monitor report results - ensure that 'PDPractitionerResourceCreated' Event Out Activity is present for all new Practitioner/Practitioner Enrollment entries filed via the Avatar Cal-PM 'Practitioner Enrollment' and/or '274 - Provider Directory Definition' forms, with 'Entity ID' reflecting the Practitioner/Provider (i.e. 'Practitioner-000001'). In CareFabric Monitor report results - ensure that 'PDPractitionerResourceUpdated' Event Out Activity is present for all Practitioner Enrollment entries updated via the Avatar Cal-PM 'Practitioner Enrollment' and/or '274 - Provider Directory Definition' forms, with 'Entity ID' reflecting the Practitioner/Provider (i.e. 'Practitioner-000001'). Using the 'Click To View Record' link, ensure that the 'PDPractitionerResourceCreated'/'PDPractitionerResourceUpdated' Event Out Activity includes the following information fields: 'practitionerResourceID' Practitioner/Staff ID, format 'Practitioner-[ID]' ' IsActive' 'True' where Practitioner Enrollment is active (Practitioner Termination not filed) 'names' ('first' and 'last') From Practitioner Enrollment 'Name' field 'phoneNumbers' From Practitioner Enrollment 'Office Telephone (1)' , 'Office Telephone (2)', 'Home Telephone', 'Cellular Telephone' and 'Beeper Number' fields 'addresses' From Practitioner Enrollment 'Office Address...' and 'Home Address...' fields 'qualifications' From Practitioner Enrollment 'Taxonomy Code' and 'Effective Date'/'End Date' fields 'communications' From '274 - Provider Directory Definition' form Provider/Site Association 'Language Code - 1 (2100EA-LUI-02)'/'Language Proficiency Indicator - 1 (2100EA-LUI-05)' through 'Language Code - 8 (2100EA-LUI-02)'/'Language Proficiency Indicator - 8 (2100EA-LUI-05)' fields, using Client '(274195) Fhir Language Code' and '(274196) Fhir Language Proficiency Code' Extended Dictionary Data Elements 'fhirIdentifiers - NPI' From Practitioner Enrollment 'NPI Number' field (or '274 - Provider Directory Definition' Provider/Site Association 'Provider Identifier (2100EA-NM1-09)' field, only where not defined in Practitioner Enrollment) 'fhirProfiles' Static value 'http://hl7.org/fhir/us/davinci-pdex-...t-Practitioner' Scenario 4: '274 - Provider Directory Definition' - Validation of 'PDPractitionerRoleResourceCreated' / 'PDPractitionerRoleResourceUpdated' SDK Event Specific Setup: One or more Practitioner record(s) for assignment to 274 Provider Site (via '274 - Provider Directory Definition' form) Steps Open Avatar Cal-PM '274 - Provider Directory Definition' form. Note - Acceptance testing may also be confirmed via 274 Provider Directory Definition information filed via the Avatar Cal-PM 'File Import' form Navigate to 'Provider Definition' section of form. Select value for 'Plan Type' field. Search/select Provider (Practitioner) for association to Site in 'Provider' field. Search/select 274 Site for Provider association/update in 'Associated Site' field. Select value for 'Active' field. Enter/select values for all other 'Provider Definition' fields as desired. Click 'File Provider Details' button to save/file 274 Provider Directory Provider Definition entry; ensure user is presented with filing confirmation dialog. Open Avatar Cal-PM 'CareFabric Monitor' form. Enter values for 'From Date' and 'Through Date' fields (using dates which include 274 Provider Directory Provider Definition entry/edit). Enter/select values for any other CareFabric Monitor fields as desired. Click 'View Activity Log' button to display CareFabric Monitor report results. In CareFabric Monitor report results - ensure that 'PDPractitionerRoleResourceCreated' Event Out Activity is present for all new Provider/Site Association entries filed via the Avatar Cal-PM '274 - Provider Directory Definition' form, with 'Entity ID' reflecting the Provider Role ID (i.e. 'PractitionerRole-1'). Note - 'PDHealthcareServiceResourceCreated'/'PDHealthcareServiceResourceUpdated' and 'PDPractitionerResourceCreated'/'PDPractitionerResourceUpdated' Event Out Activities will also be filed for 'Service Type (2100EA-N2-02)' Dictionary Codes and associated 'Practitioner Enrollment' records where Provider/Site Association entries are added (to ensure complete/latest data for associated records) In CareFabric Monitor report results - ensure that 'PDPractitionerRoleResourceUpdated' Event Out Activity is present for all updated Provider/Site Association entries filed via the Avatar Cal-PM '274 - Provider Directory Definition' form, with 'Entity ID' reflecting the Provider Role ID (i.e. 'PractitionerRole-1'). Note - 'PDHealthcareServiceResourceCreated'/'PDHealthcareServiceResourceUpdated' and 'PDPractitionerResourceCreated'/'PDPractitionerResourceUpdated' Event Out Activities will also be filed for 'Service Type (2100EA-N2-02)' Dictionary Codes and associated 'Practitioner Enrollment' records where Provider/Site Association entries are updated (to ensure complete/latest data for associated records) Using the 'Click To View Record' link, ensure that the 'PDPractitionerRoleResourceCreated'/'PDPractitionerRoleResourceUpdated' Event Out Activity includes the following information fields: 'practitionerRoleResourceID' System-assigned ID, format 'PractitionerRole-[ID]' 'locationIDs' Associated 274 Provider Directory Site, format 'ProviderSite-[ID]' 'organizationID' Associated 274 Provider Directory Group, format 'ProviderGroup-[ID]' 'providerID' Associated Practitioner ID, format 'Practitioner-[ID]' 'isActive' 'True'/'False' 'authorizedDateRange' From 'Affiliation Contract Effective Date (2100EA-DTP-03)'/'Affiliation Contract Expiration Date (2100EA-DTP-03)' fields 'specialtyCodes' From 'Provider Specialty Code - 1 (2120EA-LQ-02)' through 'Provider Specialty Code - 5 (2120EA-LQ-02)' fields 'healthcareServiceIDs' From 'Service Type (2100EA-N2-02)' field, using associated 'PDHealthcareServiceResource' ID, format 'ServiceType-[ID]' 'fhirProfiles' Static value 'http://hl7.org/fhir/us/davinci-pdex-...actitionerRole' Scenario 5: '274 - Provider Directory Definition' - Validation of 'PDHealthcareServiceResourceCreated' / 'PDHealthcareServiceResourceUpdated' SDK Event Specific Setup: One or more Dictionary Code(s) defined for 'Other Tabled Files' Indirect '(274224) Service Type (2100EA-N2-02)' Data Element/Dictionary, including values for the following Extended Dictionary Data Elements: '(274290) Fhir Healthcare Service Category' '(274291) Fhir Healthcare Service Type' '(274292) Fhir Appointment Required' '(274293) Fhir Delivery Methods and Modalities' One or more Practitioner record(s) for assignment to 274 Provider Site (via '274 - Provider Directory Definition' form) Steps Open Avatar Cal-PM 'Dictionary Update' form. Navigate to 'Input Dictionary Code(s)' section of form. Select 'Other Tables Files' file/indirect. Select Data Element/Dictionary '(274224) Service Type (2100EA-N2-02)'. Enter/select value for Dictionary Code/Value, and enter/select values for the following Extended Dictionary Data Elements: '(274290) Fhir Healthcare Service Category' '(274291) Fhir Healthcare Service Type' '(274292) Fhir Appointment Required' '(274293) Fhir Delivery Methods and Modalities' Click 'Apply Changes' button to save/file Dictionary Code entry; repeat as desired for additional '(274224) Service Type (2100EA-N2-02)' Dictionary Codes. Open Avatar Cal-PM '274 - Provider Directory Definition' form. Navigate to 'Provider Definition' section of form. Select value for 'Plan Type' field. Search/select Provider (Practitioner) for association to Site in 'Provider' field. Search/select 274 Site for Provider association/update in 'Associated Site' field. Select value for 'Active' field. Enter/select values for all other 'Provider Definition' fields as desired. Click 'File Provider Details' button to save/file 274 Provider Directory Provider Definition entry; ensure user is presented with filing confirmation dialog. Open Avatar Cal-PM 'CareFabric Monitor' form. Enter values for 'From Date' and 'Through Date' fields (using dates which include 274 Provider Directory Provider Definition entry/edit). Enter/select values for any other CareFabric Monitor fields as desired. Click 'View Activity Log' button to display CareFabric Monitor report results. In CareFabric Monitor report results - ensure that 'PDHealthcareServiceResourceCreated' Event Out Activity is present for all new 'Service Type (2100EA-N2-02)' Dictionary Codes filed via the Avatar Cal-PM 'Dictionary Update' form, with 'Entity ID' reflecting the Service Type ID (i.e. 'ServiceType-IC'). Note - 'PDHealthcareServiceResourceCreated' Event Out Activity will be filed on entry/update of Provider/Site Association entries via Avatar Cal-PM '274 - Provider Directory Definition' form (not directly upon addition of Service Type (2100EA-N2-02)' Dictionary Code in 'Dictionary Update' form) In CareFabric Monitor report results - ensure that 'PDHealthcareServiceResourceUpdated' Event Out Activity is present for all updated 'Service Type (2100EA-N2-02)' Dictionary Codes filed via the Avatar Cal-PM 'Dictionary Update' form, with 'Entity ID' reflecting the Service Type ID (i.e. 'ServiceType-IC'). Note - 'PDHealthcareServiceResourceUpdated Event Out Activity will be filed on entry/update of Provider/Site Association entries via Avatar Cal-PM '274 - Provider Directory Definition' form (not directly upon update of Service Type (2100EA-N2-02)' Dictionary Code in 'Dictionary Update' form) Using the 'Click To View Record' link, ensure that the 'PDHealthcareServiceResourceCreated'/'PDHealthcareServiceResourceUpdated' Event Out Activity includes the following information fields: 'healthcareServiceResourceID' 'Dictionary Code' value, format 'ServiceType-[Dictionary Code]' 'name' 'Dictionary Value' value 'isActive' 'True'/'False' 'categoryCodes' From Extended Dictionary Data Element '(274290) Fhir Healthcare Service Category' 'typeCodes' From Extended Dictionary Data Element '(274291) Fhir Healthcare Service Type' 'isAppointmentRequired' From Extended Dictionary Data Element '(274292) Fhir Appointment Required' 'fhirExtentions - type - delivery-method' From Extended Dictionary Data Element '(274293) Fhir Delivery Methods and Modalities' for selected value 'Physical' 'fhirExtentions - virtualModalities' From Extended Dictionary Data Element '(274293) Fhir Delivery Methods and Modalities' for all selected values other than 'Physical' 'fhirProfiles' Static value 'http://hl7.org/fhir/us/davinci-pdex-...lthcareService'	Topics • CareFabric • Practitioner
Update 56 Summary \| Details Added ability for users to Review an amended laboratory result in Medical Note. Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Launch OrderConnect Lab Order Results Medical Note Results Entry - Results Details - Select Result HomeviewClinician HomeView.myDay Here is what I found: Scenario 1: Avatar NX -Validate amended lab results display properly in the 'Lab Results' section of Medical Note and OE Console when the results are amended after Clinical and Client Reviews have been completed Specific Setup: Facility must have the ability to receive an electronic laboratory result. Facility must have the ability receive an amended electronic laboratory result. Facility must have a laboratory wiling to send a test rest and an amended result. User must have the ability to view results, clinically review results, and review results with the client. Steps Log into myAvatar. Navigate to the 'Medical Note' Validate the presence of an existing laboratory result. Expand the result item. Validate result items are correct. Click [Review] and complete the 'Clinical Review'. Check the 'Mark as Client Reviewed' checkbox. Click [Save]. Validate that the result now appears in the ' Reviewed Lab Results' section of the 'Medical Note'. Return to the myAvatar 'Home' screen. Have the laboratory send an updated/amended result. Navigate back to the 'Medical Note' Refresh the 'Medical Note'. Validate that the result now appears in the 'Results Pending Review' section of the 'Medical Note'. Expand the result item. Validate the the amended laboratory result fields are correct. Click [Review] and complete the 'Clinical Review'. Check the 'Mark as Client Reviewed' checkbox. Click [Save]. Validate that the result now appears in the ' Reviewed Lab Results' section of the 'Medical Note'.	Topics • Results • ListLaboratoryResult
Update 59 Summary \| Details Avatar CareFabric - support for other products and modules Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Vitals Entry CareFabric Monitor Scenario 1: Vitals Entry - Validate the 'ObservationResourceCreated', 'ObservationResourceUpdated', and 'ObservationResourceDeleted' SDK events Specific Setup: A client is enrolled in an existing episode (Client A). Steps Select "Client A" and access the 'Vitals Entry' form. Select "Add" in the 'Update Vital Sign' field. Enter the current date in the 'Date' field. Enter the current time in the 'Time' field. Enter the desired value in the 'Blood Pressure - Systolic' and 'Blood Pressure - Diastolic' fields. Select the desired value in the 'Position' field. Click [Submit] and close the form. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate an "ObservationResourceCreated" record is displayed for "Client A". Note: this record will be triggered for each individual vital sign that is created. Click [Click To View Record]. Validate the 'categoryCode' - 'code' field contains "vital_signs". Validate the 'clientID' - 'id' field contains the ID for "Client A". Validate the 'Diastolic Blood Pressure' and 'Systolic Blood Pressure' values are displayed as expected. Validate the 'effectiveDateRange' - 'fromDate' field contains the date/time entered in 'Vitals Entry'. Validate the 'issuedDate' field contains the date/time entered in 'Vitals Entry'. Validate the 'observationResourceID' - 'id' field contains a unique identifier such as "vital-signs\|\|18\|\|20231205131800166813,65956.521\|\|BloodPressure1". Validate the 'statusCode' - 'code' field contains "final". Validate the 'subject' field contains the ID for "Client A". Close the report and the form. Select "Client A" and access the 'Vitals Entry' form. Select "Edit" in the 'Update Vital Sign' field. Click [Select Vital Sign]. Select the vitals filed in the previous steps and click [OK]. Enter any new value in the 'Blood Pressure - Systolic' and 'Blood Pressure - Diastolic' fields. Click [Submit] and close the form. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate an "ObservationResourceUpdated" record is displayed for "Client A". Note: this record will be triggered for each individual vital sign that is updated. Validate the updated 'Diastolic Blood Pressure' and 'Systolic Blood Pressure' values are displayed as expected. Close the report and the form. Select "Client A" and access the 'Vitals Entry' form. Select "Delete" in the 'Update Vital Sign' field. Click [Select Vital Sign]. Select the vitals filed in the previous steps and click [OK]. Validate the previously filed vitals are displayed and fields are disabled. Click [Submit]. Validate a message is displayed stating: Are you sure you wish to delete this row? Click [Yes]. Validate a message is displayed stating: Deleted. Click [OK] and close the form. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate an "ObservationResourceDeleted" record is displayed for "Client A". Note: this record will be triggered for each individual vital sign that is deleted. Validate the 'statusCode' - 'code' field contains "cancelled". Close the report and the form. Repeat as needed for additional types of vital signs. Scenario 2: Smoking Status - Validate the 'ObservationResourceCreated' SDK event Specific Setup: A client is enrolled in an existing episode (Client A). Steps Select "Client A" and access the 'Update Client Data' form. Select the desired value in the 'Smoker' field. Enter the desired date in the 'Smoking Status Assessment Date' field. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate a "ObservationResourceCreated" message is displayed. Click [Click to View Record]. Validate the 'categoryCode' - 'code' field contains "social-history". Validate the 'clientID' - 'id' field contains the ID for "Client A". Validate the 'code' field contains "72166-2". Validate the 'code' - 'codeSystem' field contains "2.16.840.1.113883.6.1". Validate the 'code' - 'codeSystemName' field contains "LOINC". Validate the 'code' - 'displayName' field contains "Tobacco smoking status". Validate the 'effectiveDateRange' - 'fromDate' field contains the 'Smoking Status Assessment Date'. Validate the 'issuedDate' field contains the 'Smoking Status Assessment Date'. Validate the 'observationResourceID' - 'id' field contains a unique identifier such as "social-history\|\|18\|\|MPI66813.002\|\|SmokingStatus". Validate the 'statusCode' - 'code' field contains "final". Validate the 'subject' field contains the ID for "Client A". Validate the 'value' field contains the smoking status code filed in the previous steps. Close the report and the form. Scenario 3: Sexual Orientation - Validate the 'ObservationResourceCreated' SDK event Specific Setup: A client is enrolled in an existing episode (Client A). Steps Select "Client A" and access the 'Update Client Data' form. Select the desired value in the 'Sexual Orientation' field. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate a "ObservationResourceCreated" message is displayed. Click [Click to View Record]. Validate the 'categoryCode' - 'code' field contains "social-history". Validate the 'clientID' - 'id' field contains the ID for "Client A". Validate the 'code' field contains "76690-7". Validate the 'code' - 'codeSystem' field contains "2.16.840.1.113883.6.1". Validate the 'code' - 'codeSystemName' field contains "LOINC". Validate the 'code' - 'displayName' field contains "Sexual Orientation". Validate the 'effectiveDateRange' - 'fromDate' field contains the current date. Validate the 'issuedDate' field contains the current date. Validate the 'observationResourceID' - 'id' field contains a unique identifier such as "social-history\|\|18\|\|MPI66813.001\|\|SexualOrientation". Validate the 'statusCode' - 'code' field contains "final". Validate the 'subject' field contains the ID for "Client A". Validate the 'value' field contains the sexual orientation code filed in the previous steps. Close the report and the form.	Topics • Vitals • CareFabric Monitor • Update Client Data
Update 60 Summary \| Details Scheduling Calendar - TeleHealth appointment events Time Zone Offset Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: CareFabric Monitor Scenario 1: Schedule a TeleHealth appointment with a TeleHealth service code and validate the TeleHealthAppointmentCreated/Updated/Deleted SDK events Specific Setup: A service code must be defined as a "Telehealth Service" in the 'Service Codes' form. A client is enrolled in an existing episode and has a phone number and email filed (Client A). A user is defined in 'User Definition' that has the following: "TeleHealth" selected in the 'Netsmart Mobile App Access' field, "System Admin" selected in the 'Netsmart Mobile App User Role' field, an email filed in the 'Organizational Email Address' field, and an associated staff member that has hours for scheduling. Steps Access the 'Scheduling Calendar' form. Right click in the 'Appointment Grid' and click [Add Appointment]. Enter the TeleHealth Service Code in the 'Service Code' field. Enter "Client A" in the 'Client' field. Select a non-TeleHealth location in the 'Location' field. Click [Submit]. Validate the 'Appointment Grid' contains the new appointment. Click [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' field contains a "TeleHealthAppointmentCreated" record. Click [Click To View Record]. Validate the 'isReoccuringAppointment" contains "IsFalse". Validate the 'appointmentDateRange' - 'fromDate' field contains the appointment start date/time. Validate the 'appointmentDateRange' - 'toDate' field contains the appointment end date/time. Validate the 'participants' - 'email' field contains "Client A's" email. Validate the 'participantID' - 'id' field contains "Client A's" ID. Validate the 'participantName' field contains "Client A's" name in the format of LAST,FIRST. Validate the 'phoneNumber' field contains "Client A's" phone number. Validate the 'typeCode' - 'code' field contains "CLIENT". Validate the 'typeCode' - 'isActive' field contains "true". Validate the 'programCode' - 'code' field contains "Client A's" program code. Validate the 'programCode' - 'displayName' field contains "Client A's" program. Validate the 'programCode' - 'isActive' field contains "true". Validate the 'serviceCode' - 'code' field contains the TeleHealth service code used. Validate the 'serviceCode' - 'displayName' field contains the name of the TeleHealth service code used. Validate the 'serviceCode' - 'isActive' field contains "true". Validate the 'teleHealthAppointmentID' - 'id' field contains unique id for the appointment. Validate the 'teleHealthProviderIDs' - 'humanReadableValue' field contains the TeleHealth Provider ID. Validate the 'teleHealthProviderIDs' - 'id' field contains the email associated to the TeleHealth Provider. Close the report and the form. Access the 'Scheduling Calendar' form. Right click on the appointment for "Client A". Click [Details/Edit]. Enter any new value in the 'Duration' field. Click [Submit]. Validate the 'Appointment Grid' field contains the appointment for "Client A" with the updated duration. Click [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentUpdated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentUpdated" record. Click [Click To View Record]. Validate the 'isReoccuringAppointment" contains "IsFalse". Validate the 'appointmentDateRange' - 'fromDate' field reflects the updated appointment duration. Validate the 'appointmentDateRange' - 'toDate' field reflects the updated appointment duration. Close the report and the form. Access the 'Scheduling Calendar' form. Right click on the appointment for "Client A". Click [Delete] and [Yes]. Validate the 'Appointment Grid' no longer contains the appointment for "Client A". Click [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentDeleted" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentDeleted" record. Click [Click To View Record]. Validate the 'isReoccuringAppointment" contains "IsFalse". Validate the 'appointmentDateRange' field contains "null". Validate the 'participants' field contains "[ ]". Validate the 'programCode' field contains "null". Validate the 'serviceCode' field contains "null". Validate the 'teleHealthAppointmentID' - 'humanReadableValue' field contains "null". Validate the 'teleHealthAppointmentID' - 'id' field contains the unique id for the appointment. Validate the 'teleHealthProviderIDs' field contains "[ ]". Close the report and the form. Open the "Update Client Data" form for [Client A]. Select a time zone that doesn't respect Daylight Savings Time from the "Time Zone for Appointment Reminders" drop down. Submit the form to file the data. Open the "Scheduling Calendar". Add a new appointment for a telehealth service for [Client A]. The appointment should be a recurring appointment. The client should be set up for telehealth. Submit to file the appointment. Open the "Carefabric Monitor" form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentCreated" record for each recurrence of the appointment. . Click [Click To View Record]. Validate the 'toDate" property reflects the date/time of the event firing is not adjusted for Daylight Savings Time. Validate the 'participants" object contains "timeZoneCode" property. Validate the code is equal to the time zone offset value (e.g. -10:00). Validate the 'displayName is equal to the time zone value selected in "Update Client Data" form. Validate the 'frequency' property field contains the value entered in the "Recurrence Schedule" field of the "Add Appointment" function in "Scheduling Calendar". Validate the 'recurrenceInfo' field contains a 'SeriesID' property. Note the value of the 'id' property. . Open the "Update Client Data" form for [Client A].. Change the client's time zone to one that respects Daylight Savings Time. Open the "Scheduling Calendar". Add a new appointment for a telehealth service for [Client A]. The appointment should be a recurring appointment. The client should be set up for telehealth. Submit to file the appointment. Open the "Carefabric Monitor" form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentCreated" record for each recurrence of the appointment. . Click [Click To View Record]. Validate the 'toDate" property reflects the date/time of the event firing is adjusted by Daylight Savings Time. Validate the 'participants" object contains "timeZoneCode" property. Validate the code is equal to the time zone offset value (e.g. -10:00). Validate the 'displayName is equal to the time zone value selected in "Update Client Data" form. Validate the 'frequency' property field contains the value entered in the "Recurrence Schedule" field of the "Add Appointment" function in "Scheduling Calendar". Validate the 'recurrenceInfo' field contains a 'SeriesID' property. Note the value of the 'id' property. . Repeat all steps in 10-12 for all appointments in the series. Scenario 2: Schedule a TeleHealth appointment with a TeleHealth location and validate the TeleHealthAppointmentCreated/Updated/Deleted SDK events Specific Setup: The 'Enable Telehealth integration at location level' registry setting is set to "Y". A location must be defined as a "TeleHealth Location" in the 'Dictionary Update' form. A client is enrolled in an existing episode and has a phone number and email filed (Client A). A user is defined in 'User Definition' that has the following: "TeleHealth" selected in the 'Netsmart Mobile App Access' field, "System Admin" selected in the 'Netsmart Mobile App User Role' field, an email filed in the 'Organizational Email Address' field, and an associated staff member that has hours for scheduling. Steps Access the 'Scheduling Calendar' form. Right click in the 'Appointment Grid' and click [Add Appointment]. Enter a non-TeleHealth service code in the 'Service Code' field. Enter "Client A" in the 'Client' field. Select the TeleHealth Location in the 'Location' field. Click [Submit]. Validate the 'Appointment Grid' contains the new appointment. Click [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' field contains a "TeleHealthAppointmentCreated" record. Click [Click To View Record]. Validate the 'isReoccuringAppointment" contains "IsFalse". Validate the 'appointmentDateRange' - 'fromDate' field contains the appointment start date/time. Validate the 'appointmentDateRange' - 'toDate' field contains the appointment end date/time. Validate the 'participants' - 'email' field contains "Client A's" email. Validate the 'participantID' - 'id' field contains "Client A's" ID. Validate the 'participantName' field contains "Client A's" name in the format of LAST,FIRST. Validate the 'phoneNumber' field contains "Client A's" phone number. Validate the 'typeCode' - 'code' field contains "CLIENT". Validate the 'typeCode' - 'isActive' field contains "true". Validate the 'programCode' - 'code' field contains "Client A's" program code. Validate the 'programCode' - 'displayName' field contains "Client A's" program. Validate the 'programCode' - 'isActive' field contains "true". Validate the 'serviceCode' - 'code' field contains the service code used. Validate the 'serviceCode' - 'displayName' field contains the name of the service code used. Validate the 'serviceCode' - 'isActive' field contains "true". Validate the 'teleHealthAppointmentID' - 'id' field contains unique id for the appointment. Validate the 'teleHealthProviderIDs' - 'humanReadableValue' field contains the TeleHealth Provider ID. Validate the 'teleHealthProviderIDs' - 'id' field contains the email associated to the TeleHealth Provider. Close the report and the form. Access the 'Scheduling Calendar' form. Right click on the appointment for "Client A". Click [Details/Edit]. Enter any new value in the 'Duration' field. Click [Submit]. Validate the 'Appointment Grid' field contains the appointment for "Client A" with the updated duration. Click [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentUpdated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentUpdated" record. Click [Click To View Record]. Validate the 'isReoccuringAppointment" contains "Isfalse". Validate the 'appointmentDateRange' - 'fromDate' field reflects the updated appointment duration. Validate the 'appointmentDateRange' - 'toDate' field reflects the updated appointment duration. Close the report and the form. Access the 'Scheduling Calendar' form. Right click on the appointment for "Client A". Click [Delete] and [Yes]. Validate the 'Appointment Grid' no longer contains the appointment for "Client A". Click [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentDeleted" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentDeleted" record. Click [Click To View Record]. Validate the 'isReoccuringAppointment" contains "IsFalse". Validate the 'appointmentDateRange' field contains "null". Validate the 'participants' field contains "[ ]". Validate the 'programCode' field contains "null". Validate the 'serviceCode' field contains "null". Validate the 'teleHealthAppointmentID' - 'humanReadableValue' field contains "null". Validate the 'teleHealthAppointmentID' - 'id' field contains the unique id for the appointment. Validate the 'teleHealthProviderIDs' field contains "[ ]". Close the report and the form. Open the "Update Client Data" form for [Client A]. Select a time zone that doesn't respect Daylight Savings Time from the "Time Zone for Appointment Reminders" drop down. Submit the form to file the data. Open the "Scheduling Calendar". Add a new appointment for a telehealth service for [Client A]. The appointment should be a recurring appointment. The client should be set up for telehealth. Submit to file the appointment. Open the "Carefabric Monitor" form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentCreated" record for each recurrence of the appointment. . Click [Click To View Record]. Validate the 'toDate" property reflects the date/time of the event firing is not adjusted for Daylight Savings Time. Validate the 'participants" object contains "timeZoneCode" property. Validate the code is equal to the time zone offset value (e.g. -10:00). Validate the 'displayName is equal to the time zone value selected in "Update Client Data" form. Validate the 'frequency' property field contains the value entered in the "Recurrence Schedule" field of the "Add Appointment" function in "Scheduling Calendar". Validate the 'recurrenceInfo' field contains a 'SeriesID' property. Note the value of the 'id' property. . Open the "Update Client Data" form for [Client A]. Change the client's time zone to one that respects Daylight Savings Time. Open the "Scheduling Calendar". Add a new appointment for a telehealth service for [Client A]. The appointment should be a recurring appointment. The client should be set up for telehealth. Submit to file the appointment. Open the "Carefabric Monitor" form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentCreated" record for each recurrence of the appointment. . Click [Click To View Record]. Validate the 'toDate" property reflects the date/time of the event firing is adjusted by Daylight Savings Time. Validate the 'participants" object contains "timeZoneCode" property. Validate the code is equal to the time zone offset value (e.g. -10:00). Validate the 'displayName is equal to the time zone value selected in "Update Client Data" form. Validate the 'frequency' property field contains the value entered in the "Recurrence Schedule" field of the "Add Appointment" function in "Scheduling Calendar". Validate the 'recurrenceInfo' field contains a 'SeriesID' property. Note the value of the 'id' property. . Repeat all steps in 10-12 for all appointments in the series. Scheduling Calendar - Telehealth Appointment Recurrence information Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: CareFabric Monitor Scenario 1: Schedule a TeleHealth appointment with a TeleHealth service code and validate the TeleHealthAppointmentCreated/Updated/Deleted SDK events Specific Setup: A service code must be defined as a "Telehealth Service" in the 'Service Codes' form. A client is enrolled in an existing episode and has a phone number and email filed (Client A). A user is defined in 'User Definition' that has the following: "TeleHealth" selected in the 'Netsmart Mobile App Access' field, "System Admin" selected in the 'Netsmart Mobile App User Role' field, an email filed in the 'Organizational Email Address' field, and an associated staff member that has hours for scheduling. Steps Access the 'Scheduling Calendar' form. Right click in the 'Appointment Grid' and click [Add Appointment]. Enter the TeleHealth Service Code in the 'Service Code' field. Enter "Client A" in the 'Client' field. Select a non-TeleHealth location in the 'Location' field. Click [Submit]. Validate the 'Appointment Grid' contains the new appointment. Click [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' field contains a "TeleHealthAppointmentCreated" record. Click [Click To View Record]. Validate the 'isReoccuringAppointment" contains "IsFalse". Validate the 'appointmentDateRange' - 'fromDate' field contains the appointment start date/time. Validate the 'appointmentDateRange' - 'toDate' field contains the appointment end date/time. Validate the 'participants' - 'email' field contains "Client A's" email. Validate the 'participantID' - 'id' field contains "Client A's" ID. Validate the 'participantName' field contains "Client A's" name in the format of LAST,FIRST. Validate the 'phoneNumber' field contains "Client A's" phone number. Validate the 'typeCode' - 'code' field contains "CLIENT". Validate the 'typeCode' - 'isActive' field contains "true". Validate the 'programCode' - 'code' field contains "Client A's" program code. Validate the 'programCode' - 'displayName' field contains "Client A's" program. Validate the 'programCode' - 'isActive' field contains "true". Validate the 'serviceCode' - 'code' field contains the TeleHealth service code used. Validate the 'serviceCode' - 'displayName' field contains the name of the TeleHealth service code used. Validate the 'serviceCode' - 'isActive' field contains "true". Validate the 'teleHealthAppointmentID' - 'id' field contains unique id for the appointment. Validate the 'teleHealthProviderIDs' - 'humanReadableValue' field contains the TeleHealth Provider ID. Validate the 'teleHealthProviderIDs' - 'id' field contains the email associated to the TeleHealth Provider. Close the report and the form. Access the 'Scheduling Calendar' form. Right click on the appointment for "Client A". Click [Details/Edit]. Enter any new value in the 'Duration' field. Click [Submit]. Validate the 'Appointment Grid' field contains the appointment for "Client A" with the updated duration. Click [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentUpdated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentUpdated" record. Click [Click To View Record]. Validate the 'isReoccuringAppointment" contains "IsFalse". Validate the 'appointmentDateRange' - 'fromDate' field reflects the updated appointment duration. Validate the 'appointmentDateRange' - 'toDate' field reflects the updated appointment duration. Close the report and the form. Access the 'Scheduling Calendar' form. Right click on the appointment for "Client A". Click [Delete] and [Yes]. Validate the 'Appointment Grid' no longer contains the appointment for "Client A". Click [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentDeleted" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentDeleted" record. Click [Click To View Record]. Validate the 'isReoccuringAppointment" contains "IsFalse". Validate the 'appointmentDateRange' field contains "null". Validate the 'participants' field contains "[ ]". Validate the 'programCode' field contains "null". Validate the 'serviceCode' field contains "null". Validate the 'teleHealthAppointmentID' - 'humanReadableValue' field contains "null". Validate the 'teleHealthAppointmentID' - 'id' field contains the unique id for the appointment. Validate the 'teleHealthProviderIDs' field contains "[ ]". Close the report and the form. Open the "Update Client Data" form for [Client A]. Select a time zone that doesn't respect Daylight Savings Time from the "Time Zone for Appointment Reminders" drop down. Submit the form to file the data. Open the "Scheduling Calendar". Add a new appointment for a telehealth service for [Client A]. The appointment should be a recurring appointment. The client should be set up for telehealth. Submit to file the appointment. Open the "Carefabric Monitor" form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentCreated" record for each recurrence of the appointment. . Click [Click To View Record]. Validate the 'toDate" property reflects the date/time of the event firing is not adjusted for Daylight Savings Time. Validate the 'participants" object contains "timeZoneCode" property. Validate the code is equal to the time zone offset value (e.g. -10:00). Validate the 'displayName is equal to the time zone value selected in "Update Client Data" form. Validate the 'frequency' property field contains the value entered in the "Recurrence Schedule" field of the "Add Appointment" function in "Scheduling Calendar". Validate the 'recurrenceInfo' field contains a 'SeriesID' property. Note the value of the 'id' property. . Open the "Update Client Data" form for [Client A].. Change the client's time zone to one that respects Daylight Savings Time. Open the "Scheduling Calendar". Add a new appointment for a telehealth service for [Client A]. The appointment should be a recurring appointment. The client should be set up for telehealth. Submit to file the appointment. Open the "Carefabric Monitor" form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentCreated" record for each recurrence of the appointment. . Click [Click To View Record]. Validate the 'toDate" property reflects the date/time of the event firing is adjusted by Daylight Savings Time. Validate the 'participants" object contains "timeZoneCode" property. Validate the code is equal to the time zone offset value (e.g. -10:00). Validate the 'displayName is equal to the time zone value selected in "Update Client Data" form. Validate the 'frequency' property field contains the value entered in the "Recurrence Schedule" field of the "Add Appointment" function in "Scheduling Calendar". Validate the 'recurrenceInfo' field contains a 'SeriesID' property. Note the value of the 'id' property. . Repeat all steps in 10-12 for all appointments in the series. Scenario 2: Schedule a TeleHealth appointment with a TeleHealth location and validate the TeleHealthAppointmentCreated/Updated/Deleted SDK events Specific Setup: The 'Enable Telehealth integration at location level' registry setting is set to "Y". A location must be defined as a "TeleHealth Location" in the 'Dictionary Update' form. A client is enrolled in an existing episode and has a phone number and email filed (Client A). A user is defined in 'User Definition' that has the following: "TeleHealth" selected in the 'Netsmart Mobile App Access' field, "System Admin" selected in the 'Netsmart Mobile App User Role' field, an email filed in the 'Organizational Email Address' field, and an associated staff member that has hours for scheduling. Steps Access the 'Scheduling Calendar' form. Right click in the 'Appointment Grid' and click [Add Appointment]. Enter a non-TeleHealth service code in the 'Service Code' field. Enter "Client A" in the 'Client' field. Select the TeleHealth Location in the 'Location' field. Click [Submit]. Validate the 'Appointment Grid' contains the new appointment. Click [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' field contains a "TeleHealthAppointmentCreated" record. Click [Click To View Record]. Validate the 'isReoccuringAppointment" contains "IsFalse". Validate the 'appointmentDateRange' - 'fromDate' field contains the appointment start date/time. Validate the 'appointmentDateRange' - 'toDate' field contains the appointment end date/time. Validate the 'participants' - 'email' field contains "Client A's" email. Validate the 'participantID' - 'id' field contains "Client A's" ID. Validate the 'participantName' field contains "Client A's" name in the format of LAST,FIRST. Validate the 'phoneNumber' field contains "Client A's" phone number. Validate the 'typeCode' - 'code' field contains "CLIENT". Validate the 'typeCode' - 'isActive' field contains "true". Validate the 'programCode' - 'code' field contains "Client A's" program code. Validate the 'programCode' - 'displayName' field contains "Client A's" program. Validate the 'programCode' - 'isActive' field contains "true". Validate the 'serviceCode' - 'code' field contains the service code used. Validate the 'serviceCode' - 'displayName' field contains the name of the service code used. Validate the 'serviceCode' - 'isActive' field contains "true". Validate the 'teleHealthAppointmentID' - 'id' field contains unique id for the appointment. Validate the 'teleHealthProviderIDs' - 'humanReadableValue' field contains the TeleHealth Provider ID. Validate the 'teleHealthProviderIDs' - 'id' field contains the email associated to the TeleHealth Provider. Close the report and the form. Access the 'Scheduling Calendar' form. Right click on the appointment for "Client A". Click [Details/Edit]. Enter any new value in the 'Duration' field. Click [Submit]. Validate the 'Appointment Grid' field contains the appointment for "Client A" with the updated duration. Click [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentUpdated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentUpdated" record. Click [Click To View Record]. Validate the 'isReoccuringAppointment" contains "Isfalse". Validate the 'appointmentDateRange' - 'fromDate' field reflects the updated appointment duration. Validate the 'appointmentDateRange' - 'toDate' field reflects the updated appointment duration. Close the report and the form. Access the 'Scheduling Calendar' form. Right click on the appointment for "Client A". Click [Delete] and [Yes]. Validate the 'Appointment Grid' no longer contains the appointment for "Client A". Click [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentDeleted" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentDeleted" record. Click [Click To View Record]. Validate the 'isReoccuringAppointment" contains "IsFalse". Validate the 'appointmentDateRange' field contains "null". Validate the 'participants' field contains "[ ]". Validate the 'programCode' field contains "null". Validate the 'serviceCode' field contains "null". Validate the 'teleHealthAppointmentID' - 'humanReadableValue' field contains "null". Validate the 'teleHealthAppointmentID' - 'id' field contains the unique id for the appointment. Validate the 'teleHealthProviderIDs' field contains "[ ]". Close the report and the form. Open the "Update Client Data" form for [Client A]. Select a time zone that doesn't respect Daylight Savings Time from the "Time Zone for Appointment Reminders" drop down. Submit the form to file the data. Open the "Scheduling Calendar". Add a new appointment for a telehealth service for [Client A]. The appointment should be a recurring appointment. The client should be set up for telehealth. Submit to file the appointment. Open the "Carefabric Monitor" form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentCreated" record for each recurrence of the appointment. . Click [Click To View Record]. Validate the 'toDate" property reflects the date/time of the event firing is not adjusted for Daylight Savings Time. Validate the 'participants" object contains "timeZoneCode" property. Validate the code is equal to the time zone offset value (e.g. -10:00). Validate the 'displayName is equal to the time zone value selected in "Update Client Data" form. Validate the 'frequency' property field contains the value entered in the "Recurrence Schedule" field of the "Add Appointment" function in "Scheduling Calendar". Validate the 'recurrenceInfo' field contains a 'SeriesID' property. Note the value of the 'id' property. . Open the "Update Client Data" form for [Client A]. Change the client's time zone to one that respects Daylight Savings Time. Open the "Scheduling Calendar". Add a new appointment for a telehealth service for [Client A]. The appointment should be a recurring appointment. The client should be set up for telehealth. Submit to file the appointment. Open the "Carefabric Monitor" form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentCreated" record for each recurrence of the appointment. . Click [Click To View Record]. Validate the 'toDate" property reflects the date/time of the event firing is adjusted by Daylight Savings Time. Validate the 'participants" object contains "timeZoneCode" property. Validate the code is equal to the time zone offset value (e.g. -10:00). Validate the 'displayName is equal to the time zone value selected in "Update Client Data" form. Validate the 'frequency' property field contains the value entered in the "Recurrence Schedule" field of the "Add Appointment" function in "Scheduling Calendar". Validate the 'recurrenceInfo' field contains a 'SeriesID' property. Note the value of the 'id' property. . Repeat all steps in 10-12 for all appointments in the series. Scheduling Calendar - Telehealth Appointment Recurrence information Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: CareFabric Monitor Scenario 1: Schedule a TeleHealth appointment with a TeleHealth service code and validate the TeleHealthAppointmentCreated/Updated/Deleted SDK events Specific Setup: A service code must be defined as a "Telehealth Service" in the 'Service Codes' form. A client is enrolled in an existing episode and has a phone number and email filed (Client A). A user is defined in 'User Definition' that has the following: "TeleHealth" selected in the 'Netsmart Mobile App Access' field, "System Admin" selected in the 'Netsmart Mobile App User Role' field, an email filed in the 'Organizational Email Address' field, and an associated staff member that has hours for scheduling. Steps Access the 'Scheduling Calendar' form. Right click in the 'Appointment Grid' and click [Add Appointment]. Enter the TeleHealth Service Code in the 'Service Code' field. Enter "Client A" in the 'Client' field. Select a non-TeleHealth location in the 'Location' field. Click [Submit]. Validate the 'Appointment Grid' contains the new appointment. Click [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' field contains a "TeleHealthAppointmentCreated" record. Click [Click To View Record]. Validate the 'isReoccuringAppointment" contains "IsFalse". Validate the 'appointmentDateRange' - 'fromDate' field contains the appointment start date/time. Validate the 'appointmentDateRange' - 'toDate' field contains the appointment end date/time. Validate the 'participants' - 'email' field contains "Client A's" email. Validate the 'participantID' - 'id' field contains "Client A's" ID. Validate the 'participantName' field contains "Client A's" name in the format of LAST,FIRST. Validate the 'phoneNumber' field contains "Client A's" phone number. Validate the 'typeCode' - 'code' field contains "CLIENT". Validate the 'typeCode' - 'isActive' field contains "true". Validate the 'programCode' - 'code' field contains "Client A's" program code. Validate the 'programCode' - 'displayName' field contains "Client A's" program. Validate the 'programCode' - 'isActive' field contains "true". Validate the 'serviceCode' - 'code' field contains the TeleHealth service code used. Validate the 'serviceCode' - 'displayName' field contains the name of the TeleHealth service code used. Validate the 'serviceCode' - 'isActive' field contains "true". Validate the 'teleHealthAppointmentID' - 'id' field contains unique id for the appointment. Validate the 'teleHealthProviderIDs' - 'humanReadableValue' field contains the TeleHealth Provider ID. Validate the 'teleHealthProviderIDs' - 'id' field contains the email associated to the TeleHealth Provider. Close the report and the form. Access the 'Scheduling Calendar' form. Right click on the appointment for "Client A". Click [Details/Edit]. Enter any new value in the 'Duration' field. Click [Submit]. Validate the 'Appointment Grid' field contains the appointment for "Client A" with the updated duration. Click [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentUpdated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentUpdated" record. Click [Click To View Record]. Validate the 'isReoccuringAppointment" contains "IsFalse". Validate the 'appointmentDateRange' - 'fromDate' field reflects the updated appointment duration. Validate the 'appointmentDateRange' - 'toDate' field reflects the updated appointment duration. Close the report and the form. Access the 'Scheduling Calendar' form. Right click on the appointment for "Client A". Click [Delete] and [Yes]. Validate the 'Appointment Grid' no longer contains the appointment for "Client A". Click [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentDeleted" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentDeleted" record. Click [Click To View Record]. Validate the 'isReoccuringAppointment" contains "IsFalse". Validate the 'appointmentDateRange' field contains "null". Validate the 'participants' field contains "[ ]". Validate the 'programCode' field contains "null". Validate the 'serviceCode' field contains "null". Validate the 'teleHealthAppointmentID' - 'humanReadableValue' field contains "null". Validate the 'teleHealthAppointmentID' - 'id' field contains the unique id for the appointment. Validate the 'teleHealthProviderIDs' field contains "[ ]". Close the report and the form. Open the "Update Client Data" form for [Client A]. Select a time zone that doesn't respect Daylight Savings Time from the "Time Zone for Appointment Reminders" drop down. Submit the form to file the data. Open the "Scheduling Calendar". Add a new appointment for a telehealth service for [Client A]. The appointment should be a recurring appointment. The client should be set up for telehealth. Submit to file the appointment. Open the "Carefabric Monitor" form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentCreated" record for each recurrence of the appointment. . Click [Click To View Record]. Validate the 'toDate" property reflects the date/time of the event firing is not adjusted for Daylight Savings Time. Validate the 'participants" object contains "timeZoneCode" property. Validate the code is equal to the time zone offset value (e.g. -10:00). Validate the 'displayName is equal to the time zone value selected in "Update Client Data" form. Validate the 'frequency' property field contains the value entered in the "Recurrence Schedule" field of the "Add Appointment" function in "Scheduling Calendar". Validate the 'recurrenceInfo' field contains a 'SeriesID' property. Note the value of the 'id' property. . Open the "Update Client Data" form for [Client A].. Change the client's time zone to one that respects Daylight Savings Time. Open the "Scheduling Calendar". Add a new appointment for a telehealth service for [Client A]. The appointment should be a recurring appointment. The client should be set up for telehealth. Submit to file the appointment. Open the "Carefabric Monitor" form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentCreated" record for each recurrence of the appointment. . Click [Click To View Record]. Validate the 'toDate" property reflects the date/time of the event firing is adjusted by Daylight Savings Time. Validate the 'participants" object contains "timeZoneCode" property. Validate the code is equal to the time zone offset value (e.g. -10:00). Validate the 'displayName is equal to the time zone value selected in "Update Client Data" form. Validate the 'frequency' property field contains the value entered in the "Recurrence Schedule" field of the "Add Appointment" function in "Scheduling Calendar". Validate the 'recurrenceInfo' field contains a 'SeriesID' property. Note the value of the 'id' property. . Repeat all steps in 10-12 for all appointments in the series. Scenario 2: Schedule a TeleHealth appointment with a TeleHealth location and validate the TeleHealthAppointmentCreated/Updated/Deleted SDK events Specific Setup: The 'Enable Telehealth integration at location level' registry setting is set to "Y". A location must be defined as a "TeleHealth Location" in the 'Dictionary Update' form. A client is enrolled in an existing episode and has a phone number and email filed (Client A). A user is defined in 'User Definition' that has the following: "TeleHealth" selected in the 'Netsmart Mobile App Access' field, "System Admin" selected in the 'Netsmart Mobile App User Role' field, an email filed in the 'Organizational Email Address' field, and an associated staff member that has hours for scheduling. Steps Access the 'Scheduling Calendar' form. Right click in the 'Appointment Grid' and click [Add Appointment]. Enter a non-TeleHealth service code in the 'Service Code' field. Enter "Client A" in the 'Client' field. Select the TeleHealth Location in the 'Location' field. Click [Submit]. Validate the 'Appointment Grid' contains the new appointment. Click [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' field contains a "TeleHealthAppointmentCreated" record. Click [Click To View Record]. Validate the 'isReoccuringAppointment" contains "IsFalse". Validate the 'appointmentDateRange' - 'fromDate' field contains the appointment start date/time. Validate the 'appointmentDateRange' - 'toDate' field contains the appointment end date/time. Validate the 'participants' - 'email' field contains "Client A's" email. Validate the 'participantID' - 'id' field contains "Client A's" ID. Validate the 'participantName' field contains "Client A's" name in the format of LAST,FIRST. Validate the 'phoneNumber' field contains "Client A's" phone number. Validate the 'typeCode' - 'code' field contains "CLIENT". Validate the 'typeCode' - 'isActive' field contains "true". Validate the 'programCode' - 'code' field contains "Client A's" program code. Validate the 'programCode' - 'displayName' field contains "Client A's" program. Validate the 'programCode' - 'isActive' field contains "true". Validate the 'serviceCode' - 'code' field contains the service code used. Validate the 'serviceCode' - 'displayName' field contains the name of the service code used. Validate the 'serviceCode' - 'isActive' field contains "true". Validate the 'teleHealthAppointmentID' - 'id' field contains unique id for the appointment. Validate the 'teleHealthProviderIDs' - 'humanReadableValue' field contains the TeleHealth Provider ID. Validate the 'teleHealthProviderIDs' - 'id' field contains the email associated to the TeleHealth Provider. Close the report and the form. Access the 'Scheduling Calendar' form. Right click on the appointment for "Client A". Click [Details/Edit]. Enter any new value in the 'Duration' field. Click [Submit]. Validate the 'Appointment Grid' field contains the appointment for "Client A" with the updated duration. Click [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentUpdated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentUpdated" record. Click [Click To View Record]. Validate the 'isReoccuringAppointment" contains "Isfalse". Validate the 'appointmentDateRange' - 'fromDate' field reflects the updated appointment duration. Validate the 'appointmentDateRange' - 'toDate' field reflects the updated appointment duration. Close the report and the form. Access the 'Scheduling Calendar' form. Right click on the appointment for "Client A". Click [Delete] and [Yes]. Validate the 'Appointment Grid' no longer contains the appointment for "Client A". Click [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentDeleted" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentDeleted" record. Click [Click To View Record]. Validate the 'isReoccuringAppointment" contains "IsFalse". Validate the 'appointmentDateRange' field contains "null". Validate the 'participants' field contains "[ ]". Validate the 'programCode' field contains "null". Validate the 'serviceCode' field contains "null". Validate the 'teleHealthAppointmentID' - 'humanReadableValue' field contains "null". Validate the 'teleHealthAppointmentID' - 'id' field contains the unique id for the appointment. Validate the 'teleHealthProviderIDs' field contains "[ ]". Close the report and the form. Open the "Update Client Data" form for [Client A]. Select a time zone that doesn't respect Daylight Savings Time from the "Time Zone for Appointment Reminders" drop down. Submit the form to file the data. Open the "Scheduling Calendar". Add a new appointment for a telehealth service for [Client A]. The appointment should be a recurring appointment. The client should be set up for telehealth. Submit to file the appointment. Open the "Carefabric Monitor" form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentCreated" record for each recurrence of the appointment. . Click [Click To View Record]. Validate the 'toDate" property reflects the date/time of the event firing is not adjusted for Daylight Savings Time. Validate the 'participants" object contains "timeZoneCode" property. Validate the code is equal to the time zone offset value (e.g. -10:00). Validate the 'displayName is equal to the time zone value selected in "Update Client Data" form. Validate the 'frequency' property field contains the value entered in the "Recurrence Schedule" field of the "Add Appointment" function in "Scheduling Calendar". Validate the 'recurrenceInfo' field contains a 'SeriesID' property. Note the value of the 'id' property. . Open the "Update Client Data" form for [Client A]. Change the client's time zone to one that respects Daylight Savings Time. Open the "Scheduling Calendar". Add a new appointment for a telehealth service for [Client A]. The appointment should be a recurring appointment. The client should be set up for telehealth. Submit to file the appointment. Open the "Carefabric Monitor" form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentCreated" record for each recurrence of the appointment. . Click [Click To View Record]. Validate the 'toDate" property reflects the date/time of the event firing is adjusted by Daylight Savings Time. Validate the 'participants" object contains "timeZoneCode" property. Validate the code is equal to the time zone offset value (e.g. -10:00). Validate the 'displayName is equal to the time zone value selected in "Update Client Data" form. Validate the 'frequency' property field contains the value entered in the "Recurrence Schedule" field of the "Add Appointment" function in "Scheduling Calendar". Validate the 'recurrenceInfo' field contains a 'SeriesID' property. Note the value of the 'id' property. . Repeat all steps in 10-12 for all appointments in the series.	Topics • Telehealth
Update 63 Summary \| Details Avatar CareFabric - uncoded allergies Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Allergies and Hypersensitivities Orders This Episode CareFabric Monitor HL7 Connection Monitor Medical Note BedBoard eMAR Launch OrderConnect Scenario 1: Uncoded Allergies Specific Setup: In order to utilize this functionality the following updates must be installed: Avatar CWS 2023 Update 84 Avatar OE 2023 Update 41 Avatar eMAR 2023 Update 22 Avatar CareFabric 2023 Update 63 Avatar HL7 2023 Update 8 RADplus Client Update 3392.007 A client must be admitted to an inpatient episode with no allergies existing. (Client A) "Client A" must be associated with a user role. (HomeviewCLINICIAN) Two users must exist. One that is associated with a user role (User A) and one who is not. (User B) The 'Avatar CWS->CWS Utilities->Set System Defaults->CWS Allergies->->Allow Access to Uncoded Allergies' registry setting must be set to "HomeviewCLINICIAN". Please log out of the application and log back in after completing the above configuration. Make note of the 'Unit' and 'Room' associated with "Client A". "User A" must be logged into the application. Steps Select "Client A" and access the 'Allergies and Hypersensitivities' form. Validate that no values are selected in the 'Known Medications Allergies' and 'Known Food Allergies' fields. Click [Update]. Click [New Row] and add a row for "BASIC CARE IBUPROFEN" with the following 'Comment' of "do not administer ibuprofen". Click [New Row] and add a row for "Uncoded Drug (Uncoded-Drug)" with the following 'Comment' of "Uncoded Drug- Prozatec". Click [New Row] and add a row for "Uncoded Environmental (Uncoded-Envr)" with the following 'Comment' of "Uncoded Environment - Thunderstorm". Click [New Row] and add a row for "Uncoded Food (Uncoded-Food)" with the following 'Comment' of "Uncoded Food - Peanut oil". Click [Save]. Validate the 'Known Medication Allergies' field is disabled and has "Yes" selected. Validate the 'Known Food Allergies' field is disabled and has "Yes" selected. Click [Submit]. Access the 'Allergies and Hypersensitivities' form. Validate the 'Client Information' banner contains "Allergies (4) 1) BASIC CARE IBUPROFEN - Confirmed 2) Uncoded Drug: Uncoded Drug- Prozatec - Confirmed 3) Uncoded Environmental: Uncoded Environment - Thunderstorm - Confirmed 4) Uncoded Food: Uncoded Food - Peanut oil - Confirmed". Click [Display] in the 'Allergies and Hypersensitivities' form and validate a 'Client Allergies/Hypersensitivities' report is displayed and includes all of the information entered in the 'Allergies and Hypersensitivities' form and close the report and the form. Open the Client Dashboard and validate the 'Client Information' banner contains "Allergies (4) 1) BASIC CARE IBUPROFEN - Confirmed 2) Uncoded Drug: Uncoded Drug- Prozatec - Confirmed 3) Uncoded Environmental: Uncoded Environment - Thunderstorm - Confirmed 4) Uncoded Food: Uncoded Food - Peanut oil - Confirmed" and click [Close]. Access "Med Note" and click "Allergies" on the 'Facesheet' tab. Validate the following are displayed: BASIC CARE IBUPROFEN Uncoded Drug: Uncoded Drug - Prozatec Uncoded Environmental: Uncoded Environment - Thunderstorm Uncoded Food: Uncoded Food - Peanut oil Click [Reviewed with Client]. Select the 'BedBoard' widget. Click the unit associated with "Client A". Select "Client A" under the appropriate room number. Validate that under 'Allergies" that the following is displayed: "BASIC CARE IBUPROFEN (Severity);Uncoded Drug (Severity);Uncoded Environmental (Severity);Uncoded Food (Severity)" and click [Cancel]. Access the Order Entry Console. Validate the 'Client Information' banner contains the following: "Allergies (4)↳Allergies Reviewed=Yes (Date Reviewed) ↳1) BASIC CARE IBUPROFEN - Status ↳2) Uncoded Drug: Uncoded Drug- Prozatec - Status ↳3) Uncoded Environmental: Uncoded Environment - Thunderstorm - Status ↳4) Uncoded Food: Uncoded Food - Peanut oil - Status". Search for and select "BASIC CARE IBUPROFEN" in the 'New Order' field. Validate a warning indicator and "At least one warning has been found with this order" appears under the 'New Order' field. Click the link and validate the following is displayed in the 'Interactions' dialog on the 'Interactions' tab: Uncoded Allergies Filed Warning: The following uncoded allergies are on file for TESTA,ALLERGY (Client ID: 1468): Uncoded Drug: Uncoded Drug- Prozatec, Uncoded Environmental: Uncoded Environment - Thunderstorm, Uncoded Food: Uncoded Food - Peanut oil. These allergies will be not be screened for drug interactions. Allergy Interaction(s) Reaction Severity Filter Level being used: # Drug: BASIC CARE IBUPROFEN 100 MG ORAL TABLET, CHEWABLE Allergen: BASIC CARE IBUPROFEN Description: BASIC CARE IBUPROFEN Screening Message: A history of hypersensitivity to the following substance has been noted for this patient: BASIC CARE IBUPROFEN. There was an experienced reaction of the reactions selected (Reaction Severity: severity selected). Click [Close]. Access the 'CareFabric Monitor' form. Select the current date in the 'From Date' and 'Through Date' fields. Search for and select "Client A" in the 'Client ID' field. Search for "allergycreated" in the 'Event/Action Search' field and select "Allergy/Created Out". Validate "Allergy/Created" is displayed and checked off in the 'Select Event/Actions' field. Click [View Activity Log]. Validate that 4 rows are selected Click the 1st 'Click To View Record' link and validate that "name":"BASIC CARE IBUPROFEN" is displayed and click the 'Main Report' tab. Click the 2nd 'Click To View Record' link and validate that "name":"Uncoded Drug: Uncoded Drug- Prozatec" is displayed and click the 'Main Report' tab. Click the 3rd 'Click To View Record' link and validate that "name":"Uncoded Environmental: Uncoded Environment - Thunderstorm" is displayed and click the 'Main Report' tab. Click the 4th 'Click To View Record' link and validate that "name":"Uncoded Food: Uncoded Food - Peanut oil" is displayed and click [Close Report] and close form. Access the 'Launch OrderConnect' form. Click [Launch OrderConnect Prescriptions]. Validate the 'Known Allergies' section contains: "BASIC CARE IBUPROFEN, Uncoded Drug: Uncoded Drug - Prozatec, Uncoded Environmental: Uncoded Environment - Thunderstorm, and Uncoded Food: Uncoded Food - Peanut oil" and click [Close Chart] and close form. Log out of the application and log back in as "User B". Select "Client A" and access the 'Allergies and Hypersensitivities' form. Click [Update] and [New Row]. In the 5th 'Allergen/Reactant' cell search for "Uncoded" and press Tab. Validate a message is displayed stating: "Allergen/Reactant Code Not Found. No Allergen/Reactant code or Allergen/Reactant code description matches 'UNCODED'." and click [OK] and [Close/Cancel]. Validate a message is displayed stating "You have made changes to the table. Are you sure you want to cancel and lose these changes?" and click [Yes] and close the form.	Topics • Allergies and Hypersensitivities
Update 64 Summary \| Details ProviderConnect Enterprise - 'Update ProviderConnect Enterprise Mapping' form Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Update ProviderConnect Enterprise Mapping Scenario 1: Update ProviderConnect Enterprise Mapping - Delete a client mapping Specific Setup: Please note: this functionality is available for the sole intent of allowing System Administrators to take corrective actions, when needed. Please do not make changes to client mappings that are valid and do NOT require correction. The 'Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y". The 'Managing Organization Definition' form must be configured for valid managing organizations. A client must be enrolled in an existing episode and be mapped to the defined managing organization in the 'ProviderConnect Enterprise Identifiers' section of the 'Admission' form (Client A). This client mapping must require corrective action. A practitioner must have a NPI that is mapped to a matching practitioner in the managing organization's system (Practitioner A). Steps Access the 'Update ProviderConnect Enterprise Mapping' form. Select "Client A" in the 'Local Client' field. Select the corresponding organization in the 'Managing Organization' field. Validate the 'External Client ID' field populates with the current external ID on file for "Client A". Click [Delete Mapping]. Validate a message is displayed stating: Are you sure you wish to continue? Deleting this mapping cannot be undone. Re-mapping this client at a later time will send new data records to the appropriate managing organization, which may result in duplicate episodes and records if that organization has not cleared its records. Click [OK]. Select "Client A" in the 'Local Client' field. Select the corresponding organization in the 'Managing Organization' field. Validate a message is displayed stating: No external mapping exists. Click [OK] and close the form. Access Crystal Reports or other SQL Reporting Tool. Create a report using the 'SYSTEM.pce_client_mapping' SQL table. Validate a row for the deleted mapping for "Client A" is not displayed. Close the report. Scenario 2: Update ProviderConnect Enterprise Mapping - Update an episode mapping Specific Setup: Please note: this functionality is available for the sole intent of allowing System Administrators to take corrective actions, when needed. Please do not make changes to episode mappings that are valid and do NOT require correction. The 'Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y". The 'Managing Organization Definition' form must be configured for valid managing organizations. A client must be enrolled in an existing episode and be mapped to the defined managing organization in the 'ProviderConnect Enterprise Identifiers' section of the 'Admission' form (Client A). This client's episode mapping must require corrective action. A practitioner must have a NPI that is mapped to a matching practitioner in the managing organization's system (Practitioner A). Steps Access the 'Update ProviderConnect Enterprise Mapping' form. Select the "Episode Mapping" section. Select "Client A" in the 'Local Client' field. Select the episode needing correction in the 'Local Episode' field. Select the corresponding organization in the 'Managing Organization' field. Validate the 'External Client ID' field populates with the external ID on file for "Client A". Validate the 'External Episode ID' field contains the current external episode ID for "Client A". Validate the 'External Movement ID' field contains the current movement ID for "Client A". Enter the corrected value in the 'External Episode ID' field. Enter the corrected value in the 'External Movement ID' field. Click [Update Mapping]. Validate a message is displayed stating: Are you sure you wish to continue? Updating this episode without changes in the appropriate managing organization may result in incorrect episodes and records. Click [OK]. Select "Client A" in the 'Local Client' field. Select the corresponding organization in the 'Managing Organization' field. Validate the 'External Episode ID' field populates with the corrected episode ID filed for "Client A". Validate the 'External Movement ID' field populates with the corrected movement ID for "Client A". Close the form. Access Crystal Reports or other SQL Reporting Tool. Create a report using the 'SYSTEM.pce_episode_mapping' SQL table. Navigate to the row for "Client A". Validate the 'external_EPISODE_NUMBER' field contains the corrected value for "Client A". Validate the 'external_movement_ID' field contains the corrected value for "Client A". Close the report. Scenario 3: Update ProviderConnect Enterprise Mapping - Delete an episode mapping Specific Setup: Please note: this functionality is available for the sole intent of allowing System Administrators to take corrective actions, when needed. Please do not make changes to episode mappings that are valid and do NOT require correction. The 'Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y". The 'Managing Organization Definition' form must be configured for valid managing organizations. A client must be enrolled in an existing episode and be mapped to the defined managing organization in the 'ProviderConnect Enterprise Identifiers' section of the 'Admission' form (Client A). This client's episode mapping must require corrective action. A practitioner must have a NPI that is mapped to a matching practitioner in the managing organization's system (Practitioner A). Steps Access the 'Update ProviderConnect Enterprise Mapping' form. Select the "Episode Mapping" section. Select "Client A" in the 'Local Client' field. Select the episode needing correction in the 'Local Episode' field. Select the corresponding organization in the 'Managing Organization' field. Validate the 'External Client ID' field populates with the external ID on file for "Client A". Validate the 'External Episode ID' field contains the current external episode ID for "Client A". Validate the 'External Movement ID' field contains the current movement ID for "Client A". Click [Delete Mapping]. Validate a message is displayed stating: Are you sure you wish to continue? Deleting this mapping cannot be undone. Re-mapping this episode at a later time will send new data records to the appropriate managing organization, which may result in duplicate episodes and records if that organization has not cleared its records. Click [OK]. Select "Client A" in the 'Local Client' field. Select the corresponding organization in the 'Managing Organization' field. Validate a message is displayed stating: No external mapping exists. Click [OK] and close the form. Access Crystal Reports or other SQL Reporting Tool. Create a report using the 'SYSTEM.pce_episode_mapping' SQL table. Validate a row for the deleted mapping for "Client A" is not displayed. Close the report. Scenario 4: Update ProviderConnect Enterprise Mapping - Update a record mapping Specific Setup: Please note: this functionality is available for the sole intent of allowing System Administrators to take corrective actions, when needed. Please do not make changes to record mappings that are valid and do NOT require correction. The 'Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y". The 'Managing Organization Definition' form must be configured for valid managing organizations. A client must be enrolled in an existing episode and be mapped to the defined managing organization in the 'ProviderConnect Enterprise Identifiers' section of the 'Admission' form (Client A). This client must have a record mapping that requires corrective action. A practitioner must have a NPI that is mapped to a matching practitioner in the managing organization's system (Practitioner A). Steps Access the 'Update ProviderConnect Enterprise Mapping' form. Select the "Record Mapping" section. Select the desired organization in the 'Managing Organization' field. Select "Client A" in the 'Local Client' field. Select the form requiring corrective action for "Client A" in the 'Form' field. Select the corresponding episode in the 'Local Episode' field (if applicable). Select the record requiring corrective action in the 'Local Record' field. Validate the 'External Client ID' field contains the external ID for "Client A". Validate the 'External Episode ID' field contains the external episode ID for "Client A" (if applicable). Validate the 'External Record ID' field contains the current record ID for "Client A". Enter the corrected value in the 'External Record ID' field. Click [Update Mapping]. Validate a message is displayed stating: Are you sure you wish to continue? Updating this record without changes in the appropriate managing organization may result in incorrect episodes and records. Click [OK]. Select the desired organization in the 'Managing Organization' field. Select "Client A" in the 'Local Client' field. Select the form requiring corrective action for "Client A" in the 'Form' field. Select the corresponding episode in the 'Local Episode' field (if applicable). Select the record corrected in the previous steps in the 'Local Record' field. Validate the 'External Record ID' field populates with the corrected record ID for "Client A". Close the form. Access Crystal Reports or other SQL Reporting Tool. Create a report using the 'SYSTEM.pce_record_mapping' SQL table. Navigate to the row for "Client A". Validate the 'external_RECORD_ID' field contains the corrected value for "Client A". Close the report. Scenario 5: Update ProviderConnect Enterprise Mapping - Delete a record mapping Specific Setup: Please note: this functionality is available for the sole intent of allowing System Administrators to take corrective actions, when needed. Please do not make changes to record mappings that are valid and do NOT require correction. The 'Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y". The 'Managing Organization Definition' form must be configured for valid managing organizations. A client must be enrolled in an existing episode and be mapped to the defined managing organization in the 'ProviderConnect Enterprise Identifiers' section of the 'Admission' form (Client A). This client must have a record mapping that requires corrective action. A practitioner must have a NPI that is mapped to a matching practitioner in the managing organization's system (Practitioner A). Steps Access the 'Update ProviderConnect Enterprise Mapping' form. Select the "Record Mapping" section. Select the desired organization in the 'Managing Organization' field. Select "Client A" in the 'Local Client' field. Select the form requiring corrective action for "Client A" in the 'Form' field. Select the corresponding episode in the 'Local Episode' field (if applicable). Select the record requiring corrective action in the 'Local Record' field. Validate the 'External Client ID' field contains the external ID for "Client A". Validate the 'External Episode ID' field contains the external episode ID for "Client A" (if applicable). Validate the 'External Record ID' field contains the record ID for "Client A". Click [Delete Mapping]. Validate a message is displayed stating: Are you wish to continue? Deleting this mapping cannot be undone. Re-mapping this episode at a later time will send new data records to the appropriate managing organization, which may result in duplicate episodes and records if that organization has not cleared its records. Click [OK] and close the form. Access Crystal Reports or other SQL Reporting tool. Create a report using the 'SYSTEM.pce_record_mapping' SQL table. Validate a row for the deleted mapping for "Client A" is not displayed. Close the report. Scenario 6: Update ProviderConnect Enterprise Mapping - Import/Export Mapping Specific Setup: Please note: this functionality is available for the sole intent of allowing System Administrators to take corrective actions, when needed. Please do not make changes to record mappings that are valid and do NOT require correction. The 'Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y". The 'Managing Organization Definition' form must be configured for valid managing organizations. Must have an invalid 'Managing Organization Data File' for import that does not contain valid client/episode/record mappings (File A). Must have a valid 'Managing Organization Data File' for import that contains valid client/episode/record mappings (File B). Steps Access the 'Update ProviderConnect Enterprise Mapping' form. Select the "Import/Export Mapping" section. Click [Upload Managing Organization Data File]. Search for and select "File A" for import. Validate a message is displayed stating: Errors existed in the uploaded file. Click [OK] and [Export Managing Organization Error File]. Navigate to the exported error file and validate the expected errors are displayed. Close the file. Click [Upload Managing Organization Data File]. Search for and select "File B" for import. Click [Export Certified Contracting Provider Mapping File]. Navigate to the exported 'Certified Contracting Provider Mapping File' and validate the imported data is displayed. Save the 'Certified Contracting Provider Mapping File'. Click [Upload Certified Contracting Provider Mapping File]. Navigate to the 'Certified Contracting Provider Mapping File' saved in the previous steps and select it for import. Validate a message is displayed stating: Mapping loaded successfully. Click [OK] and close the form. Access Crystal Reports or other SQL Reporting Tool. Create reports using the 'SYSTEM.pce_client_mapping', 'SYSTEM.pce_episode_mapping', and 'SYSTEM.pce_record_mapping' SQL tables. Validate each client, episode, and record mapping uploaded in the previous steps is displayed as expected. Close the reports. Scenario 7: Update ProviderConnect Enterprise Mapping - Update a client mapping Specific Setup: Please note: this functionality is available for the sole intent of allowing System Administrators to take corrective actions, when needed. Please do not make changes to client mappings that are valid and do NOT require correction. The 'Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y". The 'Managing Organization Definition' form must be configured for valid managing organizations. A client must be enrolled in an existing episode and be mapped to the defined managing organization in the 'ProviderConnect Enterprise Identifiers' section of the 'Admission' form (Client A). This client mapping must require corrective action. A practitioner must have a NPI that is mapped to a matching practitioner in the managing organization's system (Practitioner A). Steps Access the 'Update ProviderConnect Enterprise Mapping' form. Select "Client A" in the 'Local Client' field. Select the corresponding organization in the 'Managing Organization' field. Validate the 'External Client ID' field populates with the current external ID on file for "Client A". Enter the corrected value in the 'External Client ID' field. Click [Update Mapping]. Validate a message is displayed stating: Are you sure you wish to continue? Updating this client without changes in the appropriate managing organization may result in incorrect episodes and records. Click [OK]. Select "Client A" in the 'Local Client' field. Select the corresponding organization in the 'Managing Organization' field. Validate the 'External Client ID' field populates with the corrected external ID filed for "Client A". Close the form. Access Crystal Reports or other SQL Reporting Tool. Create a report using the 'SYSTEM.pce_client_mapping' SQL table. Navigate to the row for "Client A". Validate the 'external_PATID' field contains the corrected value for "Client A". Close the report.	Topics • ProviderConnect Enterprise
Update 69 Summary \| Details Avatar CareFabric - Support for CareManager Scenario 1: CareManager - Validate the 'PutProgressNote' action when document routing is enabled Specific Setup: myAvatar must be configured to integrate with CareManager. Please note: this must be done by a Netsmart Associate. A progress notes form must be configured for CareManager integration. Document routing is enabled on this progress notes form. A practitioner (Practitioner A) must exist in both myAvatar and CareManager that is associated to an Avatar user (User A). This user does not require a supervisor's approval for document routing. A client is enrolled in an existing episode in myAvatar and CareManager (Client A). Steps Log into CareManager. Search for and select "Client A". File a progress note for a "New Service", populating all required and desired fields. Select "Practitioner A" as the 'Practitioner'. Enter the desired value for the 'Duration'. Select "Final" as the 'Note Status'. Click [Save]. Log into myAvatar as "User A". Navigate to the "My To Do's" widget. Locate the To Do just routed and click [Approve Document]. Validate the document is displayed with the progress note data sent from CareManager. Click [Accept]. Enter the password for "User A" in the 'Verify Password' dialog and click [OK]. Validate the To-Do is no longer displayed. Select "Client A" and navigate to the 'Progress Notes' widget. Validate the 'Progress Notes' widget contains the finalized progress note submitted from CareManager. Validate all progress note data displays as expected. Scenario 2: CareManager - Validate the 'PutProgressNote' action when document routing is disabled Specific Setup: myAvatar must be configured to integrate with CareManager. Please note: this must be done by a Netsmart Associate. A progress notes form must be configured for CareManager integration. Document routing is disabled on this progress notes form. A practitioner (Practitioner A) must exist in both myAvatar and CareManager that is associated to an Avatar user (User A). A client is enrolled in an existing episode in myAvatar and CareManager (Client A). Steps Log into CareManager. Search for and select "Client A". File a progress note for a "New Service", populating all required and desired fields. Select "Practitioner A" as the 'Practitioner'. Enter the desired value for the 'Duration'. Select "Final" as the 'Note Status'. Click [Save]. Log into myAvatar as "User A". Select "Client A" and navigate to the 'Progress Notes' widget. Validate the 'Progress Notes' widget contains the finalized progress note submitted from CareManager. Validate all progress note data displays as expected. Avatar CareFabric - 'PutProgressNote' SDK action Scenario 1: Bells Notes Integration - Validate document routing for progress notes when a supervisor is not required Specific Setup: myAvatar must be configured to integrate with Bells Notes. Please note: this must be done by a Netsmart Associate. The 'Progress Notes (Group and Individual)' form is configured and selected in the "Bells Notes" section of the 'CarePOV Management' form. Please note: this must be done by a Netsmart Associate. The 'Progress Notes (Group and Individual)' form must have: Document routing enabled. The 'Clear Selected Client After Filing' registry setting set to "Y". A user is defined with the following (User A): Access to Bells Notes Associated practitioner (Practitioner A) Does not require a supervisor's approval for document routing Access to the 'My To Do's' widget on the HomeView. A client is enrolled in "Program A" (Client A). Steps Access the 'Scheduling Calendar' form. Right click in the 'Appointment Grid' and click [Add Appointment]. Enter the desired service code in the 'Service Code' field. Enter "Client A" in the 'Client' field. Select the desired value in the 'Episode Number' field. Validate "Program A" is selected in the 'Program' field. Select the desired value in the 'Location' field. Validate the 'Practitioner' field is populated with "Practitioner A" Fill out all required fields. Click [Submit]. Validate successful submission. Validate the scheduled appointment is added to the 'Scheduling Calendar' form. Log into Bells Notes as "User A". Click the 'Agenda' section and verify the existence of the scheduled appointment from the 'Scheduling Calendar' form in myAvatar. Select the scheduled appointment and validate the summary of the scheduled appointment is displayed on the right side of the Bells Notes. Click [Start Note] and verify the existence of the 'Session Information' window. Fill out all required fields and select the desired note type. Validate user is able to start a note successfully. Verify the existence of "Client A" in the client header when note is started. Fill out all required fields. Click [Sign Note]. Validate the Sign Note' dialog is displayed. Enter the pin for "User A" in the 'Pin' field and click [Sign]. Validate a message is displayed stating: Note Signed Successfully. Log into myAvatar as "UserA". Navigate to the "My To Do's" widget. Locate the To Do just routed and click [Approve Document]. Validate the document is displayed with the progress note data and an electronic signature at the bottom for "Practitioner A" as Author. Click [Accept]. Enter the password for "User A" in the 'Verify Password' dialog and click [OK]. Validate the To-Do is no longer displayed. Select "Client A" and access the 'Progress Notes' widget. Validate the 'Progress Notes' widget contains the finalized progress note submitted from Bells Notes. Validate all progress note data displays as expected.	Topics • Progress Notes
Update 70 Summary \| Details Avatar CareFabric - Support for CareManager Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: CareFabric Monitor Scenario 1: Validate the 'GetClient' SDK action Steps Internal testing only.	Topics • CareFabric
Update 73 Summary \| Details Future Functionality Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Real Time Inquiry (270) Request Eligibility Inquiry (270/271) Real-Time Setup Guarantors/Payors Financial Eligibility Eligibility Inquiry and Response (270/271) Report CareFabric Monitor Scenario 1: Enable RevConnect = YA - Real Time Inquiry (270) Request Specific Setup: Netsmart Client Alignment Associate has been contacted to enable 'RevConnect'. Netsmart Avatar support has completed the following: Enabled the 'Enable RevConnect' registry setting has been updated to contain 'YA'. Completed & submitted the 'RevConnect Configuration' form. 'System Generated Email Settings' has been used to add the tester’s email to enable notification verification. Registry Setting: The 'Enable 270/271 Transaction Sets' registry setting is set to 'Y'. Guarantors/Payors: An existing guarantor is identified and has a value of 'Yes' in 'Support 270/271 Transaction Sets' of the '270 / 271 / 834' sections. Note all selections on the form. Admission: A client is admitted to a program, or an existing client is identified. Note client id/name, admission date/program. Financial Eligibility: The above guarantor is assigned to client. Based on the setup in the '270 / 271 / 834' section of 'Guarantors/Payors', the client either has one, or any combination of the following: services, appointments, or an eligibility request in financial eligibility. Eligibility Inquiry (270/271) Real-Time Setup: The 'Access Point Type' contains a 'RevConnect' option only when the 'Enable RevConnect' registry setting has a value of 'YA'. The 'RevConnect Account Key' field is added to the form when the 'Enable RevConnect' registry setting has a value of 'YA'. Steps Open 'Real Time Inquiry (270) Request'. Create a request for the client. Close the form. Open 'Eligibility Inquiry And Response (270/271) Report'. Enter the 'Client' ID' and other desired data. Click 'Display Report'. Validate the report data. Close the report. Close the form. Open 'Real Time Inquiry (270) Request'. Enter the 'Client ID', 'Guarantor' and other desired data. Click [Process Report]. Click [OK]. Review the report data. Validate that the 'Response' field contains the correct data. If desired, click [Post Inquiry]. Close the form. Open 'CareFabric Monitor'. Enter the desired 'From Date', 'Through Date' and 'Client ID'. Click [View Activity Log]. Review the data to ensure the events/actions were created. Close the report. Close the form.	Topics • Real Time Inquiry (270) Request • RevConnect
Update 74 Summary \| Details '274 - Provider Directory Definition' CareFabric Support Scenario 1: Verification of 'GetPDOrganizationResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. Scenario 2: Verification of 'GetPDLocationResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. Scenario 3: Verification of 'GetPDPractitionerResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. Scenario 4: Verification of 'GetPDPractitionerRoleResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. Scenario 5: Verification of 'GetPDHealthcareServiceResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. Scenario 6: Verification of 'GetPDOrganizationResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. Scenario 7: Verification of 'GetPDLocationResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. Scenario 8: Verification of 'GetPDPractitionerResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. Scenario 9: Verification of 'GetPDPractitionerRoleResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only. Scenario 10: Verification of 'GetPDHealthcareServiceResource' Action for '274 - Provider Directory Definition' Information Steps Internal testing only.	Topics • CareFabric

Avatar_CareFabric_2023_Monthly_Release_2023.04.00_Details.csv