Top Banner
Metadata becomes alive via a web service between MDR and SAS Kevin Lee NY PhUSE SDE on May 14 th 2015 We help our Clients deliver better outcomes, so they can improve the quality of people’s lives.
26

Metadata becomes alive via a web service between MDR and SAS

Aug 07, 2015

Download

Healthcare

Kevin Lee
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Metadata becomes alive via a web service between MDR and SAS

Metadata becomes alive via a web service between MDR and SASKevin LeeNY PhUSE SDEon May 14th 2015

We help our Clients deliver better outcomes, so they can improve the quality of people’s lives.

Page 2: Metadata becomes alive via a web service between MDR and SAS

2© 2015 Accenture All Rights Reserved.

AgendaIntroduction of Metadata

Introduction of MDR

A Web Service and its method (SOAP and REST)

Data Exchange between MDR and SAS

SOAP XML request and response file

Conversion to SAS data set

Metadata driven clinical artefacts development

Page 3: Metadata becomes alive via a web service between MDR and SAS

3© 2015 Accenture All Rights Reserved.

Introduction of Metadata• Definition

• Data about other data• Examples of metadata

Variable Name

Variable Label Type CT Role Core

STUDYID Study Identifier Char Identifier Req

DOMAIN Domain Abbreviation Char DM Identifier Req

USUBJID Unique Subject Identifier

Char Identifier Req

Page 4: Metadata becomes alive via a web service between MDR and SAS

4© 2015 Accenture All Rights Reserved.

Types of Metadata• Structural metadata

Target dataset

Target variable

Business Rule Source dataset

Source variable

DM USUBJID is equal to DEMO USUBJID

DM AGE Age from birth date to study start date

Target dataset

Target variable

Machine readable derivation

Source dataset

Source variable

DM USUBJID = DEMO USUBJID

DM AGE %AGE(DM.RFSTDTC – BRTHDTC)

Variable Name Variable Label Type CT Role Core

USUBJID Unique Subject Identifier Char Identifier Req

Age Age Num Identifier Req

• System agnostic transformation metadata

• System dependable transformation metadata

Page 5: Metadata becomes alive via a web service between MDR and SAS

5© 2015 Accenture All Rights Reserved.

Evolution of metadata technology

Spreadsheet or document

Database

Metadata Repository

Page 6: Metadata becomes alive via a web service between MDR and SAS

6© 2015 Accenture All Rights Reserved.

Metadata Repository (MDR) • General definition: an application for database

created to store metadata. • Its function in healthcare:

• Develop and maintain Standards metadata(e.g., CDISC Standards and sponsors-specific Standards)

• Govern Standards metadata(e.g., workflow, people)• Control Standards versions• Store the history of all the activities(e.g., request,

development, approval and retirement )• Provide taxonomy/level of Standards and their library

• Industry/Dictionary • Global, Therapeutic, Compound, Study

Page 7: Metadata becomes alive via a web service between MDR and SAS

7© 2015 Accenture All Rights Reserved.

Study level metadata definition development in MDR

MDR

Protocol

Global Library

CDASH

TFL

ADaM

SDTM

Protocol

Study 001

CDASH

TFL

ADaM

SDTM

Page 8: Metadata becomes alive via a web service between MDR and SAS

8© 2015 Accenture All Rights Reserved.

MDR

Protocol

Global Library

CDASH

TFL

ADaM

SDTM

Protocol

Study 001

CDASH

TFL

ADaM

SDTM

Study level metadata definition development in MDR (2)

Page 9: Metadata becomes alive via a web service between MDR and SAS

Question

What

How

Why

• Now, we built all the study level metadata in MDR, but then what?

Page 10: Metadata becomes alive via a web service between MDR and SAS

10© 2015 Accenture All Rights Reserved.

Why is Study Level metadata definition in MDR important?

MDR

Protocol

Study 001

CDASH

TFL

ADaM

SDTM

Protocol

EDC database

eCRF

SDTM datasets

ADaM datasets

TFL

It can dictate study level artefacts development.

Study 001

Page 11: Metadata becomes alive via a web service between MDR and SAS

11© 2015 Accenture All Rights Reserved.

How can study level metadata in MDR be used to create artefacts?

MDR

Protocol

Study 001

CDASH

TFL

ADaM

SDTM

Protocol

EDC database

eCRF

SDTM datasets

ADaM datasets

TFL

How?

Study 001

Page 12: Metadata becomes alive via a web service between MDR and SAS

12© 2015 Accenture All Rights Reserved.

Data(e.g., metadata) exchange over internet

Page 13: Metadata becomes alive via a web service between MDR and SAS

13© 2015 Accenture All Rights Reserved.

Introduction of a web service

A web service is a method of communication that allows two software systems to exchange the data over the internet. Two primary architectures for web services are SOAP and REST.

Page 14: Metadata becomes alive via a web service between MDR and SAS

14© 2015 Accenture All Rights Reserved.

Introduction of Simple Object Access protocol (SOAP)

Simple Object Access protocol (SOAP) is a protocol specification for data exchange in web services. • It is platform, system and language independent and

communicates through the internet. • It uses XML format and Hypertext Transfer Protocol

(HTTP). • It sends request files in XML and receives response file in

XML. • Structures: SOAP envelope, head and body.

Page 15: Metadata becomes alive via a web service between MDR and SAS

15© 2015 Accenture All Rights Reserved.

Introduction of Representational state transfer (REST)

Representational state transfer (REST) is a simpler data exchange format than SOAP data exchange. • It is also platform, system and language independent and

communicates through the internet. • It also uses HTTP, but unlike SOAP, response files come

