Difference between revisions of "Pharm Tech Minutes 2012.06.20"
m (→Participants) |
|||
Line 4: | Line 4: | ||
− | * | + | * |
− | * | + | * |
− | * | + | * |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== 14:00 - 14:15 Welcome == | == 14:00 - 14:15 Welcome == |
Revision as of 05:10, 20 June 2012
Day 2, Jun 20th, 2012, 14:00 - 18:00
Participants
14:00 - 14:15 Welcome
14:15 Medication catalog (e.g. Formulary)
- Status update
The version 0.3 of the Formulary white paper available : ftp://ftp.ihe.net/Pharmacy/yr3_2011-2012/Technical_Committee/Whitepapers/Formulary
15:00 Glossary work item
- Status update
- IHE/HL7 Pharmacy glossary spreadsheet:
https://docs.google.com/spreadsheet/ccc?key=0AmpTn7l3l1lfdFFQNFhzd0FqRUxaTUNneUZhTkk2YlE
16:00 -- Break --
16:10 Improvements in HMW for scope and error-fixing
- Approving CPs
CPs available on the FTP:
ftp://ftp.ihe.net/Pharmacy/TF_Maintenance-2012/CPs
- CP-PHARM-024 to CP-PHARM-029.
17:00 HMW Exceptional cases
- Approving CPs
17:30 Make CMPD better readable
1) CP-PHARM-023: New version 5 created
ftp://ftp.ihe.net/Pharmacy/TF_Maintenance-2012/CPs/Assigned/CP-PHARM-023v5.doc
New version : no changes but rather created because one of the changes has been taken out of the CP and has been relocated in a new CP. This was done for formal correctness only because the change was not only for “improving readability” but was rather an error in the profile.
2) CP-PHARM-030: New CP created
ftp://ftp.ihe.net/Pharmacy/TF_Maintenance-2012/CPs/Assigned/CP-PHARM-030.doc
This CP contains the one change, which formerly was placed within CP-PHARM-023 (see above).
3) CP-PHARM-031: New CP created
ftp://ftp.ihe.net/Pharmacy/TF_Maintenance-2012/CPs/Assigned/CP-PHARM-031.doc
This CP contains a new change! It relaxes the optionality of the transaction PHARM-1 for client-side actors (Pharmaceutical Advisers and Medication Dispensers) from “Required” to “Optional”. This is possible and consistent, because actually CMPD can also be operated without a “Community Pharmacy Manager” (although this is not the intention), so the optionality “required” was to strict.