Metadata Class Model
Date | Activity | Status Update(s) | Owner(s) |
|---|---|---|---|
2020/09/03 | Class Model for Metamodel |  | |
2020/10/05 | Updated class model |  | |
2020/11/04 | Updated UML Diagram |  |
Metadata Set
Date | Activity | Status Update(s) | Owner(s) |
|---|---|---|---|
2020/04/20 | Version 0.2 of Metadata based on telecon revisions | ||
2020/04/21 | Added Metadata revisions to spreadsheet | ||
2020/04/23 | Updated Spreadsheet based on group call; Revised metamodel | ||
2020/04/27 | Updated Spreadsheet based on group call | ||
2020/04/29 | Revised metamodel graphic source and PDF. |
| |
2020/04/29 | Updated Spreadsheet based on group call; revised metamodel graphic source and PDF. | ||
2020/04/30 | Updated Spreadsheet based on call | ||
2020/05/01 | Updated spreadsheet with Jane’s contribution and comments | ||
2020/05/04 | Updated spreadsheet from call | ||
2020/05/06 | Updated spreadsheet from call | ||
2020/05/07 | Updated Spreadsheet with Laura’s additions | ||
2020/05/08 | Revised metamodel graphic source and PDF | ||
2020/05/18 | Metamodel Review 0.6 | ||
2020/06/03 | Metamodel Revision | ||
2020/06/19 | Metamodel Revision | ||
2020/07/20 | Outbrief of Asset Classification Exercise Review/Revise Metamodel Discuss Data Entry Approach | Call focused on outbrief of the experiential learning from the Tiger Team doing asset mapping. In brief, the recommendation was to limit the depth of the “branches” of the meta model, flattening the overall field structure to simplify classification. Revisions to the metamodel were done, with corresponding updates to the classification document. While not all revisions have been cascaded throughout the deliverables, current-state edits are included here. Additionally the group discussed approaches for data entry tooling in support of asset classification and lifecycle management. | |
2020/07/22 | From the UX call, we have been given a homework assignment: What items are filter criteria? How do facets interrelate? Do any tie specifically to personas? Need to document this for UX team and development How do we deal with versions of the same asset from a user experience perspective? | ||
2020/08/03 | Joint discussion with AHRQ/ACTS regarding their COVID Collaboration Hub. Discussed how to extend Navigator metamodel to include elements to support these needs. Draft version posted here. Discussion is ongoing. Anticipate completion of integrative work by end of August. |
Model Comments
Comment/suggestion | Rationale (if necessary) | Submitter | Adjudication |
|---|---|---|---|
Consider looking at Dublin Core metadata standard | We’re a standards organization… | Jane Shellum |
|
Consider changing “area of interest” to “subject” | “subject” may be a more accurate description of what the metadata is capturing. And this is one element from Dublin Core | Jane Shellum |
|
Consider breaking down Area of interest into groups. E.g Care Setting (inpatient, outpatient, emergency, long-term care, home, telemedicine), Special Populations (children, pregnancy, immunocompromised, etc), Comorbidities (HTN, Asthma, etc), Complications (Cardiac, Neuro, Respiratory) Care Process (screening, diagnosis, treatment, prevention, follow-up) | This will allow for a better search/browse experience (faceted search) and allows for an asset to be characterized along multiple axes. | Jane Shellum |
|
Are resource management and logistics the same? |
| Jane Shellum |
|