/
Implementing Secure Web Services using Professional Profile Implementing Secure Web Services using Professional Profile

Implementing Secure Web Services using Professional Profile - PowerPoint Presentation

jane-oiler
jane-oiler . @jane-oiler
Follow
383 views
Uploaded On 2016-05-16

Implementing Secure Web Services using Professional Profile - PPT Presentation

MedBiquitous Annual Meeting May 10 2011 Madhavkumar Iyer NBME miyernbmeorg Neal Swearer AAMC nealsweareraamcorg What is Data Commons An infrastructure for realtime creation of data sets across organizations in the House of Medicine based on agreements ID: 322515

commons data medmember medbiquitous data commons medbiquitous medmember org service http web professional member xmlns xml getstudentprofile aamc response

Share:

Link:

Embed:

Download Presentation from below link

Download Presentation The PPT/PDF document "Implementing Secure Web Services using P..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.


Presentation Transcript

Slide1

Implementing Secure Web Services using Professional Profile (Data Commons)

MedBiquitous Annual Meeting (May 10, 2011)

Madhavkumar Iyer

NBME

miyer@nbme.org

Neal Swearer

AAMC

neal.swearer@aamc.orgSlide2

What is Data Commons?

An infrastructure for real-time creation of data sets across organizations in the House of Medicine based on agreements.Developed jointly by NBME & AAMC.

Not a new repository. Data sets compiled from existing repositories and expunged after creation.Organizational members build infrastructure collaboratively and own and operate it jointly.Used to aggregate data sets for individuals, educational programs, institutions and educational research.

Individual medical professional can compile data for private self-assessment or to authorize public report-out of selected information.

2Data CommonsSlide3

Definitions

Data Sharing AgreementAgreement between participating organizations for the exchangefor data in real-time.

ProviderA participating organization providing data to Data CommonsInvoker

A participating organization requesting data from Data CommonsIDMSIdentity Matching Service

to match or reconcile different identifiers usedacross multiple organizations for each medical professional.3

Data CommonsSlide4

System Architecture

4

Data CommonsSlide5

System Features

Connects to certified Data ProvidersAccepts requests only from member organizationsRequests are

authenticated & authorized before retrieving dataRequest/Response data is encrypted based on invoker’s 128 bit KEYRequests validated using Authorization Certificate

Transactions logged without storing request/response dataGeneric Web Service processes all requests from InvokersProviders provide data using Web Services

All Web Services are of document/literal format and secured by SSLGeneric Request/Response XML data formats for Invoker/Provider

5

Data CommonsSlide6

Technology

Application Server – J2EE 1.4Oracle Database 10g/11gJava / PL-SQLXML

SOAP 1.1WSDL 2.0AES 128 bit message encryption

6Data CommonsSlide7

Using MedBiquitous Professional Profile

The following operations uses MedBiquitous Professional Profile:Get Enrolled Students

NBME gets updated enrolled student information for each school from AAMCGet Matriculated StudentsNBME gets new matriculants for each school from AAMC

IDMS Biographic Update NBME and AAMC provide updates to IDMS

7Data CommonsSlide8

MedBiquitous Professional Profile -

Sample

8

Data CommonsSlide9

MedBiquitous XML Schemas

The MedBiquitous Healthcare Professional Profile Schema provides a data structure that allows one to represent one or more healthcare professionals in a standard format.

Data Commons uses version 1.0 of the following MedBiquitous

XML schemas:MemberNameAddress

Source: http://ns.medbiq.org/member/v1/

9

Data CommonsSlide10

Example 1: Using the MedBiquitous

XML SchemasGetStudentProfile

web service operationRequest<

DcomOutboundGetStudentProfileRequest xmlns

="http://www.dcom.org/service"> <OperationName>

GetStudentProfile</

OperationName>

<RequestPacket>

<

RequestHeader

>

<

AamcId

>12113983</

AamcId

>

<

MedicalSchoolCode

>816</

MedicalSchoolCode

>

</

RequestHeader

>

</

RequestPacket

>

<

TransactionId

>112312312318</

TransactionId

>

</

DcomOutboundGetStudentProfileRequest

>

10

Data CommonsSlide11

Example 1: Using the MedBiquitous

XML SchemasGetStudentProfile

web service operation (continued)Response<

DcomOutboundGetStudentProfileResponse

xmlns="http://www.dcom.org/service/getStudentProfile"

xmlns:dcom=http://www.dcom.org/service

xmlns:medAddress="http://ns.medbiq.org/address/v1/" xmlns:medMember

="http://ns.medbiq.org/member/v1/"

xmlns:medName

="http://ns.medbiq.org/name/v1/">

….

</

DcomOutboundGetStudentProfileResponse

>

11

Data CommonsSlide12

Example 1: Using the MedBiquitous

XML SchemasGetStudentProfile

web service operation (continued)Response<

medMember:Members> <medMember:Member

restrictions="Restricted"> <medMember:UniqueID

domain

="Member:USMLE

ID">52153983</medMember:UniqueID>

<

medMember:UniqueID

domain

="

Member:AAMC

ID">

12713993

</

medMember:UniqueID

>

</

medMember:Member

>

</

medMember:Members

>

12

Data CommonsSlide13

Questions?

13

Data Commons