MedBiquitous Competency Framework
Specifications and Description Document

 

 

 

 

Version: 0.1

Date: July 17, 2008

Author: Valerie Smothers

Author email: valerie.smothers@medbiq.org

 

 

 

 

Version History

 

Version No.

Date

Changed By

Changes Made

0.1

17 Jul 2008

Valerie Smothers

Initial draft

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


MedBiquitous Consortium XML Public License and Terms of Use

 

MedBiquitous XML (including schemas, specifications, sample documents, Web services description files, and related items) is provided by the copyright holders under the following license. By obtaining, using, and or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions.

 

The Consortium hereby grants a perpetual, non-exclusive, non-transferable, license to copy, use, display, perform, modify, make derivative works of, and develop the MedBiquitous XML for any use and without any fee or royalty, provided that you include the following on ALL copies of the MedBiquitous XML or portions thereof, including modifications, that you make.

 

  1. Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, the following notice should be used: “Copyright © [date of XML release] MedBiquitous Consortium. All Rights Reserved. http://www.medbiq.org”
  2. Notice of any changes or modification to the MedBiquitous XML files.
  3. Notice that any user is bound by the terms of this license and reference to the full text of this license in a location viewable to users of the redistributed or derivative work.

 

In the event that the licensee modifies any part of the MedBiquitous XML, it will not then represent to the public, through any act or omission, that the resulting modification is an official specification of the MedBiquitous Consortium unless and until such modification is officially adopted.

 

THE CONSORTIUM MAKES NO WARRANTIES OR REPRESENTATIONS, EXPRESS OR IMPLIED, WITH RESPECT TO ANY COMPUTER CODE, INCLUDING SCHEMAS, SPECIFICATIONS, SAMPLE DOCUMENTS, WEB SERVICES DESCRIPTION FILES, AND RELATED ITEMS. WITHOUT LIMITING THE FOREGOING, THE CONSORTIUM DISCLAIMS ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY, EXPRESS OR IMPLIED, AGAINST INFRINGEMENT BY THE MEDBIQUITOUS XML OF ANY THIRD PARTY PATENTS, TRADEMARKS, COPYRIGHTS OR OTHER RIGHTS.  THE LICENSEE AGREES THAT ALL COMPUTER CODES OR RELATED ITEMS PROVIDED SHALL BE ACCEPTED BY LICENSEE “AS IS”.  THUS, THE ENTIRE RISK OF NON-PERFORMANCE OF THE MEDBIQUITOUS XML RESTS WITH THE LICENSEE WHO SHALL BEAR ALL COSTS OF ANY SERVICE, REPAIR OR CORRECTION.

 

IN NO EVENT SHALL THE CONSORTIUM OR ITS MEMBERS BE LIABLE TO THE LICENSEE OR ANY OTHER USER FOR DAMAGES OF ANY NATURE, INCLUDING, WITHOUT LIMITATION, ANY GENERAL, DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, OR SPECIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF ANY USE OF MEDBIQUITOUS XML. 

 

LICENSEE SHALL INDEMNIFY THE CONSORTIUM AND EACH OF ITS MEMBERS FROM ANY LOSS, CLAIM, DAMAGE OR LIABILITY (INCLUDING, WITHOUT LIMITATION, PAYMENT OF ATTORNEYS’ FEES AND COURT COSTS) ARISING OUT OF MODIFICATION OR USE OF THE MEDBIQUITOUS XML OR ANY RELATED CONTENT OR MATERIAL BY LICENSEE.

 

LICENSEE SHALL NOT OBTAIN OR ATTEMPT TO OBTAIN ANY PATENTS, COPYRIGHTS OR OTHER PROPRIETARY RIGHTS WITH RESPECT TO THE MEDBIQUITOUS XML.

 

THIS LICENSE SHALL TERMINATE AUTOMATICALLY IF LICENSEE VIOLATES ANY OF ITS TERMS AND CONDITIONS.

 

The name and trademarks of the MedBiquitous Consortium and its members may NOT be used in advertising or publicity pertaining to MedBiquitous XML without specific, prior written permission. Title to copyright in MedBiquitous XML and any associated documentation will at all times remain with the copyright holders.

 

 



Acknowledgements

 

The MedBiquitous Consortium wishes to acknowledge the help of …

 


Introduction

 

Founded by Johns Hopkins Medicine and leading professional medical societies, the MedBiquitous Consortium is the ANSI-accredited developer of information technology standards for healthcare education and competence assessment. Our members are creating a technology blueprint for professional healthcare education. Based on XML and Web services standards, this blueprint will seamlessly support the learner in ways that will improve patient care and simplify the administrative work associated with education and competence assessment. MedBiquitous also provides a neutral forum for educators and industry alike to exchange ideas about innovative uses of Web technologies for healthcare education and communities of practice.

 

This document describes a data specification for …

 

 


Documentation Conventions

 

This document uses the following conventions.

 

Documentation Conventions

Convention

Description

