![]() |
Page History
...
ID | Requirement | Source | Release |
---|---|---|---|
MOS-1 | The Model Service MUST support the abilities to record new model elements. |
| |
MOS-2 | The Model Service MUST support the abilities to record new assertions. |
| |
MOS-3 | The Model Service MUST support the abilities to record new rules. |
| |
MOS-4 | The Model Service SHOULD support the abilities to record queries. |
| |
MOS-10 | The Model Service MUST allow for the discovery of models based on querying model parts. |
| |
MOS-11 | The Model Service MAY support the federated discovery of models. |
| |
MOS-12 | The Model Service SHOULD allow the discovery of related model parts. |
| |
MOS-20 | The Model Service MUST support the comparison of model parts. |
| |
MOS-21 | The Model Service MUST support the harmonization of models through the comparison of model parts. |
| |
MOS-30 | The Model Service SHOULD support the merging of different parts of different models. |
| |
MOS-40 | The Model Service MAY support the graphical visualization of models. |
| |
MOS-50 | The Model Service MUST support the versioning of models. |
| |
MOS-60 | The Model Service MUST allow the retiring of models. |
| |
MOS-70 | The Model Service MUST allow the of updating of parts of a model. |
| |
MOS-80 | The Model Service MUST allow the deletion/unregistering of models. |
| |
MOS-90 | The Model Service SHOULD support the transformation of models. |
| |
MOS-100 | The Model Service SHOULD support the validation of models. |
| |
MOS-110 | The Model Service MUST support the reuse of model parts. |
| |
MOS-111 | The Model Service MUST support the entire reuse of direct copies of model parts. |
| |
MOS-120 | The Model Service MUST support the extension of model parts. |
| |
MOS-121 | The Model Service MUST allow the extension of classes. |
| |
MOS-122 | The Model Service MUST allow the extensions of model part relationships. |
| |
MOS-123 | The Model Service SHOULD allow the extension of attribute value lists. |
| |
MOS-130 | The Model Service SHOULD support the constraining of model parts. |
| |
MOS-131 | The Model Service SHOULD allow for classes to be subsetted. |
| |
MOS-132 | The Model Service SHOULD allow for attribute value lists to be subsetted. |
| |
MOS-140 | The Model Service MUST support the discovery of services related by model similarities. |
| |
MOS-150 | The Model Service SHOULD support the discovery of related documentation. |
|
Metadata Services
Some basic description of metadata services.
ID | Requirement | Source | Release |
---|---|---|---|
MDS-1 | The Metadata Service MUST support the notion of data elements. |
| |
MDS-2 | The Metadata Service MUST allow the recording of data elements. |
| |
MDS-3 | The Metadata Service MUST allow new data element assertions to be made. |
| |
MDS-4 | The Metadata Service MUST allow for data elements to be updated. |
| |
MDS-5 | The Metadata Service MUST allow for data elements to be versioned. |
| |
MDS-6 | The Metadata Service SHOULD allow for data element business rules to be validated. |
| |
MDS-7 | The Metadata Service MUST allow for data elements to be retired. |
| |
MDS-8 | The Metadata Service MUST allow for data elements to be deleted/rolled back. |
| |
MDS-9 | The Metadata Service MUST support the discovery of reusable data element content. |
| |
MDS-10 | The Metadata Service SHOULD support the notion of data element usage information. |
| |
MDS-11 | The Metadata Service MUST support metadata to be queried by data element. |
| |
MDS-12 | The Metadata Service SHOULD support metadata to be queried by data element in a federated manner. |
| |
MDS-13 | The Metadata Service MUST support the comparison of data elements |
| |
MDS-14 | The Metadata Service SHOULD support the creation of a new data element from an existing data element. |
| |
MDS-15 | The Metadata Service MUST support the discovery of related models by data element. |
| |
MDS-16 | The Metadata Service SHOULD support the discover related metadata items by data element. |
| |
MDS-17 | The Metadata Service SHOULD support the discovery of related services by data element. |
| |
MDS-18 | The Metadata Service SHOULD support the discovery of related data element rules. |
| |
MDS-19 | The Metadata Service SHOULD support the discovery of forms related by data element. |
| |
MDS-101 | Value Domain |
| |
MDS-102 | Record (no rules) |
|
|
MDS-103 | New assertions |
|
|
MDS-104 | Update |
|
|
MDS-105 | Version |
|
|
MDS-106 | Validate business rules |
|
|
MDS-107 | Retire |
|
|
MDS-108 | Delete/rollback |
|
|
MDS-109 | Discover reusable content |
|
|
MDS-110 | Usage information |
|
|
MDS-111 | Search/query |
|
|
MDS-112 | Federated search/query |
|
|
MDS-113 | Compare |
|
|
MDS-114 | Create new from existing |
|
|
MDS-115 | Discover related models |
|
|
MDS-116 | Discover related metadata items |
|
|
MDS-117 | Discover related services |
|
|
MDS-118 | Discover related rules |
|
|
MDS-119 | Discover related forms |
|
|
MDS-120 | Create subset/constrain |
|
|
MDS-120 | Extend (create new from existing) |
|
|
MDS-120 | Semantic transformations (Explicitly based on mapping e.g. to the same Value Meaning) |
| |
MDS-120 | Syntactic transformations ( Source representation to Target representation) |
| |
MDS-201 | Data Element Concept |
| |
MDS-202 | Record (no rules) |
| |
MDS-203 | New assertions |
|
|
MDS-204 | Update |
|
|
MDS-205 | Version |
|
|
MDS-206 | Validate business rules |
|
|
MDS-207 | Retire |
|
|
MDS-208 | Delete/rollback |
|
|
MDS-209 | Discover reusable content |
|
|
MDS-210 | Usage information |
|
|
MDS-211 | Search/query |
|
|
MDS-212 | Federated search/query |
|
|
MDS-213 | Compare |
|
|
MDS-214 | Create new from existing |
|
|
MDS-215 | Discover related models |
|
|
MDS-216 | Discover related metadata items |
|
|
MDS-217 | Discover related services |
|
|
MDS-218 | Discover related rules |
|
|
MDS-219 | Discover related forms |
|
|
MDS-220 | Discover related data elements |
| |
MDS-222 | Discover related value sets |
| |
MDS-223 | Create data element from existing data element concept and value domain |
| |
MDS-224 | Create new data element concept from existing data element concept |
|
Registry-Registry Service
ID | Requirement | Source | Release |
---|---|---|---|
RRS-1 | Import Content |
| |
RRS-10 | Export Content |
| |
RRS-20 | Update Content |
| |
RRS-30 | Search |
| |
RRS-40 | Submit Content |
| |
RRS-50 | Register Content |
| |
RRS-60 | Update Registration |
|
General Service
ID | Requirement | Source | Release |
---|---|---|---|
GEN-1 | Annotate with concepts |
| |
GEN-10 | Subscribe to changes |
| |
GEN-20 | Reuse (classify/categorize) |
|
Metadata Registry Tools
ID | Requirement | Source | Release |
---|---|---|---|
MRT-1 | Clinician friendly browser |
| |
MRT-10 | Information specialist browser |
| |
MRT-20 | Customizable browser |
| |
MRT-30 | Portal that integrates tools |
| |
MRT-40 | Workflow management to support ECCF artifact creation |
| |
MRT-50 | Interface of browser/editing models and metadata with modeling tools |
|
Non-functional Requirements
...