oship-dev team mailing list archive

[Eduardo César <xcesar@xxxxxxxxx>]

Hi all,

Tim, in the specfication of the ehr extract information model, some classes
do not have a super class discrimined. I had put those classes subclassing
"object", but I don't know if it is the best approach. Any tips?

Here is an example:
class ExtractEntityIdentifier(object):
    u"""
    Identifier for a single demographic entity or record thereof. Because
    identification is poorly standardised and also heavily dependent on
    existing systems, this class provides two possibilities for
identification:
    an id for the record, or an id for the demographic entity. These are not
    always 1:1 anyway, due to errors that occur in systems causing duplicate
    records for a given entity.
    """

    def __init__(self, entityid, recordid):
        self.entityid = entityid
        self.recordid = recordid


Also, on the Syncextract Package of the Ehr Extract IM wants a class of the
Message Package that is not there.
Perhaps should I change the message package? Or should I change the ehr
extract package? Some more tips? :)

Cheers
Eduardo