1.1   DiagnosisWS – Diagnosis

Version: 2.1.17180

 

Web Service with methods to handle main and subdiagnosis for a patient’s contact.

 

The DiagnosisWS Web Service contains these methods:

The Web Service reference is: DiagnosisWS.asmx

Open in a Web Browser for more detailed information about each method.  The Web Service's WSDL, SOAP request and response is described.

 

For more detailed information as the Web Service's WSDL, SOAP request and response see:

https://linkws.service.tieto.com/PasLinkWS/DiagnosisWS/DiagnosisWS.asmx

 

1.1.1   GetContactDiagnosis

Applicable systems for method:

INFOMEDIX

HIS90

 

 

 

 

 

 

Description:

Gets main- and sub-diagnosis for a given contact.

 

Syntax:

ContactDiagnosis = GetContactDiagnosis(PatientId, ContactId, TypeOfCare)

 

Parameter in

Type

Length byte

Description – Data format – Valid data

PatientId

Number

4 byte

Internal patient id. Format N(9).

Required. For HIS90 although required the patientId is not used and replaced by PatientId from ContactId

ContactId

String

N/A

Dynamic

Contact's id in the HIS. Format N(9)

Required.

In His90 ContactId = PatientId|SourceOfServ|SerialNoMeca|SerialNoStay.

To get this id, use the Web Service ContactWS, method GetPatientContacts.

 

Returned parameter

Type

Length Byte

Description – Comments

ContactDiagnosis

 

N/A

Dynamic

Contact diagnosis class according to XML schema ContactDiagnosis.xsd.

 

Schema for ContactDiagnosis:  Diagnosis.xsd

Schema documentation for ContactDiagnosis: Diagnosis.html

 

Web Service Response and Request:

See https://linkws.service.tieto.com/PasLinkWS/DiagnosisWS/DiagnosisWS.asmx?op=GetContactDiagnosis

 

Related methods or functions used:

GetUserLogin                   Used to verify a user, and to get a valid authentication Block in return.

 

Other references:

RequestHeader                Information required calling a method, containing authentication information.

ResponseHeader             Information and messages returned from the method, e.g. error codes/description, 

system name or version.

 

Comments:

To use this method the RequestHeader must contain a valid Authentication Block and the system name is required. An error will be raised if one of these is missing.

 

Valid Authentication Block for RequestHeader the can be retrieved by using the method GetUserLogin in Authentication-Web Service.

 

In return from the method there will always be a ResponseHeader, which contains Error Information and System Information. Error Information block must always be checked to determine if any error has occurred while processing the methods.

 

1.1.2   SaveContactDiagnosis

Applicable systems for method:

INFOMEDIX

HIS90

 

 

 

 

 

 

Description:

Saves main- and sub diagnosis for a contact. Either one or all can be saved.

 

Syntax:

ContactDiagnosis = SaveContactDiagnosis(ContactDiagnosis)

 

Parameter in

Type

Length byte

Description – Data format – Valid data

ContactDiagnosis

 

N/A

Dynamic

Contact diagnosis class according to XML schema ContactDiagnosis.xsd.

 

../Code/Id

 

 

Required if you want to update a diagnosis. The Id is obtained after insert or by getting the diagnosis.

../Code/MedCode/Code or ../Code/MedCode/Id

 

 

Required. This is the medical code, ie an ICD-10 code.

In His90 Id=MedRegisterId|D|ICD|DiagnosisCode. To get this id, use the Web Service CommonCodesWS, method ListMedicalCodes.

../Code/MedCode/MedRegister/Code or ../ Code/MedCode/MedRegister/Id

 

 

Required. Not required in His90.

This is the medical register, ie ICD-10. For medical registers you have to use the HIS-codes, not the official NPR-codes. To get these internal codes or id’s, use the Web Service CommonCodesWS, method ListMedicalRegisters.

 

../Code/SequenceNumber

 

 

Required even if you only want to insert one diagnosis. Not required in His90.

../Code/UpdateCount

 

 

Required in HIS90 if you want to update a diagnosis. Number of diagnosis updates. (implemented in version 1.1)

Returned parameter

Type

Length Byte

Description – Comments

ContactDiagnosis

 

N/A

Dynamic

Contact diagnosis class according to XML schema ContactDiagnosis.xsd.
It is only the Id (../Codes/Code/Id) that is updated in the resultset after insert. If you want to get all the data about this diagnosis, call the method GetContactDiagnosis.

 

Schema for ContactDiagnosis:  Diagnosis.xsd

Schema documentation for ContactDiagnosis: Diagnosis.html

 

 

Web Service Response and Request:

