Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Attendees

X

Riki Merrick

-

Amy Liu

-

Susan Downer

X

Grace Oguntebi

X

Amanda Payne

X

Phylis Stromile

-

Natalie Raketich

Gretl Glick

X

Jamie Patterson

Laura Carlton

X

Emily Augustini

Kandis Brown

Pam White

Dave Sanderson

-

Tina Hardin

X

Benson Chang

X

Jerry Sable

X

Doug York

X

Andy Shotwell

Discussion topics

Item

Presenter

Notes

Agenda Review

 

 

OOO

Vocab Team Calendar

Holiday Coverage in December

AIMS+ Topics

Benson/Doug

 No topics

Pulsecheck/Round Robin

All

Vocab Team Resource Dashboard

Clinical Architecture

Jamie / Riki

Feedback on the Adaptive Workflow presentation?

How are we using Clinical Architecture?

  • First step will be to manage PLT and PLR codes

    • also allow CDC folks access to create their own

    • will create a separate workflow to support SNOMED CT submission workflow

      • provide background information for submission (rationale / literature background)

    • will also ensure that the SCT terms are updated (Clinical Architecture will do that)

  • in the future will do the same for LOINC
    for PLT

    • assign Order/Obs/both - this will be required going forward (but have to adjust the existing ones)

    • then we can use this to create the valuesets for each program for the respective code combination tables as well as value sets

    • so we can export these directly from the tool - Clinical Architecture is working on translating the encoding guidelines

  • may be in the future offer this to PHLs for direct access - and maybe their local mappings, too

  • for ELR TA mapping support

  • for ETOR mapping support for PHLs (with or without use of the centralized solution)

We will make the next show and tell about this in more detail on Nov 10

OID Management

Riki

New place on smartsheet: https://app.smartsheet.com/folders/7CQ3243xrMXVFfj34FvVCrW7R4fCgg3jr2rMw4w1

  • Organization OIDs =

    • supports creation of APHL assigned OIDS AND documentation of collected OIDs

  • System OIDs =

    • supports creation of APHL assigned OIDS AND documentation of collected OIDs

    • Currently used to build an OID report that can be shared =

      • combines system and organization OIDS, BUT

        • only for the organizations that host the system, not all that use it - do we need that?

Problem:

How to give folks all organizaiton organization OIDs (regardless of system they use) - probably needs to be a report on the organization OIDs sheet, so a separate report

Could both be shared on 1 confluence page?

Could we build a search function by organization name / system name / CLIA number / OID?

Confluence UsePhylis

NEXT WEEK

Show and Tell?

 

SOP Worthy Topics

Next Show and Tell will be November 10, 2021 - so sign up!!decided to talk about Clinical Arcitecture tool use plan - Jamie and Riki to create

  •  Sign up to be a presenter for an SOP worthy topic, if you are the one most familiar with the topic, estimate time it will take, and pick a date you might want to present on
  •  Review the list of SOP worthy topics and add more (what do you think folks need to know, if they are taking over your work, or what skill do you know one of us has, that you would like to learn more about)

Succession Planning

 

Review every month or so:

https://aphlinformatics.atlassian.net/wiki/download/attachments/915865620/SuccessionPlan.xlsx?api=v2

Issue Review (Time Permitting)

 

Issues List from Sharepoint

  •  Review each issue to decide if it is still a valid issue that needs work.
  •  Migrate list of Smartsheet or Jira

...