Unknown macro: {font-family} /*StyleDefinitions*/p.MsoNormal,li.MsoNormal,div.MsoNormalUnknown macro: {mso-style-unhide} .MsoChpDefaultbl"><!-- /* Font Definitions */ @font-face Unknown macro: {font-family} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal Unknown macro: {mso-style-unhide} .MsoChpDefault Unknown macro: {mso-style-type} @page Section1 Unknown macro: {size} div.Section1 Unknown macro: {page} -->Creating datatype mapping
Use Case Number |
UMLSD1 |
Brief Description |
One persons object is another person's attribute". Depending on ones world view, a real life entity can be modeled in UML as Object, Attribute or value set. In caBIG models now, some model Race (and Ethnicity) as an Object while others model Race (and Etnicty ) as an attribute. This is problematic, because Race data that is modeled differently cannot be "seamlessly integrated" on caGrid (there needs to be a transform). Unknown macro: {font-family}
@font-face Unknown macro: {font-family}
/* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal Unknown macro: {mso-style-unhide}
.MsoChpDefault Unknown macro: {mso-style-type}
@page Section1 Unknown macro: {size}
div.Section1 Unknown macro: {page}
--> |
Actor(s) for this particular use case |
<!-- /* Font Definitions */ @font-face Unknown macro: {font-family}
/* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal Unknown macro: {mso-style-unhide}
.MsoChpDefault Unknown macro: {mso-style-type}
@page Section1 Unknown macro: {size}
div.Section1 Unknown macro: {page}
-DDataData Curators |
Pre-condition |
<!-- /* Font Definitions */ @font-face Unknown macro: {font-family}
/* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal Unknown macro: {mso-style-unhide}
.MsoChpDefault Unknown macro: {mso-style-type}
@page Section1 Unknown macro: {size}
div.Section1 Unknown macro: {page}
-->The various data formats along with their pluses and minuses are known |
Post condition |
<!-- /* Font Definitions */ @font-face Unknown macro: {font-family}
/* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal Unknown macro: {mso-style-unhide}
.MsoChpDefault Unknown macro: {mso-style-type}
@page Section1 Unknown macro: {size}
div.Section1 Unknown macro: {page}
-->A direct mapping is created between an agreed upon, standard format and any other format used in the healthcare settings |
Steps to take |
<!-- /* Font Definitions */ @font-face Unknown macro: {font-family}
/* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal Unknown macro: {mso-style-unhide}
.MsoChpDefault Unknown macro: {mso-style-type}
@page Section1 Unknown macro: {size}
div.Section1 Unknown macro: {page}
-->1.Curators identify various datatype formats (A, B, C and X ) that are used to represent data in various tools |
Alternate Flow |
None |
Priority |
Medium |
Associated Links |
|
Fit criterion/Acceptance Criterion |
<!-- /* Font Definitions */ @font-face Unknown macro: {font-family}
/* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal Unknown macro: {mso-style-unhide}
.MsoChpDefault Unknown macro: {mso-style-type}
@page Section1 Unknown macro: {size}
div.Section1 Unknown macro: {page}
-->A granular mapping is created between an agreed upon standard format and any other format used in the healthcare settings |
Use Case - Descriptive Name
Use Case Number |
n.n |
Brief Description |
|
Actor(s) for this particular use case |
|
Pre-condition |
|
Post condition |
|
Steps to take |
1. |
Alternate Flow |
|
Priority |
|
Associated Links |
|
Fit criterion/Acceptance Criterion |
|
Use Case - Descriptive Name
Use Case Number |
n.n |
Brief Description |
|
Actor(s) for this particular use case |
|
Pre-condition |
|
Post condition |
|
Steps to take |
1. |
Alternate Flow |
|
Priority |
|
Associated Links |
|
Fit criterion/Acceptance Criterion |
1. |
Use Case - Descriptive Name
Use Case Number |
n.n |
Brief Description |
|
Actor(s) for this particular use case |
|
Pre-condition |
|
Post condition |
|
Steps to take |
1. |
Alternate Flow |
|
Priority |
|
Associated Links |
|
Fit criterion/Acceptance Criterion |
|
Use Case - Descriptive Name
Use Case Number |
n.n |
Brief Description |
|
Actor(s) for this particular use case |
|
Pre-condition |
|
Post condition |
|
Steps to take |
1. |
Alternate Flow |
|
Priority |
|
Associated Links |
|
Fit criterion/Acceptance Criterion |
|