Summary
The code performs the following tasks:
Create a new dataset (heart_data) using the sashelp.heart dataset. In this step, it also creates a new variable called 'Smoking_Status_Group'. If the 'Smoking_Status' value is missing, the 'Unknown' category is assigned to the 'Smoking_Status_Group' variable. Otherwise, the original value is kept.
Use PROC SUMMARY to calculate the average systolic blood pressure ('Systolic') by 'Sex' and 'Smoking_Status_Group'. The output dataset, avg_sbp, contains the mean systolic blood pressure for each combination of 'Sex' and 'Smoking_Status_Group'.
Sort the avg_sbp dataset by 'Sex' and 'Smoking_Status_Group' to prepare it for the transposition step.
Use PROC TRANSPOSE to transpose the avg_sbp dataset, pivoting on the 'Smoking_Status_Group' variable. This creates a new dataset called transposed_sbp, where each unique value of 'Smoking_Status_Group' becomes a new variable, and the corresponding 'Avg_Systolic' values fill in the dataset.
Print the transposed_sbp dataset using PROC PRINT to display the results. The output shows the average systolic blood pressure for each combination of 'Sex' and 'Smoking_Status_Group' in a transposed format.
This code allows you to analyze the average systolic blood pressure for different groups based on sex and smoking status, with the results presented in a more compact and readable form.

* Use the sashelp.heart dataset;
data heart_data;
    length Smoking_Status_Group $200;
    set sashelp.heart;
    if missing(Smoking_Status) then
        Smoking_Status_Group = 'Unknown';
    else
        Smoking_Status_Group = Smoking_Status;
    keep Sex Systolic Smoking_Status_Group;
run;

* Calculate the average systolic blood pressure by Sex and Smoking_Status_Group;
proc summary data=heart_data nway;
    class Sex Smoking_Status_Group;
    var Systolic;
    output out=avg_sbp mean(Systolic)=Avg_Systolic;
run;

* Sort the dataset;
proc sort data=avg_sbp;
    by Sex Smoking_Status_Group;
run;

* Transpose the dataset;
proc transpose data=avg_sbp out=transposed_sbp;
    by Sex;
    id Smoking_Status_Group;
    var Avg_Systolic;
run;

* Print the transposed dataset;
proc print data=transposed_sbp;
run;

Keeping track of time is crucial in project management and even more so when it comes to billing hours. Google Calendar is an excellent tool for organizing and scheduling, but it doesn’t provide an out-of-the-box solution for timesheet management. On the other hand, Google Sheets allows for easy tabulation and calculation but lacks the intuitive visual aspect of a calendar.

What if we could bring together the best of both worlds? In this post, we will do exactly that. We will guide you through creating a two-way sync between Google Calendar and Google Sheets using Google Apps Script.

This will enable employees to log their time spent on various tasks in a familiar calendar interface while automatically updating the project timesheet in Google Sheets. Managers can benefit from this approach by gaining a clear overview of project timelines, employee workloads, and overall time allocation.

Step 1: Prepare Your Google Sheet

First, you need to set up your Google Sheet in the right format. The sheet should have the following columns: “Date“, “Start Time“, “End Time“, “Task“. Make sure “Date” is in the “YYYY-MM-DD” format and “Start Time” and “End Time” are in the “HH:MM” 24 hour format. Each row represents a single event.

Step 2: Open Google Apps Script

From your Google Sheet, click on Extensions > Apps Script. This will open the Google Apps Script editor where you can write and manage your scripts.

Step 3: Write the Scripts

We’ll write two scripts: one to create calendar events from the sheet data (`createCalendarEvent`), and one to fetch calendar events and write them into the sheet (`fetchCalendarEvents`).

Here is the createCalendarEvent function:

// createCalendarEvent
function createCalendarEvent() {
  let communityCalendar = CalendarApp.getCalendarById("YOUR_CALENDAR_ID");
  let sheet = SpreadsheetApp.getActiveSheet();

  let schedule = sheet.getDataRange().getValues();
  schedule.splice(0, 2); // Remove header rows

  schedule.forEach(function(entry){
    let title = entry[3];
    let date = entry[0];
    let startTime = entry[1];
    let endTime = entry[2];

    let startDateTime = new Date(date.getFullYear(), date.getMonth(), date.getDate(), startTime.getHours(), startTime.getMinutes());
    let endDateTime = new Date(date.getFullYear(), date.getMonth(), date.getDate(), endTime.getHours(), endTime.getMinutes());

    let events = communityCalendar.getEvents(startDateTime, endDateTime);

    let isDuplicate = events.some(function(event) {
      return event.getTitle() === title;
    });

    if (!isDuplicate) {
      communityCalendar.createEvent(title, startDateTime, endDateTime);
    }
  });
}

And here is the fetchCalendarEvents function:

