From:                              pmaniar@ABMS.org

Sent:                               Wednesday, July 13, 2011 10:45 PM

To:                                   vsmothers@medbiq.org

Cc:                                   jmichael@ABMS.org; bruff@ABMS.org

Subject:                          RE: Changes to Medbiq Schema V2

 

Importance:                   High

 

Hi Valerie,

 

We are currently working on a project to exchange MOC requirements information with different organizations.  In order for us to exchange this information, we need several changes to the medbiq schema v2.  We would like to have these changes by July 22 for our testing.  If there is a problem with incorporating these elements into the v2 schema by July 22nd, please let me know.

 

Following lists all the changes to medbiq schema v2:

 

MOCInfo container needs to be added in Member container and right above XtensibleInfo section.  Changes are highlighted in yellow.

 

<xsd:complexType name="MemberType">

  <xsd:sequence>

  <xsd:element name="UniqueID" type="UniqueIDType" minOccurs="0" maxOccurs="unbounded" />

  <xsd:element name="Name" type="n:NameType" minOccurs="0" />

  <xsd:element name="Address" type="a:AddressType" minOccurs="0" maxOccurs="unbounded" />

  <xsd:element name="EducationInfo" type="EducationInfoType" minOccurs="0" maxOccurs="unbounded" />

  <xsd:element name="TrainingInfo" type="TrainingInfoType" minOccurs="0" maxOccurs="unbounded" />

  <xsd:element name="CertificationInfo" type="CertificationInfoType" minOccurs="0" maxOccurs="unbounded" />

  <xsd:element name="LicenseInfo" type="LicenseInfoType" minOccurs="0" />

  <xsd:element name="DisciplinaryInfo" type="DisciplinaryInfoType" minOccurs="0" />

  <xsd:element name="ClinicalStatus" type="ClinicalStatusType" minOccurs="0" />

  <xsd:element name="AcademicAppointmentInfo" type="AcademicAppointmentInfoType" minOccurs="0" />

  <xsd:element name="OccupationInfo" type="OccupationInfoType" minOccurs="0" maxOccurs="unbounded" />

  <xsd:element name="PersonalInfo" type="PersonalInfoType" minOccurs="0" />

  <xsd:element name="MembershipInfo" type="MembershipInfoType" minOccurs="0" maxOccurs="unbounded" />

  <xsd:element name="ModifiedDate" type="xsd:date" minOccurs="0" />

   <xsd:element name="MOCInfo" type="MOCInfoType" minOccurs="0" maxOccurs="unbounded" />

   <xsd:element name="XtensibleInfo" type="XtensibleInfoType" minOccurs="0" />

  </xsd:sequence>

  <xsd:attribute name="restrictions" type="a:RestrictionsType" />

  </xsd:complexType>

 

 

MOCInfoType type

<xsd:complexType name="MOCInfoType">

<xsd:sequence>

        <xsd:element name="MOCBoard" type="NonNullStringType" minOccurs="1" />

         <xsd:element name="MeetingMOCRequirements" type=" MeetingMOCRequirementsType" minOccurs="1" />

        </xsd:sequence>

  </xsd:complexType>

 

    MeetingMOCRequirementsType

 

<xsd:simpleType name="MeetingMOCRequirementsType">

- <xsd:restriction base="xsd:string">

  <xsd:enumeration value="Yes" />

  <xsd:enumeration value="No" />

  </xsd:restriction>

  </xsd:simpleType>

 

 

 

Level

Element

Attributes

ABMS Requirements

 

 

 

 

Required

Multiplicity

DataType

 

 

 

 

1.7

MOCInfo

 

Optional

0 or 1

Container

1.7.1

MOCBoard

 

Required

1

Non-null string

1.7.2

MeetingMOCRequirements

 

Required

1

Restricted (Valid Values are Yes, No)

 

 

Please let me know if you have any questions.  Sorry to inform you with these changes on a short notice.

 

Thank you. 

 

Purvi Maniar

Software Engineer

American Board of Medical Specialties

 

Please note new contact information:

222 North LaSalle Street, Suite 1500

Chicago, IL 60601-1117

Direct (312) 436-2615

Fax (312) 436-2715

Visit us online at www.abms.org

Please consider the environment before printing this e-mail

 



CONFIDENTIALITY NOTICE: This E-mail contains proprietary and confidential information intended only for the use of the recipient(s) named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient(s), please note that any dissemination, distribution or copy of this communication is strictly prohibited. Anyone who receives this communication in error should notify the sender immediately and delete the communication from all electronic media and destroy all physical copies thereof.