02 - Claim Request - Professional Services - New Transaction

The overall structure of the message algins with the Claim for a Medication Dispense, where possible. Many resources are identical, including Bundle, Message Header, Patient and Coverage resources. The Professional services claim request does not include dispense data, though it will reference medications when the service relates specifically to a medication or to a pharmacist adaption. Only message changes that are specific to Professional Services claims are outlined below. .

Support for New Fields during MVP

As a general rule, new fields that have been added to support the Professional Services claim will be optional for MVP. The PCS standard allows for provision of the data if the data is present and already captured as discrete data in the Pharmacy application. There is no desire or expectation that the Pharmacy User should need to take extra steps to input data that is not collected today during the initial rollout. If the data is present as a discrete data field in the pharmacy application, it may be sent as part of the MVP work.

From the adjuidcator perspective, there is no expectation that new fields will be populated during MVP unless indicated specifically. The longer term benefit to providing additional data is that it will ultimately reduce auditing and claw backs to the pharmacy. Over time and as use cases evolve and implementers gain experience, additional data will be sent in order to fully realize these benefits.

New Fields and Functionality

Feature	MVP Scope	Details	POS - Sender Responsibility - MVP	Adjudicator - Receiver Responsibility - MVP
CLAIM INFORMATION	[Professional Claim Request Profile]
NEW MESSAGE New Professional services message	MANDATORY	A new transaction to support the Professional service. Mandatory support from onset; Adjudicator must determine fixed values that are in CPHA3 but not in FHIR when mapping request	MANDATORY	MANDATORY
STREAMLINED CLAIM REQUEST	MANDATORY	The new transaction eliminates unnecessary fields and allows for new data to be sent BENEFIT: Additional information should reduce audits and clawbacks	All new fields are optional though must be populated where data is available	Should consume as required
NEW FIELD ORIGINAL MEDICATION/DIN - PRESCRIPTION DATA	MANDATORY Mappable	Use Case: Pharmacy Adaptation. Useful for adjudicators to match with original prescription. Future Use BENEFIT: Additional information should reduce audits and clawbacks	OPTIONAL Data should be sent if sent today for certain professional services. POS may include if data is available, however, no additional inputs should be required by Pharmacy users	OPTIONAL Data will be sent as it is today for specific services.
NEW FIELD ADAPTED PRESCRIPTION: SUBSTITUTED DIN - PRESCRIPTION DATA	Optional	Use Case: Pharmacy Adaptation. May be useful for adjudicators	OPTIONAL Not required for MVP. POS may include if data is available, however, no additional inputs should be required by Pharmacy users. Br> BENEFIT: Additional information should reduce audits and clawbacks	OPTIONAL No expectations that data will be provided for MVP.
NEW FIELD Clinical Notes	Optional	Use Case: Pharmacy Adaptation. May be useful for adjudicators	OPTIONAL Not required for MVP. POS may include if data is available, however, no additional inputs should be required by Pharmacy users BENEFIT: Additional information should reduce audits and clawbacks	OPTIONAL No expectations that data will be provided for MVP. . No expectation that data will be present.
NEW FIELD Adjusted/modified Dosage/Formulation - Text Claim:Supporting Information	Optional	Use Case: Pharmacy Adaptation BENEFIT: Additional information should reduce audits and clawbacks.	OPTIONAL No expectations that data will be provided for MVP. POS may include if data is available, however, no additional inputs should be required by Pharmacy users. BENEFIT: Additional information should reduce audits and clawbacks. Only text will be supported.	OPTIONAL No expectation that data will be present.
NEW FIELD Originating Prescriber ID Sent in Prescription/Medication Request	Optional	Use Case: Pharmacy Adaptation. May be useful for adjudicators	OPTIONAL Not required for MVP. POS may include if data is available, however, no additional inputs should be required by Pharmacy users. BENEFIT: Additional information should reduce audits and clawbacks.	OPTIONAL No expectations that data will be provided for MVP. No expectation that data will be present.
MAPPABLE NEW FIELD Therapeutic Substititution Code	MANDATORY For applicable use cases	This is conveyed in CPHA3 as an intervention code. The existing codes will be used but will be conveyed in a field specifically for this use. Examples are: supply disruption, patient safety or allergy.	OPTIONAL Though optional in the message this must be supported where Therapeutic substitution applies as it does currently	OPTIONAL Supported only where the professional service code indicates that the professional service is Therapeutic Substitition
NEW FIELD Adjusted Dosage or formulation	Optional	Must be sent for Prescription Adaptions if available and supported today	OPTIONAL - May be provided when available and applicable.	OPTIONAL Must be consumed where possible and applicable
NEW FIELD Clinical Notes	Optional	Not required for MVP BENEFIT: Additional information should reduce audits and clawbacks.	OPTIONAL No expectations that data will be provided for MVP. May optionally include if data is available. No additional inputs should be required by Pharmacy users	OPTIONAL No expectation that data will be present.
MAPPABLE FIELD - SERVICE CODE	MANDATORY	Professional Service Codes. The codes are typically conveyed as PINS today in CPHA3 in the DIN/MEDICAITON field. This field will support multiple codings to allow for movement to a national code set over time. Special service codes will also be supported though they are rarely used	MANDATORY Must send the code used by adjuidicators today and if available, should send the new national service code (being developed in 2026) for MVP.	MANDATORY Must support the PIN used today. No expectation to support the national code set during MVP
NEW FIELD LOCATION	Optional	A code to indicate where the service occurred, eg virtual, Patient's home, in pharmacy, etc	OPTIONAL No expectations that data will be provided for MVP. May optionally include if data is available. No additional inputs should be required by Pharmacy users** for MVP**	OPTIONAL for MVP
MAPPABLE FIELD - CARE TEAM	MANDATORY Mappable	Used to specify the Pharmacist responsible for the serivce. Includes a role. In future, may also be used to specify other members of the care team, such as a Nurse, Nurse Practitioner.	MANDATORY for Pharmacist; no expectation that others will be specified initially	MANDATORY For Pharmacist
NEW FIELD Care Team - Contact Indicator - Prescriber Contact Indicator - True or False.	Optional	Indicates that the prescriber has been contacted.	OPTIONAL May become mandatory for some implementers for specific use cases No expectations that data will be provided for MVP otherwise. POS may include if data is available, however, no additional inputs should be required by Pharmacy users. BENEFIT: Additional information should reduce audits and clawbacks.

FHIR Message

Following are some key points of note regarding the Claim request message structure:

1. Allows for "Prescription" data to be optionally included. Important for some use cases but not all. This includes the Prescriber and the medication/DIN, as well as a link from the Adapted Prescription. Though the "Medication Request" may convey full prescription details, only a few ncessary fields are supported in the Professional services claim.
2. Adapted Prescription Details - are only included if required. This can identified the Pharmacist as a Prescriber where applicable. Notes are also included as an optional data element.
3. Claim - this allows for a few additional fields for professional services as identified above, including the service location, care team members, adjusted/modified dosage/formulation, Therapeutic Substitition code and Clinical Reason code. All fields are optional and will vary by use case. None of these fields are expected during the MVP phase, though may be sent if the POS vendor wishes to do so and where no additional data must be entered by the user.
4. Though COB is rare for professional services, the message structure optionally allows for it, using a mechanism that is identical to the claim for dispensed medications. As such, minimal if any addtional work is required to support this.