Person - relationship

Question

In our application, you can set the relationship for that person (used in EmergencyContact). For example, father, daughtor...

 

Is there such a field that I can use or I'll have to extand the Person class?

Answer 1

I took a look around, and didn't see anything that would work for you, so for now, you would probably have to store it in an extension.

 

It seems like having "relationship" as a member of that person class would be useful for other people, so I'd appreciate it if you'd make a data type request.

Answer 2

thanks, Eric. I've submit the request.

 

Answer 3

 

I saw the request come in yesterday, and we talked it over a bit, and it seems reasonable, but we'll want to have some further discussions.

 

You'll be able to find more information about it as it progresses at:

 

http://blogs.msdn.com/healthvaultdatatypes/

 

We have a bunch of data type stuff we're working on now, so I can't give you a good idea of when it will show up. For now, putting the data in extensions is probably the best bet, though it's not preferable to deploy in that state.

Answer 4

thanks for the info, Eric. I'll check on if once a while. I'll use the extension as for now.

Answer 5

Hello there,

 

Just a quick post to know what the status of this new relationship property being available wihtin the "Person" item type is ?

 

We also need this to be in our application but I'd rather not use type extension if the the update is coming soon.

 

I tried checking progresses at http://blogs.msdn.com/healthvaultdatatypes/ , but couldn't find anything relevant.

 

In fact I was also wondering if instead of having new "relationship"  property, you could simply add new vocabulary items in the person-types vocabulary ?

 

Thanks in advance for your reply.

 

-Joscelin

Guide Productions

www.guideproductions.com

Answer 6

We spent a little time a while back looking at adding relationship to Person, but because of how it is used, it turns out to be a fairly intrusive change to make at this time. We have some new work that we're doing now that should make such changes less intrusive in the near future. There's more information on the work in the versioning post I put up on the data types blog a day or so ago.

 

So, I guess that's a short way of saying that we're going to be in a holding pattern for a short period on adding relationship.

 

As for PersonType, that's an interesting question. I think our intention was to code that only using person-types, but it would be possible to code it with personal-relationship as well. In other words, to code my brother as an emergency contact, I'd use the following in PersonType

 

person.PersonType = new CodableValue("Emergency Contact (Brother)");

person.PersonType.Add(new CodedValue("1", "person-types");

person.PersonType.Add(new CodedValue("Bro", "personal-relationship");

 

I discussed that with Tim just now, and we think that's a good approach until we get relationship as a separate member of the type, and it has the advantage that you can do it today.

 

We've been doing some thinking about how to better communicate this kind of information to our partners. I don't think our raw notes are going to be useful, and while I'm open to spending more time writing about what we're doing, any time that I spend doing that is time that I'm not spending doing the actual design work. On the other hand, we're limited in how much of the design work we can do in a day because my brain gets tired after a while. If you have thoughts on what level of information you need, I'd like to hear them.