We explore selective viewing of items distinct from selective behavior of pages, as with cryptographic signatures, and distinct from whole site visibility as with login to view.
In our CORA – Technical Setup Discussion today we suggested that we "play act" the way our intended users would make and share pages.
"I'm thinking of writing a PrivateHtml plugin which would be much like the existing Html plugin except that the contents (words, data, tables, svgs, etc) would only be visible to readers with specific relationships to the author. This is for the purpose of supporting a persona based "design fiction" where we would explore possibilities, including mechanisms for an author to identify the indivituals who are in each specific relationship called out by the private information."
Baby Maybe Urinalysis
Consider this report fabricated by Baby Maybe. site 
We can mockup this as an HTML table were we can experiment with styling and role-based access control. Ultimately this would be a data-aware resource configured to meet medical requirements.
| Color | Yellow |
| pH | 5.3 |
| Glucose | Negative, mg/dL |
| Protein | Negative, mg/dL |
| Blood | Negative |
| Red blood cells | 0 - 2 #/hpf |
| White blood cells | 0 - 5 #/hpf |
| hCG, urine | 10,493 mIU/ml (Pos) |
With this test case we now consider item annotations and their semantic properties.
Role-Based Item Access -- how we will protect items.
Qualifying a Viewer in a Role -- how we enable readers.
Contrast with Shared Care Plan privacy summary. image