ready to be used, not wrapped in SOAP envelope. So, REST does not need to use XML format to send and receive data through web services.

• It could include HTTP Get parameters in the URL

Page 16: Metadata becomes alive via a web service between MDR and SAS

MDR

SOAP

SAS Environment

SOAP request.xml (2)

SOAP response.xml (4)

SAS datasets (6)

Secured Internet (HTTPS)

XML conversion SAS program(5)

SOAP request

SAS program (3)

Example of Metadata Flow Diagram between MDR and SAS using SOAP

WSDL(1)

Page 17: Metadata becomes alive via a web service between MDR and SAS

17© 2015 Accenture All Rights Reserved.

1. Example of WSDL• Web Service Description Language (WSDL), which is an

XML-based interface definition language that is used for describing the functionality offered by a web service of MDR.

• With WSDL and SOAPUI, SOAP XML request file can be created.

• Example:<wsdl:definitons xmlns:wsdl=“http://schemas.xmlsoap.org/wsdl” xmlns:s=“http://www.w3.org/2001/XMLschema” > <wsdl:types>

<s:element name=“GetMetadata”> <s:sequence> <s:element name=“Study”/> <s:element name=“Standards”/></s:sequence> </s:element”>

…. </wsdl:types>

…..

Page 18: Metadata becomes alive via a web service between MDR and SAS

18© 2015 Accenture All Rights Reserved.

2. Example of SOAP XML request file to MDR

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.accenture.adrs.com/quantum/client1"> <soapenv:Header/> <soapenv:Body> <ns:GetMetadata>

<ns:Study>study001</ns:Study><ns:Standards>SDTM</ns:Standards>

</ns:GetMetadata> </soapenv:Body></soapenv:Envelope>

Page 19: Metadata becomes alive via a web service between MDR and SAS

19© 2015 Accenture All Rights Reserved.

3. Example of SAS program for SOAP request

FILENAME request 'T:\study001\Request.xml' ;FILENAME response 'T:\study001\Response.xml'; DATA _NULL_;** URL is from SOAP Header in POST;

url="http://www.accenture.adrs.com/quantum/client1"; ** SOAPACTION is from SOAP Header in POST;

SOAPACTION='GetMetadata';rc=SOAPWEB("request",url,"response",soapaction,,,,,,,);

RUN;

Page 20: Metadata becomes alive via a web service between MDR and SAS

20© 2015 Accenture All Rights Reserved.

4. Example of SOAP XML response file from MDR<?xml version="1.0" encoding="UTF-8"?> <GetMetadataResponse > <GetMetadataResult xmlns=“http://www.cdisc.org/ns/sdtm/v3.2” > <domain label="Demographics" name="DM">

<variable> <name>USUBJID</name> <label>Unique subject Identifier</label> <type>Char</type> <source>DEMO.USUBJID</source> <deriviation>=</deriviation>

</variable> <variable>

<name>AGE</name> <label>Age</label> <type>Num</type> <source>DM.RFSTDTC DM.BRTHDTC</source> <deriviation>%AGE(DM.RFSTDTC, DM.BRTHDTC)</deriviation>

</variable> </domain>

</GetMetadataResult> </GetMetadataResponse>

Page 21: Metadata becomes alive via a web service between MDR and SAS

21© 2015 Accenture All Rights Reserved.

5. Example of SAS program to convert XML files to SAS datasets

** SOAP response xml files;filename  myresp "T:\study001\Response.xml";  **** Create response xml map file;filename  respmap " T:\study001\response.map";libname myresp xmlv2 xmlmap=respmap automap=replace; **** Convert SOAP response xml files to SAS temporary dataset in work area;proc copy in=myresp out=work;run;

Data

Page 22: Metadata becomes alive via a web service between MDR and SAS

22© 2015 Accenture All Rights Reserved.

6. Example of SAS datasets from SOAP request file

GetMetadataResult_ORDINAL

domain_ORDINAL

domain_name domain_label

1 1 DM Demographics

domain_ORDINAL

variable_ORDINAL

name label type source derivation

1 1 USUBJID Unique subject identifier

Char DEMO.USUBJID

=

1 2 AGE Age Num DM.RFSTDTC MD.BRTHDTC

%AGE(DM.RFSTDTC, DM.BRTHDTC)

domain SAS dataset

variable SAS dataset

Page 23: Metadata becomes alive via a web service between MDR and SAS

23© 2015 Accenture All Rights Reserved.

What can we do with metadata from MDR in SAS environment?

Compliance checks on clinical study artefacts with metadata

Metadata driven clinical study artefacts development

Automated clinical study artefacts development driven by metadata.

Page 24: Metadata becomes alive via a web service between MDR and SAS

24© 2015 Accenture All Rights Reserved.

Metadata driven clinical study artefact development in SAS

MDR

Protocol

Study 001

CDASH

TFL

ADaM

SDTM

SAS

SDTM datasets

ADaM datasets

TFL

Web Service

SAS Engine

Page 25: Metadata becomes alive via a web service between MDR and SAS

25© 2015 Accenture All Rights Reserved.

Final Thought

Standards Metadata could be

developed, managed

and governed in

MDR

Study level metadata could be

developed in MDR

Through a web

service, study level metadata could be

transferred into SAS.

Metadata driven

study level artefacts

development in SAS

Page 26: Metadata becomes alive via a web service between MDR and SAS

26© 2015 Accenture All Rights Reserved.

Contacts and Questions

Kevin LeeEmail: [email protected]

LinkedIn: www.linkedin.com/in/hellokevinlee

Slides: www.slideshare.net/KevinLee56

Tweet: @HelloKevinLee

Blogs: HiKevinLee.tumbrl.com