See https://linkws.service.tieto.com/PasLinkWS/DiagnosisWS/DiagnosisWS.asmx?op=SaveContactDiagnosis

 

Related methods or functions used:

GetUserLogin                   Used to verify a user, and to get a valid authentication Block in return.

 

Other references:

RequestHeader                Information required calling a method, containing authentication information.

ResponseHeader             Information and messages returned from the method, e.g. error codes/description, 

system name or version.

 

Comments:

To use this method the RequestHeader must contain a valid Authentication Block and the system name is required. An error will be raised if one of these is missing.

 

Valid Authentication Block for RequestHeader the can be retrieved by using the method GetUserLogin in Authentication-Web Service.

 

In return from the method there will always be a ResponseHeader, which contains Error Information and System Information. Error Information block must always be checked to determine if any error has occurred while processing the methods.

 

1.1.3   DeleteContactDiagnosis

Applicable systems for method:

INFOMEDIX

HIS90

 

 

 

 

 

 

Description:

Deletes main- and sub diagnosis for a contact. Either one or all can be deleted.

 

DeleteContactDiagnosis requires that GetContactDiagnosis is used first to get current diagnosis. Then delete diagnosis from the response form the get methods, before it is sent to DeleteContactDiagnosis. To delete a single diagnosis base on diagnosis id and contact id is not possible by this method.

 

Syntax:

DeleteContactDiagnosis(ContactDiagnosis)

 

Parameter in

Type

Length byte

Description – Data format – Valid data

ContactDiagnosis

 

N/A

Dynamic

Contact diagnosis class according to XML schema ContactDiagnosis.xsd.

 

../Codes/Code/Id

 

 

Required. This is the diagnosis id.

../Codes/Code/UpdateCount

 

 

Required in HIS90. Number of diagnosis updates. (implemented in version 1.1)

 

Returned parameter

Type

Length Byte

Description – Comments

None

 

 

 

 

Schema for ContactDiagnosis:  Diagnosis.xsd

Schema documentation for ContactDiagnosis: Diagnosis.html

 

 

Web Service Response and Request:

See https://linkws.service.tieto.com/PasLinkWS/DiagnosisWS/DiagnosisWS.asmx?op=DeleteContactDiagnosis

 

Related methods or functions used:

GetUserLogin                   Used to verify a user, and to get a valid authentication Block in return.

 

Other references:

RequestHeader                Information required calling a method, containing authentication information.

ResponseHeader             Information and messages returned from the method, e.g. error codes/description, 

system name or version.

 

Comments:

To use this method the RequestHeader must contain a valid Authentication Block and the system name is required. An error will be raised if one of these is missing.

 

Valid Authentication Block for RequestHeader the can be retrieved by using the method GetUserLogin in Authentication-Web Service.

 

In return from the method there will always be a ResponseHeader, which contains Error Information and System Information. Error Information block must always be checked to determine if any error has occurred while processing the methods.

 

1.1.4   RenumberSubDiagnosis

Applicable systems for method:

INFOMEDIX

Classic

HIS-90

 

 

 

 

 

Description:

Renumbers a subdiagnosis. All the other subdiagnosis are renumbered as well.

 

Syntax:

RenumberSubDiagnosis(PatientId, ContactId, DiagnosisId, InsertBeforeDiagnosisNumber)

 

Parameter in

Type

Length byte

Description – Data format – Valid data

PatientId

Number

4

Internal patient id

ContactId

Number

4

Internal contact id

DiagnosisId

 

Number

4

Internal diagnosis id (schema location ../Codes/Code/Id)

InsertBeforeDiagnosisNumber

Number

2

The new number of this sub diagnosis. If InsertBeforeDiagnosisNumber is 0, the diagnosis will be put last.

 

Returned parameter

Type

Length Byte

Description – Comments

None

 

 

 

 

Schema for ContactDiagnosis:  Diagnosis.xsd

Schema documentation for ContactDiagnosis: Diagnosis.html

 

 

Web Service Response and Request:

See https://linkws.service.tieto.com/PasLinkWS/DiagnosisWS/DiagnosisWS.asmx?op=RenumberSubDiagnosis

 

Related methods or functions used:

GetUserLogin                   Used to verify a user, and to get a valid authentication Block in return.

 

Other references:

RequestHeader                Information required calling a method, containing authentication information.

ResponseHeader             Information and messages returned from the method, e.g. error codes/description, 

system name or version.

 

Comments:

To use this method the RequestHeader must contain a valid Authentication Block and the system name is required. An error will be raised if one of these is missing.

 

Valid Authentication Block for RequestHeader the can be retrieved by using the method GetUserLogin in Authentication-Web Service.

 

