This wiki has undergone a migration to Confluence found Here
Difference between revisions of "2015-08-03 Rx Conf Call"
Jump to navigation
Jump to search
Marla albitz (talk | contribs) (Created page with "{| style="width:100%; background-color:transparent;" |- | style="vertical-align:top; width:50%" | <!-- LEFT COLUMN --> __TOC__ | style="vertical-align:top; width:35%" | <!--...") |
Marla albitz (talk | contribs) |
||
(27 intermediate revisions by the same user not shown) | |||
Line 21: | Line 21: | ||
=Attendees= | =Attendees= | ||
− | * | + | * John Hatem (Chair) |
− | * | + | * Marla Albitz (Scribe) |
+ | * Melva Peters | ||
* Scott Robertson | * Scott Robertson | ||
− | * | + | * Rik Smithies |
− | + | * Jose Costa Teixeira | |
− | |||
− | |||
− | |||
− | * Jose Costa | ||
− | |||
==FHIR Ballot Reconciliation== | ==FHIR Ballot Reconciliation== | ||
+ | * Medication Examples discussion | ||
+ | **John led group through various scenarios with the goal to answer questions to inform example creation. | ||
+ | |||
* Modelling changes - Discussion | * Modelling changes - Discussion | ||
− | |||
* Medication.Coding | * Medication.Coding | ||
− | + | ** Completed Action: Tom de Jong will author explanation for medication.coding for group to vote for inclusion. | |
+ | Action: Marla to ask Tom to finalize the wording based on responses to allow group to vote at next meeting. | ||
− | * Medication Name - is name attribute needed when the code attribute has a display text? | + | * Medication Name - is name attribute needed when the code attribute has a display text? Tom circulated this question to the group. |
− | + | ** Completed Action: Tom de Jong to circulate a proposal that will suggest explanation for use of medication name attribute in addition to Medication codeable code and display text. | |
+ | Action: Group to draw conclusions from email exchanges, discuss and vote at next meeting. There is debate as to whether medication name should be removed or not. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
* Group reviewed and discussed proposed status' for medication administration. | * Group reviewed and discussed proposed status' for medication administration. | ||
* Will continue this discussion to next week's meeting. | * Will continue this discussion to next week's meeting. | ||
− | Action: John to send out status' changes to allow for a vote next week. | + | Action: 8/3 still outstanding - John to send out status' changes to allow for a vote next week on 8/3. |
==ListServ== | ==ListServ== | ||
Line 56: | Line 51: | ||
** Need to determine how FHIR versioning is handled to help understand how a prescription is updated over time - Rik explained on the call that FHIR provides the ability to have an old version and a new version of the resource, but whether the resources persist over time as it changes, it a non-FHIR issue and is handled by the systems and data stores exchanging resources. | ** Need to determine how FHIR versioning is handled to help understand how a prescription is updated over time - Rik explained on the call that FHIR provides the ability to have an old version and a new version of the resource, but whether the resources persist over time as it changes, it a non-FHIR issue and is handled by the systems and data stores exchanging resources. | ||
− | Action: | + | Action: 8/3 - still outstanding - John to respond to Michelle to get more information about the types of resource updates she is referring to for this issue. |
− | * | + | * Medication.code.coding from Michelle Miller - see Medication.code actions in FHIR section for details. |
− | * | + | |
+ | * Medication frequency question from Christina - John forwarded to Tom to ask him to answer this question. | ||
+ | Action: Scott will look at our hot topics list to see if we have this issue listed. | ||
==NCPDP Implementation Guidance - Ballot Reconciliation== | ==NCPDP Implementation Guidance - Ballot Reconciliation== | ||
Line 65: | Line 62: | ||
Completed Action Item: Scott will post ballot reconciliation spreadsheet | Completed Action Item: Scott will post ballot reconciliation spreadsheet | ||
Completed Action item: Scott to send a note to Karen re: publication Update - Scott sending email 7/6, today | Completed Action item: Scott to send a note to Karen re: publication Update - Scott sending email 7/6, today | ||
− | Action: can close project once completed - still needs to be done, will be done once scott confirms that Karen responded, close to being done | + | Action: 8/3 update - Karen has not responded, Scott will try calling Karen **** can close project once completed - still needs to be done, will be done once scott confirms that Karen responded, close to being done |
==ARB Project== | ==ARB Project== | ||
− | * update from meeting from John | + | * update from meeting from John - last week's meeting did not include Pharmacy items. |
+ | * Link to ARB meeting minutes: | ||
+ | https://docs.google.com/document/d/14RFfP4ehHz_WOwS0G6VH0ibE1aDjuUWXC4flDKcfp4w/edit | ||
==Next meeting== | ==Next meeting== | ||
* August 10, 2015 | * August 10, 2015 | ||
+ | |||
+ | * Agenda | ||
+ | ** Final review of medication status's and vote | ||
+ | ** Vote on removal of medication.name | ||
+ | ** Vote on wording of medication.code explanation | ||
+ | |||
+ | Definition: A code (or set of codes) that specify this medication, or a textual description if no code is available. Usage note: This could be a standard medication code such as a code from RxNorm, SNOMED CT, IDMP etc. It could also be a national or local formulary code, optionally with translations to other code systems. | ||
+ | |||
+ | Comments: Depending on the context of use, the code that was actually selected by the user (prescriber, dispenser, etc.) should be marked as “primary”. Other codes can only be literal translations to alternative code systems, or codes at a lower level of granularity (e.g. a generic code for a vendor-specific primary one). |
Latest revision as of 18:46, 7 August 2015
Related Links |
Attendees
- John Hatem (Chair)
- Marla Albitz (Scribe)
- Melva Peters
- Scott Robertson
- Rik Smithies
- Jose Costa Teixeira
FHIR Ballot Reconciliation
- Medication Examples discussion
- John led group through various scenarios with the goal to answer questions to inform example creation.
- Modelling changes - Discussion
- Medication.Coding
- Completed Action: Tom de Jong will author explanation for medication.coding for group to vote for inclusion.
Action: Marla to ask Tom to finalize the wording based on responses to allow group to vote at next meeting.
- Medication Name - is name attribute needed when the code attribute has a display text? Tom circulated this question to the group.
- Completed Action: Tom de Jong to circulate a proposal that will suggest explanation for use of medication name attribute in addition to Medication codeable code and display text.
Action: Group to draw conclusions from email exchanges, discuss and vote at next meeting. There is debate as to whether medication name should be removed or not.
- Group reviewed and discussed proposed status' for medication administration.
- Will continue this discussion to next week's meeting.
Action: 8/3 still outstanding - John to send out status' changes to allow for a vote next week on 8/3.
ListServ
- New request (7/20): Modify medication prescription from Michelle Miller
- Need to determine how FHIR versioning is handled to help understand how a prescription is updated over time - Rik explained on the call that FHIR provides the ability to have an old version and a new version of the resource, but whether the resources persist over time as it changes, it a non-FHIR issue and is handled by the systems and data stores exchanging resources.
Action: 8/3 - still outstanding - John to respond to Michelle to get more information about the types of resource updates she is referring to for this issue.
- Medication.code.coding from Michelle Miller - see Medication.code actions in FHIR section for details.
- Medication frequency question from Christina - John forwarded to Tom to ask him to answer this question.
Action: Scott will look at our hot topics list to see if we have this issue listed.
NCPDP Implementation Guidance - Ballot Reconciliation
- what is the status of this? All comments resolutions will be accepted per the ballot reconciliation spreadsheet. Moved John H, Seconded Jean Duteau Vote:5:0:0
Completed Action Item: Scott will post ballot reconciliation spreadsheet Completed Action item: Scott to send a note to Karen re: publication Update - Scott sending email 7/6, today Action: 8/3 update - Karen has not responded, Scott will try calling Karen **** can close project once completed - still needs to be done, will be done once scott confirms that Karen responded, close to being done
ARB Project
- update from meeting from John - last week's meeting did not include Pharmacy items.
- Link to ARB meeting minutes:
https://docs.google.com/document/d/14RFfP4ehHz_WOwS0G6VH0ibE1aDjuUWXC4flDKcfp4w/edit
Next meeting
- August 10, 2015
- Agenda
- Final review of medication status's and vote
- Vote on removal of medication.name
- Vote on wording of medication.code explanation
Definition: A code (or set of codes) that specify this medication, or a textual description if no code is available. Usage note: This could be a standard medication code such as a code from RxNorm, SNOMED CT, IDMP etc. It could also be a national or local formulary code, optionally with translations to other code systems.
Comments: Depending on the context of use, the code that was actually selected by the user (prescriber, dispenser, etc.) should be marked as “primary”. Other codes can only be literal translations to alternative code systems, or codes at a lower level of granularity (e.g. a generic code for a vendor-specific primary one).