Versions Compared

Old Version 46

changes.mady.by.user Unknown User (jeroen.brackez@imec.be)

Saved on

compared with

New Version 47

changes.mady.by.user Unknown User (jeroen.brackez@imec.be)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TransactionElementMeaningStore for later use?Extra information
MSid

S="ID-KmehrKMEHR"

This is a unique Kmehr-identifier for the transaction within the transactionset.

NO

S="LOCAL" SL="vitalinkuri"

This is the unique Vitalink-identifier for the MS transaction.

YESThis is the same value as the Vitalink-identier retrieved with getTransactionList.
MSE/TSid

S="ID-KmehrKMEHR"

This is a unique Kmehr-identifier for the transaction within the transactionset.

NOAlthough storage is not needed for the web service manipulation flow, it is off course needed to know the link between TS transactions and the MSE transactions they poin to.YES

S="LOCAL" SL="vitalinkuri"

This is the unique Vitalink-identifier for the MSE transaction.

YES

...

ElementMeaningExtra information
authorThe author of the manipulation of the transaction set.It is good practice to provide the author information of the user of the application. However, the Vitalink gateway will reproduce generate this infirmation information based on the used session certificates.

iscomplete

This is not used in the Vitalink business flow.It is good practice to hard code this to "true".

isvalidated

This is not used in the Vitalink business flow.It is good practice to hard code this to "true".
versionThe version of the medication scheme on which this manipulation is based.

An application must pass here the value that was earlier read in the reading sequence.

The are several ways to retrieve the correct input value:

  1. The value of the element <version> in the element <latestupdate> for the transaction "medicationscheme" in the GetLatestUpdateResponse

    Note

    For Vitalink:

    GetLatestUpdateResponse returns error 489+406 if no Vitalink transactions at all were ever created.

    GetLatestUpdateResponse returns error 489+400 if only the medication scheme has never been created yet.


  2. The value of the element <version> in the transaction MS in the latest GetTransactionSetResponse

    Note

    For Vitalink, GetTransactionSetResponse returns no version if the medication scheme exists, but is empty.


...

MSE/TS transaction

Read a MSE/TS transaction

Reading the MSE/TS transactions means parsing the correspondent transaction elements in the getTransactionSetResponse. 

Create a MSE/TS transaction

An MSE/TS transaction needs to be composed, compliant to the structure described in Medicationscheme Kmehr Structure, where the following elements have a specific meaning:

ElementMeaningExtra information
id S="ID-KMEHR"

A unique Kmehr-identifier that distinguishes this transaction from all others.

This does not need to be the same value from the orginally read one. However make sure the relations between TS and MSE transactions are not broken.
id S="LOCAL" SL="vitalinkuri"

This should not be present!

Absence of this id means for Vitalink that this is a newly created transaction.
dateDate of creationTypically, the creating application should choose "today".
timeTime of creationTypically, the creating application should choose "now".
authorThe author of the manipulation of the transaction set.It is good practice to provide the author information of the user of the application. However, the Vitalink gateway will generate this information based on the used session certificates.

iscomplete

This is not used in the Vitalink business flow.It is good practice to hard code this to "true".

isvalidated

This is not used in the Vitalink business flow.It is good practice to hard code this to "true".

Here an example of a created MS transaction:

Code Block
languagexml
titleExample
linenumberstrue
<transaction>
	<id S="ID-KMEHR" SV="1.0">6</id>
	<cd S="CD-TRANSACTION" SV="1.11">medicationschemeelement</cd>
	<date>2018-02-09</date>
	<time>10:21:13.603+01:00</time>
	<author>
		...
	</author>
	<iscomplete>true</iscomplete>
	<isvalidated>true</isvalidated>
	...
</transaction>

Update a MSE/TS transaction

Delete a MSE/TS transaction

...

An earlier MSE/TS transaction needs to be adapted, compliant to the structure described in Medicationscheme Kmehr Structure, where the following elements have a specific meaning:

ElementMeaningExtra information
id S="ID-KMEHR"

A unique Kmehr-identifier that distinguishes this transaction from all others.

This does not need to be the same value from the orginally read one. However make sure the relations between TS and MSE transactions are not broken.
id S="LOCAL" SL="vitalinkuri"

This should not be present!

Absence of this id means for Vitalink that this is a newly created transaction.
dateDate of creation

Typically, the creating application should choose "today".

timeTime of creation

Typically, the creating application should choose "now".


authorThe author of the manipulation of the transaction set.It is good practice to provide the author information of the user of the application. However, the Vitalink gateway will generate this information based on the used session certificates.

iscomplete

This is not used in the Vitalink business flow.It is good practice to hard code this to "true".

isvalidated

This is not used in the Vitalink business flow.It is good practice to hard code this to "true".

Here an example of an updated MS transaction:

Code Block
languagexml
titleExample
linenumberstrue
<transaction>
	<id S="ID-KMEHR" SV="1.0">6</id>
	<cd S="CD-TRANSACTION" SV="1.11">medicationschemeelement</cd>
	<date>2018-02-09</date>
	<time>10:21:13.603+01:00</time>
	<author>
		...
	</author>
	<iscomplete>true</iscomplete>
	<isvalidated>true</isvalidated>
	...
</transaction>

Delete a MSE/TS transaction

This can be achieved by not adding the transaction (that needs to be deleted)in the <kmehrmessage> of the putTransactionSetRequest.  


----------------------



A transaction MS must be composed.

...