There are three actors defined in this implementation guide which are guide to respond to two
transactions
Actor: Case Report Submitter
The Case Report Submitter is responsible for submitting
case report data. There are three options for the Submit Case Report transaction that a Case Reporter may use for submission of case reports depending on their purpose, nature, or maturity levels.
- Form submission - using a FHIR Questionnaire
- Tabular data submission (e.g. a CSV format with a header row). This can be take by tools like mAtches
- Direct export of FHIR Document from the EHR systems that have such a capability
Note that in the case of submission of tabular data, a
ConceptMap must be defined to map the names of the headers to the Questtionaire item.
Actor: Case Report Transformer
The Case Report Transformer is reponsible to perform any necessary transformation of case reports received from a Case Report Submitter via the Submit Case Report transaction into the requisite Case Report form to be sent into the Case Report Repository via the Store Case Report transaction. The Case Report Transformer must be able to repond to all
three options for the Submit Case Report transaction. A Case Report Transformer should also be responsible for ensuring security and auditing according to the ATNA profile.
Actor: Case Report Repository
The Case Report Repository is responsible for receiving case reports from the Case Report Transformer and storing those case reports for futher analysis and use in a data warehouse (generic FHIR server). The specific use of the case reports in the Case Report Repository is beyond the scope of this implementation guide as it will depend on the specific disease area.