In return from the method there will always be a ResponseHeader, which contains Error Information and System Information. Error Information block must always be checked to determine if any error has occurred while processing the methods.

 

1.1.5   FinishMedicalRegistration

Applicable systems for method:

INFOMEDIX

Classic

HIS-90

 

 

 

 

 

Description:

Sets medical registration (diagnosis, procedure codes) for a contact as finished. This means that diagnosis and procedure codes for the contact are locked for update, delete and insert. In Sweden medical registration must be set as finished before DRG grouping can be done.

 

Syntax:

FinishMedicalRegistrationResponse FinishMedicalRegistration(FinishMedicalRegistrationRequest)

 

Parameter in

Type

Length byte

Description – Data format – Valid data

FinishMedicalRegistrationRequest

 

 

Class including the following elements:

 

 

 

 

PatientId

Number

4

Internal patient id

ContactId

Number

4

Internal contact id

MedicalResponsibleId

String

N/A Dynamic

Internal Infomedix resource id. In Infomedix the datatype is Int32.

 

Returned parameter

Type

Length Byte

Description – Comments

FinishMedicalRegistrationResponse

 

 

Class including the following elements:

 

 

 

 

FinishedBy

String

N/A Dynamic

The usercode who finished the medical registration, ie “inb”

FinishedDate

DateTime

 

Date and time for when the medical registration was finished.

 

 

Web Service Response and Request:

See https://linkws.service.tieto.com/PasLinkWS/DiagnosisWS/DiagnosisWS.asmx?op=FinishMedicalRegistration

 

Related methods or functions used:

GetUserLogin                   Used to verify a user, and to get a valid authentication Block in return.

 

Other references:

RequestHeader                Information required calling a method, containing authentication information.

ResponseHeader             Information and messages returned from the method, e.g. error codes/description, 

system name or version.

 

Comments:

To use this method the RequestHeader must contain a valid Authentication Block and the system name is required. An error will be raised if one of these is missing.

 

Valid Authentication Block for RequestHeader the can be retrieved by using the method GetUserLogin in Authentication-Web Service.

 

In return from the method there will always be a ResponseHeader, which contains Error Information and System Information. Error Information block must always be checked to determine if any error has occurred while processing the methods.

 

1.1.6   CancelMedicalRegistration

Applicable systems for method:

INFOMEDIX

Classic

HIS-90

 

 

 

 

 

Description:

Cancel the finishing of the medical registration for a contact so that diagnosis and procedures can be edited again.

 

Syntax:

CancelMedicalRegistrationResponse = CancelMedicalRegistration(CancelMedicalRegistrationRequest)

 

Parameter in

Type

Length byte

Description – Data format – Valid data

CancelMedicalRegistrationRequest

 

 

Class including the following elements:

 

 

 

 

PatientId

Number

4

Internal patient id

ContactId

Number

4

Internal contact id

 

Returned parameter

Type

Length Byte

Description – Comments

CancelMedicalRegistrationResponse

 

 

Class including the following elements:

 

 

 

 

CancelledBy

String

N/A Dynamic

The usercode who cancelled the finishing of medical registration, ie “inb”

CancelledDate

DateTime

 

Date and time for when the finishing of medical registration was cancelled.

 

 

Web Service Response and Request:

See https://linkws.service.tieto.com/PasLinkWS/DiagnosisWS/DiagnosisWS.asmx?op=CancelMedicalRegistration

 

Related methods or functions used:

GetUserLogin                   Used to verify a user, and to get a valid authentication Block in return.

 

Other references:

RequestHeader                Information required calling a method, containing authentication information.

ResponseHeader             Information and messages returned from the method, e.g. error codes/description, 

system name or version.

 

Comments:

To use this method the RequestHeader must contain a valid Authentication Block and the system name is required. An error will be raised if one of these is missing.

 

Valid Authentication Block for RequestHeader the can be retrieved by using the method GetUserLogin in Authentication-Web Service.

 

In return from the method there will always be a ResponseHeader, which contains Error Information and System Information. Error Information block must always be checked to determine if any error has occurred while processing the methods.

 

1.1.7   SaveContactDiagnosisInclHistory

Applicable systems for method:

INFOMEDIX

 

 

 

 

 

 

 

NOT TO BE USED BY EXTERNAL SYSTEMS

1.1.8   DeleteContactDiagnosisInclHistory

Applicable systems for method:

INFOMEDIX

 

 

 

 

 

 

 

NOT TO BE USED BY EXTERNAL SYSTEMS

1.1.9   ContactDiagnosisRegistration

Applicable systems for method:

INFOMEDIX

 

 

 

 

 

 

 

NOT TO BE USED BY EXTERNAL SYSTEM