// fetchCalendarEvents
function fetchCalendarEvents() {
  let communityCalendar = CalendarApp.getCalendarById("YOUR_CALENDAR_ID");
  let sheet = SpreadsheetApp.getActiveSheet();

  sheet.getRange('A3:D').clearContent(); // Clear all rows starting from the third row

  let now = new Date();
  let events = communityCalendar.getEvents(new Date(now.getFullYear(), 0, 1), new Date(now.getFullYear() + 1, 0, 1));

  for (let i = 0; i < events.length; i++) {
    let startDateTime = events[i].getStartTime();
    let endDateTime = events[i].getEndTime();

    let startTime = Utilities.formatDate(startDateTime, Session.getScriptTimeZone(), 'HH:mm');
    let endTime = Utilities.formatDate(endDateTime, Session.getScriptTimeZone(), 'HH:mm');

    sheet.getRange(i + 3, 1).setValue(new Date(startDateTime.getFullYear(), startDateTime.getMonth(), startDateTime.getDate()));
    sheet.getRange(i + 3, 2).setValue(startTime);
    sheet.getRange(i + 3, 3).setValue(endTime);
    sheet.getRange(i + 3, 4).setValue(events[i].getTitle());
  }
}

Remember to replace “YOUR_CALENDAR_ID” with your own Google Calendar ID in both scripts.

Step 4: Save and Run the Scripts

After you’ve written the scripts, click on the floppy disk icon or File > Save to save your project. Give it a name like “Calendar-Sheet Sync”.

To run the scripts, select the function you want to run from the dropdown list next to the bug icon, then click the triangle ‘Run’ button. The first time you run the scripts, Google will ask for your permission to access your Google Calendar and Google Sheets. Click on ‘Review Permissions’, choose your account, and then click ‘Allow’.

Step 5: Test the Scripts

Try adding a few events to your Google Sheet and running the `createCalendarEvent` function. Then, check your Google Calendar to see if the events have been added.

Next, try adding some events directly to your Google Calendar. Run the `fetchCalendarEvents` function and check your Google Sheet. The events you added to the calendar should now appear in the sheet.

Step 6: Create Buttons for the Scripts

For easier access, you can create buttons in your Google Sheet that trigger the scripts when clicked. Here’s how to do it:

1. On your Google Sheet, click on Insert > Drawing. Draw a shape (this will be your button). Click Save and Close when you’re done.
2. Click on the drawing you just made, then click the three dots in the top right corner. Choose Assign Script.
3. In the text box that appears, write the name of the function you want to assign to the button (createCalendarEvent or fetchCalendarEvents), then click OK.
4. Repeat the process for the second function.

Now, whenever you click these buttons, the corresponding function will run. This is a handy way to manually sync your Google Sheet with your Google Calendar and vice versa without having to open Google Apps Script.

In the realm of project management, accurate and efficient time tracking is paramount. By integrating Google Calendar with Google Sheets, we can create a dynamic, visual, and easily manageable solution for timesheet logging. The two-way synchronization allows employees to update their hours in the calendar, which then reflects in the timesheet automatically. Similarly, any updates in the timesheet are immediately visible in the calendar view.

For managers, this approach offers valuable insights into project timelines, workloads, and time allocation at a glance, enabling better planning and resource management. Whether you are a manager looking for an improved way to visualize your team’s workload or an employee wanting a simpler method to log hours, this solution brings together the intuitive interface of Google Calendar and the data management capabilities of Google Sheets. Happy planning and tracking!

1. Familiarize yourself with CDISC standards: Before starting, ensure that you have a good understanding of the SDTM and ADaM (Analysis Data Model) standards, as well as the CDISC Controlled Terminology.
   
2. Gather necessary documentation: Collect all relevant documentation for your clinical trial, such as the protocol, case report forms (CRFs), and annotated CRFs.
   
3. Identify the SDTM domains: Identify the SDTM domains relevant to your study, such as demographics (DM), adverse events (AE), concomitant medications (CM), and others.
   
4. Create dataset specifications: For each SDTM domain, create dataset specifications that include the variable name, label, type, length, and controlled terminology (if applicable).
   
5. Obtain or create an ODM (Operational Data Model) file: An ODM file is an XML file that describes the metadata for your clinical trial. You can either export this file from your EDC (Electronic Data Capture) system or create it using an XML editor.
   
6. Generate the define.xml file: Use a software tool or a programming language like SAS, R, or Python to generate the define.xml file based on the dataset specifications and ODM file. Popular tools for generating define.xml files include Pinnacle 21, SAS Clinical Standards Toolkit, and OpenCDISC Validator.
   
7. Validate the define.xml file: After generating the define.xml file, validate it using a validation tool like Pinnacle 21 or OpenCDISC Validator to ensure it conforms to the CDISC standards.
   
8. Review and finalize the define.xml file: Review the define.xml file and address any issues or discrepancies identified during the validation process. Make sure that the file accurately reflects the structure, content, and formatting of your datasets.
   
9. Include the define.xml file in your submission package: Once the define.xml file is finalized, include it in your submission package, along with the SDTM and ADaM datasets, the annotated CRFs, and any other required documentation.

Remember that creating a define.xml file for SDTM is a complex process that requires a solid understanding of CDISC standards and clinical trial data management. It’s always a good idea to involve a data manager or a biostatistician with experience in this area to ensure compliance with regulatory requirements.