(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Patient Administration Call
Meeting Information
| PA Work Group Conference Call
Minutes
GoToMeeting
Local numbers sent to list
Meeting Information
| PA Work Group Conference Call
Minutes
Gotomeeting - see pafm@lists.hl7.org
HL7 Conference Call phone number
|
Date: Friday, July 24, 2018
Time: 12:00 PM (US Pacific Time, GMT -7)
Quorum Met (Chair+2, Yes/No)? Yes
|
| Facilitator
|
Irma Jongeneel
|
Scribe
|
Irma Jongeneel
|
|
|
| Attendee
|
Name
|
Affiliation
|
| X
|
Irma Jongeneel
|
VzVz, NL
|
| X
|
Alex de Leon
|
Kaiser Permanente
|
| X
|
Riki Merrick
|
Vernetzt, LLC
|
| X
|
Lori Fourquet
|
e-HealthSign, LLC
|
| X
|
Genny Barkocy Luensman
|
CDC/NIOSH/RHD/SB
|
| X
|
Kathy Walsch
|
LabCorp
|
| X
|
Kathleen Connor
|
US
|
| X
|
Nick Radov
|
US
|
Agenda
Agenda Topics
Agenda
- v2
Supporting Documents
Minutes
1. ODH neg comments
- 47 Not Publishing thing, needs to be done manually, suggest to accept Lori/Riki: 5/0/2
2. PRT Neg comments
- 238: needs discussion (ARV related) Riki/Nick 6 0 1
- 239: seems reasonable, suggest to accept Riki/Nick 6 0 1
- 383: seems reasonable, suggest to accept (and check all other trigger events too for this text) Riki/Nick 7 0 0
3. ARV Neg comments
- 251, 252, 254, 255: Access restriction to what level? Riki to discuss with Kathy.
The discussion is weather the access restriction should allow to restrict to the segment level or the field or even component/subcomponent level. The datatype kind of forces it to be to the lowest level it seems. Could conformance profiles/implementation guide be used for systems to declare conformance to a certain level of access restriction? That way the definition and datatype can stay as is and on implementation level it is agreed which level of Access restriction is supported. I can see that this may be quite different for different realms anyway.
13.2.14.9 ARV-9 Access Restriction Message Location (ERL) nnnnn03514
Components: <Segment ID (ST)> ^ <Segment Sequence (NM)> ^ <Field Position (NM)> ^ <Field Repetition (NM)> ^ <Component Number (NM)> ^ <Sub-Component Number (NM)>
Definition: Identifies the location in a message related to the identified access restricted data. If multiple repetitions are present, the listed access restrictions apply to all listed places. Add text to ARV-9 to reflect that Realm, business and policy rules will determine to what level the restrictions need to be supported. And add some examples (action item Kathleen/Riki). Motion Riki/Nick: 6/1/0
- Editorial changes (not marked as changed and backwards comp): Suggest to accept as persuasive in block vote: Alex/Riki: 5/0/2
- 363
- 365
- 366
- 369
- 370
- 372
- 375
- 376
- 377
- 378
- 379
- 380
- 381
- 382
- 384
- 253
|
Next Meeting/Preliminary Agenda Items
- Next telecom meeting for v2: 01. August 2018
|
Navigation
Return to PA Main Page
© 2017 Health Level Seven® International. All rights reserved.
