Subject Data Story Boards
Contents
- 1 Links
- 2 Useful Guides
- 3 Sponsor Planned Data
- 4 Cross Reference to ICSR
- 5 Class 3
- 6 Class 4
- 7 Others
- 7.1 Story Board 10. Original CRF Value Changed
- 7.2 Story Board 11. Diagnose adverse event in a subject
- 7.3 Story Board 12. Evaluate AE for Severity
- 7.4 Story Board 13. Evaluate AE for Causality
- 7.5 Story Board 14. Determine if patients met inclusion criteria
- 7.6 Story Board 15.
- 7.7 Story Board 16.
- 7.8 Story Board 17.
- 7.9 Story Board 18.
- 7.10 Story Board 19.
Links
Stage 1B page | CDISC HL7 Project Page | Stage 2 Page
Useful Guides
For those wanting assistance in editing wiki pages have a look at these pages
Sponsor Planned Data
Data collected in accordance with the plan. The Study Design message conveys (among other things) the plan for data collection, the Study Participation message includes information on the subjects in the study, and thus those two messages imply an expected set of data to be collected. The subject data message needs to be able to convey that data.
Story Board 1: Submission of SDTM and ADaM Data
Study A1234 is complete and Acme Pharmaceuticals now wants to send to the FDA all the observations recorded for each subject during the study as part of their study report submission. Acme uses the CDISC-HL7 subject data message to provide all the recorded observations, as well as all the key derived parameters resulting from those observations, as defined by the CDISC SDTM and ADaM standards. The message contains all important relationships, such as the relationship between an observed and planned assessment (or lack thereof), and the relationship between unplanned assessments and other observations (i.e. physical exam finding of jaundice led to a bilirubin measurement). Those observations that were previously reported in a spontaneous adverse event report are not re-submitted, but rather updated and referenced.
Scope question: Do we want ADaM in here for the first version? How to define the word "key"? ACTION ITEM: Need to have someone from the ADaM team review and provide feedback.
Story Board 2: FDA Completeness Check
The FDA has recieved the data for Study A1234 and wishes to asses the level of completness of the data submitted by Acme Pharmaceuticals. Mr Reviewer accesses the Janus data warehouse and runs a check to assess if all planned activities were performed.
This requires access to the plan held within the Study Design message and needs to allow for all paths to be evaluated at a high level of detail definition (sufficient to allow for a machine to perform the check)
Story Board 3.
Planned data being captured but study is high risk and therefore FDA requested that data be provided at regular intervals while the trial is running.
Since Acme Pharmaceuticals study XYZ123 being conducted has some potential toxicity issues, the FDA requested that subject data be submitted quarterly while the trial was ongoing. Subject data was submitted on 5 occasions while the trial was ongoing include updates to previously sent data points. After the trial concluded, all of the subject data was sent to the FDA as a final transmission.
Cross Reference to ICSR
Data collected in connection with ICSRs. It should be easy to make connections between data in the ICSR and other data conveyed in the Subject Data message. At minimum, this probably means that the Subject Data message needs to include unique identifiers for ICSRs.
Story Board 4.
ABC Pharmaceuticals is running study 123A. One of their sites PharmaCRO reports an SAE. ABC Pharmaceuticals collects all the relevant information and promptly submits a report via the ICSR to the FDA (referenced by HL7 identifier 2.16.840.2.113883.4.125)
A year later, ABC pharmaceuticals is preparing their submission for study 123A to the FDA utilizing the Subject Data message. As part of their submission process, the information previously provided in the ICSR is filtered out and a link is inserted in it’s place which points back to the ICSR report.
Class 3
Story Board 5.
The FDA team is reviewing the Study 123A which was submitted by ABC Pharmaceuticals. Several patients have experienced SAEs for which the study design has pre-defined treatment strategies. FDA reviewers notice a wide disparity in the outcome for patients with similar disease levels.
The FDA requests to see a complete set of health records for the affected patients from ABC Pharmaceuticals, who in turn makes a request to all of their sites. Both use RPS as the information request and fulfillment mechanism.
The site constructs an EHR HL7 message containing the requested information and sends it to ABC Pharmaceuticals who in turn forwards the information to the FDA.
The FDA discovers that some sites have availed themselves of a new treatment procedure available for the treatment for these worrisome SAEs and that use of this procedure correlates back to improved outcomes.
Story Board 6: Sponsor Initiates Additional Data Collection
Use Case: Sponsor initiates the collection of additional data from investigators and then provides an update to the FDA. All of the data reported would be in addition to the plan. Study A1234 is complete and Acme Pharmaceuticals has provided the data to the FDA using the CDISC-HL7 subject data message to provide all the recorded observations, as well as all the derived parameters resulting from those observations, as defined by the CDISC SDTM and ADaM standards. Acme is aware of issues, need some more detailed explanation here ... that suggests that it would be desirable to collect some additional observations. The sponsor initiates the collection of the data from the sites and provides the new data to the FDA using the Subject Data message. This data needs to be linked to the data already provided to the FDA but is considered additonal to the plan as defined within the Study Design message
Note: Should these additional observations and the plan for them be noted in an updated Study Design message?
I think it should be.Dianewold
Class 4
Subject Data may be conveyed in multiple stages, rather than as a monolithic data transfer. Therefore, the message must be capable of conveying both new and updated data.
Story Board 7: Periodic SubjectData messages (blinded) and then data is unblinded
See the above use cases
- Since Acme Pharmaceuticals study XYZ123 is being conducted in a vulnerable population, FDA requested that subject data be submitted quarterly while the trial was ongoing.
- Subject data was submitted on 5 occasions while the trial was ongoing. In data on study drug administration, the name of study drug was given as “Blinded product” and dose was recorded with units of “tablets.”
- After the trial completed and was unblinded, data on study drug administration was updated to include all subjects, and to provide actual study drug data (Drug A, Drug B, or Placebo) for all subjects and dose information (20 mg for Drug A, 50 mg for Drug B) for subjects who received active product.
Story Board 8: Periodic sending of SubjectData messages and Clarification process results in a data point being changed
- Since Acme Pharmaceuticals study XYZ123 is being conducted in a vulnerable population, FDA requested that subject data be submitted quarterly while the trial was ongoing.
- On the second occasion when data was submitted, lab data included an ALT value of 526 for subject 145 at Visit 3.
- This abnormal ALT value triggered a query. The response to the query was that there was a transcription error, and the true value was 256.
- In the third submission of periodic data to the FDA, the message included the corrected ALT value of 256 for subject 145 at Visit 3.
Story Board 9. Rolling NDA (PENDING)
Rolling NDA – might be worth having a use case around this
Others
Story Board 10. Original CRF Value Changed
Use Case: Sometimes the original CRF value is changed by the sponsor (could be the investigator in the case of correcting a data entry error). When this happens, the message needs to state the first and final data value. Further information (the full audit trail) would be provided in a different message if requested.
1. ABC Pharmaceuticals has completed Study123A and this study is part of a submission for a drug that lowers blood pressure.
2. Data was collected via paper CRFs.
3. Subject data for BOB123 has a first data value for a concomitant medication of “Atenolol” and a last concomitant medication value of “Aspirin”. It is highly suspicious since “Atenolol” is a prohibited medication. The reason for the change is “Dose correction” on the last Aspirin medication record.
4. A message has been sent from the FDA back to ABC Pharmaceuticals requesting the full audit trail for all of BOB123 concomitant medication records.
5. ABC sends a message back to the FDA with the full audit trail for BOB123 concomitant medications which has 6 modifications for the record of first value of “Atenolol” and last value of “Aspirin”.
Story Board 11. Diagnose adverse event in a subject
An drug that is marketed in Europe is being evaluated for marketing in the US. A consumer group claims that the drug is associated with a specific adverse event. A reviewer needs to evaluate patients that were treated with the product, and determine if they have experienced the adverse event. This will require the reviewer to evaluate patients that may not have been previously diagnosed as experiencing the adverse event. Planned and unplanned observations and requests for further info (see other use cases)
Story Board 12. Evaluate AE for Severity
Use Case: A product is known to cause a particular adverse event. Depending upon the severity of the adverse event, the effect of the adverse event on the patient can range from minor discomfort to disability or death. A reviewer needs to determine how many patients experienced the more severe manifestations of the adverse event. Message needs to provide links to the related data that was used to perform assessment of severity. These links would need to be pre-defined. Need to detail when these links are created and under what circumstances Message needs, links, planned + unplanned and request further data as per previous use cases
Story Board 13. Evaluate AE for Causality
Use Case: An drug that is marketed in Europe is being evaluated for marketing in the US. A consumer group claims that the drug causes a specific adverse event. A reviewer needs to evaluate patients that were treated with the product and experienced the adverse event, and determine if these adverse events can be reasonably explained by factors other than the drug, such as high fever, meningitis, treatment with drugs known to cause the adverse event, or pre-existing conditions. In order to determine causality, the reviewer plans to use reasoning similar to that described by Austin Bradford Hill in his paper “The Environment and Disease: Association or Causation (Proceedings of the Royal Society of Medicine, 58 (1965), 295-300.) Similar notes to Case Review 2
Story Board 14. Determine if patients met inclusion criteria
The NCI-sponsored Study RTOG 93-09 is a randomized, unblinded, multicenter, two arm parallel design study comparing Chemotherapy + Radiation Therapy (CT+RT) vs. Chemotherapy + Radiation Therapy + Surgery (CT+RT+S) for the treatment of Stage IIIa non-small cell lung cancer. A key inclusion criterion requires the presence at screening of a single, newly diagnosed, primary lung parenchymal lesion of stage IIIA (T1, 2 or 3) with ipsilateral positive mediastinal nodes. The reviewer wants to ensure that only subjects meeting this criterion were enrolled. The Study Design message contains the plan to collect these screening data, and the reviewer is able to locate and analyze the collected screening data for each subject from the Subject Data message to verify that this criterion was met.
Use Case: A study is conducted in order to determine if a product is safe and effective in a sub-population of patients. The inclusion criteria are constructed so that only patients in the sub-population of interest are enrolled in the study. The reviewer wants to ensure that only patients who met the inclusion criteria were enrolled in the study. Requirement on Study Design message to indicate those observations used to support inclusion / exclusion processing
Story Board 15.
Estimate mean and variance of subject response in a study cell, and functions of these means and variances. A reviewer wishes to estimate the mean and variance of a continuous response variable (e.g. blood pressure) at one or more times (e.g. visit) in one or more study cells, and calculate functions of these means and variances.
Story Board 16.
Estimate mean survival time for subjects in a study cell A reviewer needs to estimate the mean survival time to an event (e.g. heart transplant) in a study cell. In order to calculate the mean, the reviewer needs to know if the event happened, and if the happened, when the event happened.
Story Board 17.
Estimate the baseline value of a subject response An analyst want to estimate the pretreatment value of a patient outcome (e.g. blood pressure). Estimation of this value will be based upon one or more values of the attribute in a study cell prior to the study cell containing study treatment, or from patient history data. Being able to link observations to the study design
Story Board 18.
Test that a function of the data in one or more study cells is equal to, less than, or greater than a constant. Calculate an analysis of covariance for a continuous outcome measure for study cells in the second epoch of the study. The value at visit 3 is the response variable, and the sponsor-defined baseline score is the covariate. Message needs to allow for linking of the data to the study plan.
Story Board 19.
Test that a function of the data in one or more study cells is equal to, less than, or greater than a constant. Calculate a Mantel-Haenszel test for study cells in the second epoch of the study. The response variable is categorical (e.g. presence or absence of an adverse event, seriousness of an adverse event). Stratification needs to be done by site, age, sex, and race.