Enhancing Oncology Model
1.0.1

Publish Box goes here

EOM Data Submission Process

The EOM data submission process has multiple steps, starting with the client system's request for the attribution list or "prefill data" - this is the list of beneficiaries whose data needs to be shared with CMS. Here, we detail the steps of the EOM data submission process form request for the attribution data through the ability to poll the CMS Innovation Support Platform (ISP) system for the submission status.

Step 1: Get the Attribution Data

The client system will initiate a request for the attribution (or "prefill data") via an API request to fetch prepopulated data for beneficiaries associated with their EOM entity ID.

The client system will share the following information as part of the attribution data API request:

  • Authorization token (Retrieved by the client system from the authorization server using the client credentials provided during registration)
  • Model Identifier (Fixed: EOM)
  • Entity Identifier (entity ID assigned by the Model, format EOM-PGP-XXXX)

The response to the client system will be a FHIR resource bundle of Parameter resources, with one Parameter resource per beneficiary. Each Parameter resource will contain the following:

  • Patient resource, including
    • Medicare Beneficiary Identifier(MBI)
    • Frist name, Last name
    • Date of birth
    • Administrative gender
    • Attributed cancer type
    • Episode start and end dates

Step 2: Data Submission Preparation

The EOM participant or client system will prepare a FHIR resource bundle with clinical data elements for each of the prepopulated beneficiaries received in Step 1. The prepared FHIR resource bundle will contain FHIR resources from one or more of the following EOM IG profiles based on the attributed cancer type:

The client system will then invoke a submission API request to submit the resource bundle. The client system will share the following information as part of the submission API request:

  • Authorization token (Retrieved by the client system from the authorization server using the client credentials provided during registration)
  • Model Identifier (Fixed: EOM)
  • Entity Identifier (entity ID assigned by the Model, format EOM-PGP-XXXX)
  • FHIR resource bundle with one or more resources

The ISP system will accept the submission if the data submitted are for an attributed beneficiary for the indicated Entity ID. The ISP system will verify the submitted data are for an attributed beneficiary. If the submitted data are accepted, the ISP system will send an acknowledgement response with the polling URL in the Content-Location header. If the submitted data are rejected, the ISP system will send an error response (OperationOutcome) with the appropriate status and error code details.

The ISP system will conduct both standard FHIR validations against the EOM IG profiles, code systems and terminologies, as well as custom EOM validations to ensure the data are also consistent with EOM requirements. For more information about validations, review General Guidance - Validations and Errors.

Step 3: Submission Status

The client system can poll the status URL received during submission to get the submission status. The client system must share the Authorization token and the Model identifier (EOM) as part of the submission status request.

If the FHIR processing has not been completed for the submission, the ISP system will return a response with HTTP status “202 Accepted” with X-progress header set to “FHIR Processing in progress”.

If the FHIR processing has been completed successfully, the ISP system will return a bundle resource with type batch-response with status and location/datatype of each resource.

If one or more of the resources in the submission could not be persisted into the FHIR server, the ISP system will return a bundle resource with type batch-response with OperationOutcome of error details for each resource.