monospaced type

 

Sample XML tags, code, schema, or portion thereof

BoldText

When used with an XML tag name, indicates that the element contains sub-elements

Italicized Text

When used in an XML tag description, an attribute of the XML tag.

Tag description

Shading indicated that the tag is further described elsewhere in the document

 

The following graphical standards are used for the XML diagrams in this document.

 

 

Graphical Standards from TIBCO’s Turbo XML, Copyright TIBCO Software Inc.

 


Data Elements

 

The Competency Framework schema includes the following elements. In some cases these elements have subelements.

 

  1. CompetencyFramework
  2. CompetencyDefinitions
  3. CompetencyDefinition
  4. Definition
  5. Statement
  6. Metadata
  7. CompetencyMap

 

The root element is CompetencyFramework.

 

Other Schema Referenced

 

The Competency Framework leverages the IEEE Standard for Learning Technology-Data Model for Reusable Competency Definitions, 1484.20.1-2007, available from http://standards.ieee.org/ .

 


Competency Framework Schema Grammar

 

The following sections explain the Competency Framework Schema grammar. Values in bold under XML Tags column indicate that the element has sub-elements.

 

All the elements having sub-elements will be defined in separate sections. All elements without sub-elements will be defined within the appropriate element sections that use them.

 

1         CompetencyFramework

CompetencyFramework is the root element. It contains subelements that describe a set of related competency definitions as well as the relationships among those competency definitions. CompetencyFramework must occur once within a competency framework document.

 

 

 

CompetencyFramework Element Information

Element

Description

Required

Multiplicity

Datatype

CompetencyFramework

CompetencyFramework is the root element. It describes a set of related competency definitions and their relationships.

Required

1

Container

Title

Title is the subelement of CompetencyFramework. It contains subelements that define the title for this competency framework in one or more languages. See section LanguageString for more information.

Required

1

LanguageString

Identifier

Identifier is the subelement of CompetencyFramework. It contains subelements that define a unique identifier for the competency framework. See section IdentiferType for more information.

Required

1

IdentifierType

CompetencyDefinitions

CompetencyDefinitions is the subelement of CompetencyFramework. It contains subelements that define a set of related competencies. For more information, see section CompetencyDefinitions.

Required

1

Container

CompetencyMap

CompetencyMap is the subelement of CompetencyFramework. It defines how the relationships among the defined competencies. ( This is currently a placeholder – structure will be completed in the future ).

Required

1

Container

 

Example:

 

To be completed

 

2         CompetencyDefinitions

CompetencyDefinitions define a set of related competencies. These competencies and their interrelationships comprise the competency framework. Typically a set of competencies is developed by a single organization or agency.

 

 


CompetencyDefintions Element Information

Element

Description

Required

Multiplicity

Datatype

CompetencyDefinitions

CompetencyDefinitions is the subelement of CompetencyFramework. It contains subelements that define a set of related competencies.

Required

1

Container

CompetencyDefinition

CompetencyDefinition is the subelement of CompetencyDefintions. It contains subelements that define a single competency in detail. For more information, see section CompetencyDefinition.

Required

1 or more

Container

 

Example:

<code>

 

2.1     CompetencyDefinition

CompetencyDefinition contains subelements that uniquely identify and describe a specific competency within the competency framework.

 

 

CompetencyDefinition Element Information

Element

Description

Required

Multiplicity

Datatype

CompetencyDefinition

CompetencyDefinition is the subelement of CompetencyDefintions. It contains subelements that define a single competency in detail.

Required

1 or more

Container

Identifer

Identifier is the subelement of CompetencyDefinition. It contains subelements that define a unique identifier for the competency definitions. See section IdentiferType for more information.

Required

1

IdentifierType

Title

Title is the subelement of CompetencyDefinition. It contains subelements that define the title for this competency definition in one or more languages. See section LanguageString for more information.

Required

1

LanguageStringType

Description

Description is the subelement of CompetencyDefinition. It contains subelements that provide a description of the competency in one or more languages. See section LanguageString for more information.

Optional

0 or 1

LanguageString

Definition

Definition is the subelement of CompetencyDefinition. It contains subelements that describe the competency through a formal definition using a structured model that may include a competency statement, outcome criteria, and assessment methods. See section Definition for more information.

Optional

0 or 1

Container

Metadata

Metadata is the subelement of CompetencyDefinition. It contains subelements that define the schema and version of the competency model used. See section Metadata for more information.

Optional

0 or 1

Container

 

Example:

<code>

 

2.2     Definition

 

Definition describes the competency through a formal definition using a structured model that may include a competency statement, outcome criteria, and assessment methods.

 

 

Definition Element Information

Element

Description

Required

Multiplicity

Datatype

Definition

Definition is the subelement of CompetencyDefinition. It contains subelements that describe the competency through a formal definition using a structured model that may include a competency statement, outcome criteria, and assessment methods.

Optional

0 or 1

Container

ModelSource

