Skip to main content

Fulfillment requests

Fulfillment requests are the mechanism by which Care Connect sends orders or requests to external third-party vendors for specific services for enrolled patients. There are two types of fulfillment requests provided out of the box, each of which corresponds to a Fulfillment Request (mvn__PJN_Fulfillment_Request__c) record type. Users must have permission for at least one of the record types in order to create fulfillment requests without error. Additional types can be created as needed.

Table 151. mvn__PJN_Fulfillment_Request__c record types

Record type

API name

Description

Materials Order

PJN_Materials_Order

Defines a request to send non-drug materials to a patient.

SP Triage

PJN_SP_Triage

Defines a request to triage a drug order to a patient's specialty pharmacy.



When a fulfillment request is created, Care Connect automatically pulls in data from various records related to a patient's care plan using the PJN_FulfillmentRequestCreationHdlr trigger and saves them into a single Fulfillment Request (mvn__PJN_Fulfillment_Request__c) record. This ensures that the data that is sent to external parties is tracked for audit purposes while reducing manual data input. This also means that the record only contains static data, or the data from when the request is first generated and sent, even if the source data is eventually updated. This single record can then be easily delivered to external parties via integration paths of your choice. When external parties process the fulfillment request, details regarding any shipments can be captured in the Shipment (mvn__PJN_Shipment__c) object while updates pertaining to the status of the fulfillment can be captured in the Event (mvn__PJN_Event__c) object. These data generally come from the external vendors via the same integration paths if configured.

Mapping job and custom metadata

The retrieving and consolidating of data are completed via the following custom metadata types, including the fulfillment request mapping job that is defined for every program. When a user creates a fulfillment request from a patient's care plan, they can preview the compiled data before submitting the order or request.

  • The Fulfillment Request Creation (mvn__PJN_Fulfillment_Request_Creation__mdt) custom metadata type defines the fields that will be populated with values from the related Case record when a fulfillment request is created.

    Table 152. Sample fulfillment request mvn__PJN_Fulfillment_Request_Creation__mdt record

    Field label

    Sample value

    Care Plan Source Field API Name

    Id

    Mapping Object Type Name

    PJN_KTX_SP_Triage_Care_Plan

    Program

    PJN_KTX

    Record Type Developer Name

    PJN_SP_Triage

    Request Target Field API Name

    mvn__PJN_Care_Plan__c



  • The Mapping Job (mvn__PJN_Mapping_Job__mdt) custom metadata type defines the Fulfillment Request (mvn__PJN_Fulfillment_Request__c) object that mappings will be executed against. There should be a mapping job for every program.

    Table 153. Sample fulfillment request mvn__PJN_Mapping_Job__mdt record

    Field label

    Sample value

    Is Active

    true

    Target Object API Name

    mvn__PJN_Fulfillment_Request__c



  • The Mapping (mvn__PJN_Mapping__mdt) custom metadata type defines the type of mapping to be executed. There should be a mapping for every mapping job.

    Table 154. Sample fulfillment request mvn__PJN_Mapping__mdt record

    Field label

    Sample value

    Always Runs

    false

    Mapping Job

    The Mapping Job (mvn__PJN_Mapping_Job__mdt) metadata record created above for the given program.

    Mapping Type

    Field

    Source Object API Name

    Case

    Source Object Type Name

    PJN_KTX_SP_Triage_Care_Plan

    Note

    This must match the value of the Mapping Object Type Name field on the corresponding Fulfillment Request Creation (mvn__PJN_Fulfillment_Request_Creation__mdt) metadata record.



  • The Mapping Field (mvn__PJN_Mapping_Field__mdt) custom metadata type defines the source field and target field for a mapping of the Field Mapping Type. There can be multiple mapping fields for every mapping.

    Table 155. Sample fulfillment request mvn__PJN_Mapping_Field__mdt record

    Field label

    Sample value

    Mapping

    The Mapping (mvn__PJN_Mapping__mdt) metadata record created above.

    Source Field API Name

    Account.PersonBirthdate

    Target Field API Name

    mvn__PJN_Patient_Birthdate__c

    Note

    This is the API name of the field on the Fulfillment Request (mvn__PJN_Fulfillment_Request__c) record to which the mapped value is written.