ModelSource is the subelement of Definition. It identifies the source of the structured model used for each structured competency definition. The recommended value for ModelSource is a uniform Resource Identifer (URI), such as: http://www.opm.gov/studies/

Optional

0 or 1

Non-null string

Statement

Statement is the subelement of Definition. It defines a single characteristic or component of the competency, such as the outcome criteria. See section Statement for more information.

Required

1 or more

Container

Category

Category is the subelement of Definition. It defines a category associated with this competency. Miller’s pyramid is one example of set of categories: knows, knows how, shows how, does.

Note: Organizational groupings of competencies should be defined in the competency map.

Required

1 or more

Non-null string

References

References is the subelement of Defintion. References contains subelements that define specific references to the literature related to this competency.See section References for more information.

Optional

0 or 1

Container

 

Example:

<code>

 

2.3     Statement

Statement defines a single characteristic or component of the competency. Components include the competency statement, outcome criteria, and assessment methods.

 

 

Statement Element Information

Element

Description

Required

Multiplicity

Datatype

Statement

Statement is the subelement of Definition. It defines a single characteristic or component of the competency, such as the outcome criteria.

Required

1 or more

Container

StatementID

StatementID is the subelement of Statement. It provides a unique label for this statement within the competency definition. See section IdentifierType for more information.

Optional

0 or 1

IdentifierType

StatementName

StatementName is the subelement of Statement. It provides a unique name for this statement within the competency definition. Valid values are Competency Statement, Outcome Criteria, Assessment Methods.

Required

1

Restricted

StatementText

StatementText is the subelement of Statement. It contains subelements that provide the text description of the competency statement described in StatementName in multiple languages. For example, if StatementName indicates Assessment Methods, StatementText could be “Demonstration of skills via OSCE recommended.”

See section LanguageString for more information.

Required

1

LanguageString

 

Example:

<code>

 

2.4     Metadata

Metadata defines the schema and version of the competency model used

 

 

Metadata Element Information

Element

Description

Required

Multiplicity

Datatype

Metadata

Metadata is the subelement of CompetencyDefinition. It contains subelements that define the schema and version of the competency model used.

Optional

0 or 1

Container

RCDSchema

RCDSchema is the subelement of Metadata. It indicates which schema defines and controls this competency definition. The default value is: http://ns.medbiq.org/ competencyframework/v1

Optional

1

Non-null string

RCDSchemaVersion

RCDSchemaVersion is the subelement of Metadata. It indicates which version of the schema in RCDSchema has been used for this competency definition.

Optional

1

Non-null string

 

Example:

<code>

 

3         CompetencyMap

 

To be completed.

4         Common Data Types

4.1     LanguageString

 

Many of the elements in Competency Framework use the LanguageString datatype. LanguageString provides a way to specify a value for an element in multiple languages. For example, document creators can specify a single Title for a framework in both French and English. This functionality is important for those implementing competency frameworks for a multilingual population.

 

Elements using the LanguageString datatype have the subelement of string, which is described in the following table.


Element

Description

Datatype

string

string is the subelement of any element using the LanguageString datatype. It provides a word or phrase in a human language. If the string element is repeated within a particular element, each value should be semantically equivalent, such as a translation or alternative description.

string has the following attribute:

language
language specifies the human language of the text string. Valid values are codes from the ISO-10646-1 standard. For example, en for English and fr for French.

string

 

In the following example, two titles are provided for the CANMeds framework, one in English, and one in French.

 

<Title>

<string language=”en”>The CanMEDS 2005 Physician Competency Framework</string>

<string language=”fr”>Le Cadre de Compétences CanMEDS 2005 Pour Les Médecins</string>

</Title>

4.2     IdentifierType

 

Many of the elements in Competency Framework use the IdentifierType datatype, which allows competency framework developers to indicate the catalog or source of the identifier along with the identifier. This two-part approach facilitates the exchange of competency frameworks across systems by preventing identifier duplication.

 

 

 

 

Elements using the IdentifierType have Catalog and Entry subelements, which are described in the table that follows.

 


IdentiferType Subelements

Element

Description

Required

Multiplicity

Datatype

Catalog

Catalog indicates the identification or cataloguing scheme for the entry. URIs may be used in many cases. In others, organizations may wish to use an internal cataloguing scheme.

Required

1

Non-null string

Entry

Entry is the value of the identifier within the cataloguing scheme specified by the Catalog element.

Required

1

Non-null string

 

 

The following example shows an identifier for a competency definition that uses a URI cataloging schema.

 

<Identifier>

<Catalog>URI</Catalog>

<Entry>http://www.medschool.edu/competencies/kp87t</Entry>

</Identifier>

 

The next example shows an identifier for a competency definition that uses a local cataloguing schema.

 

<Identifier>

<Catalog>Medschool University</Catalog>

<Entry>2005.10.87</Entry>

</Identifier>

 

 

 

 


 


Sample XML Document s

 

 

<to be completed>


References

 

To be completed